[MC-3564] Debug message "Unable to locate Sign at (x, y, z)" left inside Minecraft Client Created: 20/Nov/12  Updated: 17/Dec/15  Resolved: 17/Dec/15

Status: Resolved
Project: Minecraft: Java Edition
Component/s: None
Affects Version/s: 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
Fix Version/s: Minecraft 15w51a

Type: Bug
Reporter: lishid Assignee: ProfMobius (Thomas Guimbretiere)
Resolution: Fixed Votes: 16
Labels: None

Issue Links:
Duplicate
is duplicated by MC-5513 Unable to locate sign Resolved
is duplicated by MC-5640 Signs text vanish in SSP when moving ... Resolved
is duplicated by MC-7503 Unable to locate sign at... Resolved
is duplicated by MC-67619 unable to locate sign Resolved
is duplicated by MC-74452 "Unable to locate sign at x y z" Resolved
is duplicated by MC-3119 File format bugs. (Unable to locate s... Resolved
is duplicated by MC-4453 Unable to locate sign at [x , y, z] i... Resolved
is duplicated by MC-4878 Unable to locate sign bug Resolved
is duplicated by MC-4974 Signs Gone Blank Resolved
is duplicated by MC-5119 Minecraft tries to "locate signs" Resolved
is duplicated by MC-5192 Bug with signs Resolved
Relates
relates to MC-68052 "unable to locate sign..." when clone... Resolved
relates to MC-72823 Unable to Locate Sign (Render Issue) Resolved
CHK:
Confirmation Status: Community Consensus

 Description   

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.



 Comments   
Comment by user-f2760 (Inactive) [ 20/Sep/15 ]

confirmed for 15w38b unmodded

Comment by Zak [ 20/Sep/15 ]

This also happened to me in 1.8 recently, optifine 1.8 D5, no idea if it is optifine problem or minecraft bug, but it seems whenever I join a server, I join it 4 times, it says in chat [My IGN] has joined for like 4 or 5 times, and on other servers, I get the welcome message 4 times, also I get the unable to locate signs spammed in my chat all the time

Comment by bob [ 01/Sep/15 ]

Can confirm this is still an issue on a vanilla server running 15w35e with the recieving client also running 15w35e unmodified.

Comment by Fire Enn [ 27/Feb/15 ]

On 1.8.3 on SMP servers, I have the same problem

Comment by Marcono1234 [ 18/Jan/15 ]

Confirmed for 1.8.2-pre4 for vanilla server too

How to reproduce: Join a server and spam the "Cancel" and then "Join Server"

Comment by a [ 10/Jan/15 ]

Happened in 1.8.1.

Comment by Turnvax X [ 23/Nov/14 ]

I saw this issue today running an unmodified 1.8 client. I was connecting to a vanilla server which makes a big deal out of running the unmodified mojang jar.

Comment by Luca [ 27/Oct/14 ]

I still find this issue in 1.7.9
https://www.gommehd.net/attachments/2014-10-27_16-48-30-png.37493/

Comment by lishid [ 24/Oct/14 ]

Got it, thanks for reopening.

Comment by Galaxy_2Alex [ 24/Oct/14 ]

Please do not mark unreleased versions (anything starting with "Future Version") as affected. You don't know if it will be a problem in the future.

Also, I am just trying to be precise.

Comment by lishid [ 24/Oct/14 ]

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!

Comment by Galaxy_2Alex [ 24/Oct/14 ]

Is this still a concern in the current Minecraft version 1.8.1 Prerelease 3 / Launcher version 1.5.3 or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.

Comment by Jesper the End [ 19/Aug/14 ]

confirmed for 14w34b

Comment by jigar frobozz [ 17/Aug/14 ]

Still an issue even in 1.8 snapshots

Comment by MonsieurApple [ 01/Jan/14 ]

YES. This is still an issue @Talven81, @Tails

Comment by Kumasasa [ 08/Jul/13 ]

Reopened.

Comment by lishid [ 08/Jul/13 ]

Still an issue, please re-open.

Comment by MonsieurApple [ 08/Jul/13 ]

This is STILL an issue and never should have been closed as "Invalid".

Comment by mbcx2 [ 05/Jun/13 ]

I still find this issue in 1.5.2
I maybe think it's Optifine or mods I have

Comment by MonsieurApple [ 02/May/13 ]

Still an issue, please reopen.

Comment by Gabriel Vilariço [ 09/Jan/13 ]

Aconteceu comigo tambem, eu organizos minhas coisas em baus separados, dai coloco placas encima do bau para indicar o que deve ser colocadonele, e sempre que vou um pouco longe de casa, aparece "Unable to locale sign at x y z."

Comment by Abraham Ezequiel Ramirez Alba [ 20/Dec/12 ]

This should be fixed soon.

Comment by Stephen Baynham [ 28/Nov/12 ]

This happened to me very occasionally in SP testing when I created a mod that used a sign in a village component.

Comment by Roel MB [ 20/Nov/12 ]

This message not only occurs on bukkit servers
When one off these sign update packages gets faster to the client due to the block update package lagging
It also pops out this debug message
Making it annoying and spamming chat
Making this message optional when debug is switched on is more off a solution then popping it up everytime the problem occurs

Generated at Sun Jan 12 12:01:38 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.