Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Define attack startup/active/recovery frames, hitbox size and offset relative to parent in fighter yaml files. #157

Closed
odecay opened this issue Jul 26, 2022 · 1 comment
Closed

Define attack startup/active/recovery frames, hitbox size and offset relative to parent in fighter yaml files. #157

odecay opened this issue Jul 26, 2022 · 1 comment
Assignees
@odecay
Labels
scope:small A small and well-defined task scope:undetermined Undetermined size, needs investigation

Comments

@odecay
Copy link
Collaborator

odecay commented Jul 26, 2022 •
edited
Loading

Description

This is followup work to #134

Other notes

this may change with design of scripted attack properties that will come after #140
@odecay odecay added the scope:undetermined Undetermined size, needs investigation label Jul 26, 2022
@odecay odecay mentioned this issue Jul 26, 2022
Closed
@odecay odecay self-assigned this Jul 26, 2022
@odecay odecay added the scope:small A small and well-defined task label Jul 26, 2022
@odecay
Copy link
Collaborator Author

odecay commented Aug 12, 2022

closed in in #221

@odecay odecay closed this as completed Aug 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@odecay odecay

Labels
scope:small A small and well-defined task scope:undetermined Undetermined size, needs investigation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@odecay