-
Notifications
You must be signed in to change notification settings - Fork 70
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
.save last nade fails position if you move after throwing #244
Comments
Hm, this is an interesting point. I've always used I don't think this is easily fixable though -- for example, saving the position of a player during a running/jumpthrow of a grenade isn't going to work if the plugin only saves the final position/eye-angles. I do imagine this could be made more user-friendly, but I don't see a great solution. |
I know it's simple, but having this workflow listed on the Commands section (using .back and then .save) after verifying your nade is good would've saved me a lot of time rethrowing nades. I know it seems simple and obvious, but it's not at first. |
Expected behavior
throw a nade, and move (noclip or otherwise) to see if it landed properly. if it land successfully then you should able to use .save and then .goto the last nade to teleport back where you just threw the nade from.
Actual behavior
the position when u use .goto for the nade will be where you pressed .save from, not where you threw the nade. so you will tp to a useless spot every time, meanwhile your nade is still throwing from where you originally threw it.
Steps to reproduce
The text was updated successfully, but these errors were encountered: