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
Minecraft Version: 1.20.1 Fabric Loader Version: 0.14.22 ViaFabricPlus Version: 2.8.5 and 2.8.7-SNAPSHOT Fabric API Version: 0.88.1+1.20.1
Server Version: CraftBukkit version git-PaperSpigot-445 (MC: 1.8.8) (Implementing API version 1.8.8-R0.1-SNAPSHOT)
Bug Description
When connecting to a Minecraft 1.8 server using ViaFabricPlus version 2.8.5, configured to use version 1.8, boats are not correctly modified on the client side, resulting in inconsistent behavior between the client and server.
Steps to Reproduce
Use ViaFabricPlus version 2.8.5.
Configure ViaFabricPlus to use version 1.8.
Connect to a Minecraft 1.8 server.
Observe that boats are not properly modified on the client side
Expected Behavior
I expected that, when connecting to a Minecraft 1.8 server running ViaFabricPlus version 2.8.5, which was configured to use version 1.8, the modification of boats on the client side would match version 1.8 to match the server side.
The text was updated successfully, but these errors were encountered:
General Information
Minecraft Version: 1.20.1
Fabric Loader Version: 0.14.22
ViaFabricPlus Version: 2.8.5 and 2.8.7-SNAPSHOT
Fabric API Version: 0.88.1+1.20.1
Server Version: CraftBukkit version git-PaperSpigot-445 (MC: 1.8.8) (Implementing API version 1.8.8-R0.1-SNAPSHOT)
Bug Description
When connecting to a Minecraft 1.8 server using ViaFabricPlus version 2.8.5, configured to use version 1.8, boats are not correctly modified on the client side, resulting in inconsistent behavior between the client and server.
Steps to Reproduce
Expected Behavior
I expected that, when connecting to a Minecraft 1.8 server running ViaFabricPlus version 2.8.5, which was configured to use version 1.8, the modification of boats on the client side would match version 1.8 to match the server side.
The text was updated successfully, but these errors were encountered: