[1.19.2-2.2.7 Fabric] Game crashes whenever left-click anywhere in velocity backend server.
polaris-stella opened this issue · 1 comments
Problem Description
I encountered a problem: the game crashes whenever I left-click on a block or in the air. Additionally, hovering the mouse pointer over a backpack item in this mod within the creative inventory also causes the game to crash.
This issue occurs only in multiplayer mode, and the server must be a backend server of Velocity. (I tried waterfall, but I couldn’t even join the game.)
Reproduction Steps
-
Download and run the 3.2.0-SNAPSHOT-289 version Velocity server and 1.19.2-0.14.24 version of Fabric server. Prepare the corresponding version of the fabric client.
-
Install the following mods on both the fabric client and server:
- ‘fabric-1.19.2-2.2.7’ version Backpacked
- ’fabric-1.19.2-0.6.16‘ version Framework
- ’0.76.1+1.19.2‘ version Fabric API
-
Install 0.1.5 version of CrossStitch only on the Fabric server (it's necessary to join the game)
-
Join the game, Then left click on a block or in the air, or hovering the mouse pointer over a backpack item in this mod.
Environment Information
- OS: Windows 11 (amd64) version 10.0
- Minecraft version: 1.19.2
- Fabric version: 0.14.24
- Fabric API version: 0.76.1
- Framework version: 0.6.16
- Backpacked version: 2.2.7
- CrossStitch version: 0.1.5
- Velocity version: 3.2.0-SNAPSHOT-289
- Java Version: 17.0.2, Eclipse Adoptium
- Java VM Version: OpenJDK 64-Bit Server VM (mixed mode, sharing), Eclipse Adoptium
Additional Information
Crash report: https://mclo.gs/0SeeIri
I'll be honest, probably nothing I can do. I believe this mainly falls on Velocity, I use the Fabric Networking API to send config data during the handshake (when player is connecting to the server). It appears you are not receiving the data, hence the crashes are occurring. Even if you didn't crash, the mod will behave irregularly since you don't have the config data from the server. I am also not super familiar with Velocity, so not sure if there are any settings you need to tweak to fix said issues.
I'll leave this open, but there is unlikely to be a fix unless someone on the Velocity team sees this.