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.

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

Fix the enemies attack hitbox #156

Closed
64kramsystem opened this issue Jul 26, 2022 · 5 comments · Fixed by #158
Closed

Fix the enemies attack hitbox #156

64kramsystem opened this issue Jul 26, 2022 · 5 comments · Fixed by #158
Labels
kind:bug Something isn't working scope:undetermined Undetermined size, needs investigation

Comments

@64kramsystem
Copy link
Member

Description

The hitbox of the enemies attack is not correct; at least 50% of the times, the enemy attacks don't land; the hitbox seems to be too small.

To Reproduce

No response

Expected Behavior

No response

Additional Context

No response

Log Messages

No response

@64kramsystem 64kramsystem added kind:bug Something isn't working scope:undetermined Undetermined size, needs investigation labels Jul 26, 2022
@odecay
Copy link
Collaborator

odecay commented Jul 26, 2022

Depends what you mean by correct but its working as intended right now, the hitbox does not line up with the enemies hands as it is a box spawned ontop of the center. This will be left till attack hitbox size and offset are defined through fighter resource files.

Is that what you mean or is there another reason the attacks dont land? The other thing that you might be noticing is that currently the "bandit" attack animations last for significantly longer due to animation, but use the same short window of active frames as the other enemy, causing them to stand there and punch for awhile after the hitbox stops being active. This is also something to be addressed in resource file definitions of fighters attacks.

if you run witn --features=debug you can see the places where the larger green box is spawned ontop of the enemy, those should be the only times that an attack is active, if it doesn't hit within that window then it is indeed a bug.

@64kramsystem
Copy link
Member Author

64kramsystem commented Jul 26, 2022

Depends what you mean by correct but its working as intended right now, the hitbox does not line up with the enemies hands as it is a box spawned ontop of the center. This will be left till attack hitbox size and offset are defined through fighter resource files.

It's a bit strange. It seems that there are very slight differences, that cause hits to miss, when it seems that they should have landed. It seems that his happens in particular to the slinger (not 100% sure on this, though).

I've made a video:

record-2022-07-27_00.36.31.mp4

There are a few instances of misses, one is for example at 0'37". Maybe it's something difference, for example, the Z coordinate 🤔

@64kramsystem
Copy link
Member Author

I'll check with the hitboxes enabled 🤔

@odecay
Copy link
Collaborator

odecay commented Jul 26, 2022

Okay thanks for the video, this is indeed what I pointed out above, both enemies currently use the same attack hitbox and frame properties. The hitbox does not line up with the attacks but I left it that way intentionally. I can quickly make the hitbox bigger before release to close this out but ultimately this will be addressed in #157.

@64kramsystem
Copy link
Member Author

Okay thanks for the video, this is indeed what I pointed out above, both enemies currently use the same attack hitbox and frame properties. The hitbox does not line up with the attacks but I left it that way intentionally. I can quickly make the hitbox bigger before release to close this out but ultimately this will be addressed in #157.

I see. Thanks! That actually makes... the player easier to kill, which is something a bit hard right now 😂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind:bug Something isn't working scope:undetermined Undetermined size, needs investigation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants