Frame-based hitbox automation #19
Labels
No labels
0. Imported
1. Bug
1. Clean-up
1. Feature
1. Improvement
2. Deliverable
2. Epic
3. Duplicate
3. Invalid
3. Need investigation
4. Assets
4. Birb Core
4. Debug
4. Dependencies
4. Inputs
4. Lang
4. Scenes
4. Screen
4. World
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: epervier/epervier-old#19
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
It could be usefull to create a frame-based hitbox automation. Basically, it would indicate for every frame of an animation file the different hitboxes and their data (type, size, etc).
We would need to check at least x, y, w, h, ox, oy to return the default value if it’s not here. Then it would be directly transfered as-is, allowing us to support by default custom value (for instance the power of an hit, making us even able to allow).
The biggest question is : should we make that according to animation data or directly frame data. The first one would make us able to support directly different animations that use the same frames.
Fixed by #22