Enable MC-159163 in Debugify

[Waseem973]

What config to change

Enable MC-159163 in Debugify and allow it in servers too (debugify classifies it as a potentially advantage-providing fix, and the modpack's config is to not allow unfair advantage patches in debugify, but I really don't see how it provides any advantage)

Why should it be changed

It is a very annoying bug that most players experience when playing on servers. The bug is that pressing sneak once will make the screen sneak twice repeatedly (even though sneaking only happens once). This bug is seriously annoying when fast bridging.

Additional details

No response

[BlackWinnerYoshi]

At this point, I'd suggest enabling MC-8187 in addition to MC-159163, because both fix annoying gameplay issues and Mojang Microsoft doesn't care about either.

[TheBossMagnus]

What config to change

Enable MC-159163 in Debugify and allow it in servers too (debugify classifies it as a potentially advantage-providing fix, and the modpack's config is to not allow unfair advantage patches in debugify, but I really don't see how it provides any advantage)

Why should it be changed

It is a very annoying bug that most players experience when playing on servers. The bug is that pressing sneak once will make the screen sneak twice repeatedly (even though sneaking only happens once). This bug is seriously annoying when fast bridging.

Additional details

No response

It could trigger the server's anticheat (not sure). And anyway it provides a substancial difference that can be considered by server as unfair advantage (for example in a fight between two player) because it reduces motion.

MC-8187 changes vanilla behavior and can break farm or contrmptions. this is against fo principles.

[Waseem973]

@TheBossMagnus

It could trigger the server's anticheat (not sure). And anyway it provides a substancial difference that can be considered by server as unfair advantage (for example in a fight between two player) because it reduces motion.

No, it cannot trigger the server's anticheat. This bug is purely a visual bug on the client side and fixing it does not change game mechanics in any way. As for choosing to live with the bug because fixing it may provide an unfair advantage and thus is deemed unethical, here's my take: not everyone suffers equally from this bug. It is very dependent on your ping. People with low ping may not even notice or be annoyed by it. Choosing to live with it does not ensure everyone has a fair experience; fixing this bug does. By trying to fix this bug for everyone, no player that suffers the least from the bug will have an advantage over another player who suffers the most from the bug. In any ordinary game, no such decision needs to be made. However, Mojang is one of the laziest game studios of the decade, and relying on it to fix a simple bug is not feasible.

[BlackWinnerYoshi]

Maybe the best solution then would be to mention Debugify's gameplay fixes somewhere (probably the FAQ, not sure if on first boot would break the goals/principles though). Now that I think about it, touching any "gameplay fixes" will break the principles.

Or perhaps, players can figure out by themselves, that Debugify can fix this issue?