-
Notifications
You must be signed in to change notification settings - Fork 9
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
Spam jumping with an elytra while sprinting triggers survivalfly #521
Comments
Same thing happens with me too. |
I get the same on occasion. Is that behavior needed for anything? |
It isn't needed for anything as far as I am aware of. |
you can do some sort of bunny hopping with it if you get the timings right. |
Could perhaps build a strict and non-strict option? Not sure what bunny hopping is, but a separate check for it could be an option |
Bunny hopping is jumping again the second, or tick, that you land in order to speed up and move faster from point A to point B. Ncp already limits this speed advantage to roughly 15% if I remember correctly. |
@Joe7670 Not sure, the moving stuff tends to become complicated on the modeling side. Debug logs of reproducing this repeatedly may help in nailing it all down. At first i have to fix the mess i've created over the last weeks, so i we can all proceed (...). Currently my changes don't compile due to test failures - once that's fixed,i can test more stuff. (At least i'm past the syntax error phase.) |
I've noticed when I press space a lot while having an elytra equipped, it'll sort of "bug out" and jitter me around. When I rocket straight up, or off quickly, especially when I have bad ping, I'll get teleported back a long way and lose most of the momentum of my elytra rocket boost. Is the latter part of NCP, too? |
@SpacePuppeh Possibly - in such a case it'll be helpful to see if there are violation logs of NCP but also 'moved ... too quickly/wrongly' on the server log. |
Short description of the issue.
When you put on an elytra and start sprinting + spamming spacebar, ncp seems to generate vl under survivalfly. I was able to do this on a dedicated server, but I couldn't seem to reproduce it on a localhost server. It just seemed oddly smoother when testing on a dedicated server. It's sort of like recreating that Mario cape flying thing if you know what I mean, but just in minecraft and not flying upwards.
Complete output of the ncp version command (please prefer text here).
---- Version information ----
Server
git-Paper-1337
MC: 1.12.2detected: 1.12.2
NoCheatPlus
Plugin: 3.16.1-SNAPSHOT-sMD5NET-b1135
MCAccess: 1.12-1.12.2 / Spigot-CB-1.12_R1
Features:
blocks: BlocksMC1_4 | BlocksMC1_5 | BlocksMC1_6_1 | BlocksMC1_7_2 | BlocksMC1_8 | BlocksMC1_9 | BlocksMC1_10 | BlocksMC1_11 | BlocksMC1_12
checks: FastConsume | Gutenberg | HotFixFallingBlockPortalEnter | AttackFrequency | FlyingFrequency | KeepAliveFrequency
defaults: pvpKnockBackVelocity
packet-listeners: UseEntityAdapter | MovingFlying | OutgoingPosition | KeepAliveAdapter | SoundDistance
Hooks: AllViolations
NCP1.0Related Plugins
ProtocolLib v4.3.0
How to reproduce the issue (is it random / always happens / side conditions)?
As explained above, just put on an elytra, and start sprinting + spamming clicking spacebar.
Have you made any (noteworthy) changes to the default configuration of NCP?
Occurs with the default configuration.
Do you run any other special plugins that affect game mechanics next to NC+ (adding skills, machines, adding/changing blocks, other anti cheating)?
Not that I am aware of.
Provide additional information, such as error/debug/violation logs. (For reproducible issues with moving consider: https://github.com/NoCheatPlus/Docs/wiki/Debugging#on-the-fly-debug-output-for-individual-players) Use GitHub gists or http://pastebin.com/ or similar for huge logs, or attach a (zip-) file here. For image uploads, please prefer a site that allows viewing without JavaScript, you can upload file attachments for issues right here.
debug log: 1/2: https://pastebin.com/vnSagdkZ
debug log 2/2: https://pastebin.com/CkdfHu9R
The text was updated successfully, but these errors were encountered: