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.
Linked issues
is duplicated by 11
relates to 2
Comments 24
This happened to me very occasionally in SP testing when I created a mod that used a sign in a village component.
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."
Confirmed for 1.8.2-pre4 for vanilla server too
How to reproduce: Join a server and spam the "Cancel" and then "Join Server"
Can confirm this is still an issue on a vanilla server running 15w35e with the recieving client also running 15w35e unmodified.
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
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