lishid
- lishid
- lishid
- Europe/Stockholm
- Yes
- No
MC-3564
The debug message "Unable to locate Sign at (x, y, z)" Should not appear every time a Packet 130 (Sign Update) is received in NetClientHandler if the block is not loaded. This causes annoyances to players in certain bukkit servers which changes the order of packets or has an alternative chunk sending algorithm.
The debug message "Unable to locate Sign at (x, y, z)" Should not appear every time a Packet 130 (Sign Update) is received in NetClientHandler if the block is not loaded. This causes annoyances to players in certain bukkit servers which changes the order of packets or has an alternative chunk sending algorithm.
The debug message "Unable to locate Sign at (x, y, z)" Should not appear every time a Packet 130 (Sign Update) is received in NetClientHandler if the block is not loaded.
This causes annoyances to players in certain bukkit servers which changes the order of packets or has an alternative chunk sending algorithm.
This is a Client-Side debug message shown in chat.
The debug message "Unable to locate Sign at (x, y, z)" Should not appear every time a Packet 130 (Sign Update) is received in NetClientHandler if the block is not loaded.
This causes annoyances to players in certain bukkit servers which changes the order of packets or has an alternative chunk sending algorithm.
This is a Client-Side debug message shown in chat.This should be a one line fix! Likely only one line needs to be removed in the packet handler class in the minecraft client.
Still an issue, please re-open.
This is and will remain an active issue as long as there is no official "Fixed" response. Please stop marking it as resolved after each major release without actually fixing it. Thanks!
Got it, thanks for reopening.