-
Bug
-
Resolution: Fixed
-
Minecraft 1.4.4, Minecraft 1.4.5, Minecraft 1.4.6, Minecraft 1.5.2, Minecraft 1.6.1, Minecraft 1.7.1, Minecraft 1.7.2, Minecraft 1.7.4, Minecraft 14w33c, Minecraft 14w34b, Minecraft 1.8, Minecraft 1.8.1-pre3, Minecraft 1.8.1, Minecraft 1.8.2-pre4, Minecraft 1.8.3, Minecraft 1.8.8, Minecraft 15w35e, Minecraft 15w38b
-
None
-
Community Consensus
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.
- is duplicated by
-
MC-5513 Unable to locate sign
- Resolved
-
MC-5640 Signs text vanish in SSP when moving far from the source
- Resolved
-
MC-7503 Unable to locate sign at...
- Resolved
-
MC-67619 unable to locate sign
- Resolved
-
MC-74452 "Unable to locate sign at x y z"
- Resolved
-
MC-3119 File format bugs. (Unable to locate sign, bad compressed file format, chunk errors)
- Resolved
-
MC-4453 Unable to locate sign at [x , y, z] in Single Player.
- Resolved
-
MC-4878 Unable to locate sign bug
- Resolved
-
MC-4974 Signs Gone Blank
- Resolved
-
MC-5119 Minecraft tries to "locate signs"
- Resolved
-
MC-5192 Bug with signs
- Resolved
- relates to
-
MC-68052 "unable to locate sign..." when clone command places sign/banner at same location again
- Resolved
-
MC-72823 Unable to Locate Sign (Render Issue)
- Resolved