You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a FAWE plugin on my server, when I log into the server with versions < 1.19, I get a bug when selecting blocks with an axe. For example: I selected a block with the left mouse button and it visually disappeared, tested on all versions below 1.19.
My server is on version: 1.20.4. ViaVersion: 5.0.0, ViaBackwards 5.0.0
Steps to Reproduce
Login with versions < 1.19
You take an axe in your hands to mark out the territory
After selecting with the left mouse button, the block disappears visually
Expected Behavior
When you left-click the block should disappear for 1 ms and then appear. This happens in phenomena without the bug.
Additional Server Info
No response
Checklist
Via plugins are only running on EITHER the backend servers (e.g. Paper) OR the proxy (e.g. Velocity), not on both.
I have included a ViaVersion dump.
If applicable, I have included a paste (not a screenshot) of the error.
Was that within or outside spawn protection? Please also try removing other plugins and a standard Paper server, this would otherwise be caused by some plugin cancelling the interact event instead of the block break, then breaking apart the changed block ack system
'/viaversion dump' Output
https://dump.viaversion.com/2f7795ab2c6ba8c2127d925eca815e39ef481c6a8fb40132f3f6780d6dc448db
Console Error
Absent
Bug Description
I have a FAWE plugin on my server, when I log into the server with versions < 1.19, I get a bug when selecting blocks with an axe. For example: I selected a block with the left mouse button and it visually disappeared, tested on all versions below 1.19.
My server is on version: 1.20.4. ViaVersion: 5.0.0, ViaBackwards 5.0.0
Steps to Reproduce
Expected Behavior
When you left-click the block should disappear for 1 ms and then appear. This happens in phenomena without the bug.
Additional Server Info
No response
Checklist
The text was updated successfully, but these errors were encountered: