-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add more enemies #160
Add more enemies #160
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome! I just had a couple of tiny suggestions.
Change Bandit to Brute Co-authored-by: Zicklag <zicklag@katharostech.com>
Sweet let's merge it! bors merge |
Build succeeded: |
repeat: false | ||
attacking: | ||
frames: [16, 23] | ||
frames: [14, 16] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The frame change in the actual spritesheet asset has broken hitbox despawn for bandit attacks. It will be a simple fix but I won't have time to do it till later today/tonight. Unfortunately 3 frames of animation is really not much to work with, and since I haven't implemented loading attack frame definitions from assets yet all the attacks use the same frame data right now.
edit: it looks like there is at least another frame we can use in the actual spritesheet so it can go up to 4 which gives a bit more space.
The image property, of the fighter yaml files, now receives an array of image paths that will be loaded and stored.
When adding the correct components for the enemy a random texture atlas is picked.