Your username: Pedry In which minigame/server does the bug occur: Spleef Detailed description of bug: made a video to explain the issue focus on the snow, and set the quality to 1440p for less compression so you can tell easier the blocks on jh reappear
I have about 130 - 140 ping on both servers this is more recent, dont remember this hapening the moment the update came out I tried asking another random player about the issue and my reply was yes, the issue was there for that player aswell
i'm not sure i see the problem in your video, it feels fine to me. did you try doing this in vanilla 1.8?
in 1.8 its not the same, yet its still present, the bug is more descrete where the block break is simply delayed a bit, instead of being replaced and then breaking like you see in the video, basically feels more like latency and not a bug. (This is not normal, even with high ping. Ive played spleef for 7 years and never seen this issue)
I'm not the only one with this problem, I have talked to more players about the bug, its there alright.. It might appear normal to you, maybe you're playing on 1.8, either that or you ping is good enough to make the breaking bug not noticeable, however this is literally unplayable for me and many others considering that higher level spleef is a split second judgement game :/ I asked 3 other players whereas one of them is a competitive spleef player, one is a professional builder and the last one was a random player playing on your server that i didn't recognize... All of them had this same issue...
Can confirm this happens to everyone on 1.16 (the main version used for spleef), the bug initially started occurring occurring around the time the new anti-cheat was added, hence could be due to that. It has nothing to do with ping as all of the players with lower ping i have spoken to about it have testified they experience this bug too.
1.16 isn't a good version. (no offense) 1.8.9 is the stuff. it might also be a internet issue but it's probably to do with the anti-cheat because of the extra block each on 1.16. I'm not really a spleef player but as someone who gets 220-240 ping it's fine for me. Idk tho
i highly doubt its due to the extra 2 pixel reach on 1.16 as that’s only when crouched, the bug happens all the time, even when not crouched
Josh is right, look at my recent video, it is obvious if you watch it. Reach has nothing to do with it, and what version you want to use is irrelevant, the server supports all versions and has done it well with no game breaking bugs since 1.9 was released. This creates a horrible experience for anyone wanting to stay up to date, and its a bug that can easily be fixed by making the spleef arena an exception for the anticheat (Spleef only needs anti fly protection).
It's doing something, It's clear this issue appeared when the new anticheat got implemented Try the bug out for yourself, play on 1.16.. Also is there anything other than a new anticheat that has changed the code on the server ever since the release of the new spleef season, since this wasn't an issue in the beginning of the season?
It doesn't have to be packets, it could be a simple prevention system for fast block breaking using BlockBreakEvents (IDK), i've heard 1.16 can break blocks a bit faster than 1.8.. (All i know is that a recent change on the server did this) My theory is that this is what the new anticheat is doing, not allowing blocks to break faster than what is possible on vanilla 1.8 and replacing the blocks to have the amount of broken blocks match 1.8 Never heard of anticrash plugins... Can you explain how it works or what and how it does what it does?
Tag me on Discord when you're online and if I'm there I'll disable the anti-crash temporarily so you can test --edit we tested and no difference with or without anti-crash
This is what I was getting at - The anticheat does not stop cheats, roll-back actions of users or prevent the cheats from taking place in any way/shape/form. It prevents cheats from continuing by banning the users that it detects. I don't have the answer for what is causing it, but I can at least rule that out.