mojira.dev
MC-3564

Debug message "Unable to locate Sign at (x, y, z)" left inside Minecraft Client

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.

Related issues

Comments

Roel MB

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

Stephen Baynham

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

Abraham Ezequiel Ramirez Alba

This should be fixed soon.

Gabriel Vilariço

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."

MonsieurApple

Still an issue, please reopen.

mbcx2

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

MonsieurApple

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

lishid

Still an issue, please re-open.

kumasasa

Reopened.

MonsieurApple

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

jigarbov

Still an issue even in 1.8 snapshots

Jesper the End

confirmed for 14w34b

galaxy_2alex

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.

lishid

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!

galaxy_2alex

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.

lishid

Got it, thanks for reopening.

Luca
Turnvax X

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.

a

Happened in 1.8.1.

marcono1234

Confirmed for 1.8.2-pre4 for vanilla server too

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

Fire Enn

On 1.8.3 on SMP servers, I have the same problem

bob

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

Zak

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

user-f2760

confirmed for 15w38b unmodded

lishid

migrated

Community Consensus

Minecraft 1.4.4, Minecraft 1.4.5, Minecraft 1.4.6, Minecraft 1.5.2, Minecraft 1.6.1, ..., Minecraft 1.8.2-pre4, Minecraft 1.8.3, Minecraft 1.8.8, Minecraft 15w35e, Minecraft 15w38b

Minecraft 15w51a

Retrieved