-
Notifications
You must be signed in to change notification settings - Fork 72
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
Update and fix replay #310
Conversation
standard replay based on origin and angle still little laggy, and still many thing to be optimize(the whole plugin)
This reverts commit 7c4683f.
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.
this is a big change, and a lot of communities will be happy about this! thank you.
code seems good, but like you said, testing needed
Did some testing:
Great work! Excited to see these issues finally be a thing of the past. |
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.
epic
Sometimes the bots bug when a player cuts a trigger/wall too close, and it has been bothering us for a long time:rage:
Also, this problem can be traced back to the time since cksurf use velocity and angle to store our replay
(pretty worse legacy:joy:)
some like #20 #98 point it out directly but no one solve.
This PR cost me a half day, and here's what i'm mainly doing
I haven't done enough testing yet, may have bugs
but hope that there's something change since this pr 😣😣😣.