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 #541 : remove weak hook using #2478
Conversation
Please use descriptive variable names.
This change can only be merged in the next major version bump as this changes network code. |
I'd rename the function to AddHookDragVel, and I'd also reset the var in this function, just at the end. So you could remove the reset function |
And why dont we need it while firing ninja? was it like that before? |
I used the Reset function to set this additional velocity to whatever the weapon.
I noted that the function teeworlds/src/game/server/entities/character.cpp Lines 150 to 155 in a60ab8d
Since this is taking account in Tick, depending on the character order, the players' hook have either no effect or a small effect on the speed and the position. Since the position is also updated by And I realize that the players hit by a ninja isn't fair either. |
It looks like the hook code is only in the server side now. Have you tested hook interactions in the client side? The code is also used there (which is why it's a protocol change AFAICT). |
The current prediction is broken anyway. The order of the character handling differs between client and server. |
yikes |
Use SaturateAdd after summing all the dragging velocity