BYOND(453.1035) BUG in Developer Help

ID:273143
 
Oct 19 2009, 2:57 pm
not sure but i get this during the game, anybody have any ideas what it means and how it can be fixed?

BYOND(453.1035) BUG: Invalid request for appearance data (4767/5965) from client version 454
BYOND(453.1035) BUG: Invalid request for appearance data (3435/5934) from client version 454
BYOND(453.1035) BUG: Invalid request for appearance data (3546/6246) from client version 454
BYOND(453.1035) BUG: Invalid request for appearance data (7837/9467) from client version 454
BYOND(453.1035) BUG: Invalid request for appearance data (8570/9544) from client version 454
BYOND(453.1035) BUG: Invalid request for appearance data (9551/9015) from client version 454
BYOND(453.1035) BUG: Invalid request for appearance data (9519/8938) from client version 454
BYOND(453.1035) BUG: Invalid request for appearance data (5244/8896) from client version 454
BYOND(453.1035) BUG: Invalid request for appearance data (3269/8896) from client version 454
BYOND(453.1035) BUG: Invalid request for appearance data (4838/8896) from client version 454
BYOND(453.1035) BUG: Invalid request for appearance data (7979/9111) from client version 454
BYOND(453.1035) BUG: Invalid request for appearance data (5434/8989) from client version 450
BYOND(453.1035) BUG: Invalid request for appearance data (2825/8300) from client version 454
BYOND(453.1035) BUG: Invalid request for appearance data (3016/8300) from client version 454
BYOND(453.1035) BUG: Invalid request for appearance data (3096/8300) from client version 454
BYOND(453.1035) BUG: Invalid request for appearance data (3098/8300) from client version 454
BYOND(453.1035) BUG: Invalid request for appearance data (3444/8300) from client version 454
BYOND(453.1035) BUG: Invalid request for appearance data (6168/8300) from client version 454
BYOND(453.1035) BUG: Invalid request for appearance data (7739/8300) from client version 454
BYOND(453.1035) BUG: Invalid request for appearance data (7948/8300) from client version 454
BYOND(453.1035) BUG: Invalid request for appearance data (7991/8300) from client version 454
BYOND(453.1035) BUG: Invalid request for appearance data (8308/8300) from client version 454
BYOND(453.1035) BUG: Invalid request for appearance data (9192/8300) from client version 454
BYOND(453.1035) BUG: Invalid request for appearance data (9492/8300) from client version 454
BYOND(453.1035) BUG: Invalid request for appearance data (5086/8301) from client version 454
BYOND(453.1035) BUG: Invalid request for appearance data (9112/8301) from client version 454
BYOND(453.1035) BUG: Invalid request for appearance data (8072/8301) from client version 454
BYOND(453.1035) BUG: Invalid request for appearance data (3163/8302) from client version 454
BYOND(453.1035) BUG: Invalid request for appearance data (3731/8302) from client version 454
BYOND(453.1035) BUG: Invalid request for appearance data (9012/8303) from client version 454
BYOND(453.1035) BUG: Invalid request for appearance data (6274/8303) from client version 454
BYOND(453.1035) BUG: Invalid request for appearance data (3979/8312) from client version 454
BYOND(453.1035) BUG: Invalid request for appearance data (4737/8312) from client version 454
BYOND(453.1035) BUG: Invalid request for appearance data (6284/11285) from client version 454
BYOND(453.1035) BUG: Invalid request for appearance data (10110/11285) from client version 454
BYOND(453.1035) BUG: Invalid request for appearance data (11013/10760) from client version 454
BYOND(453.1035) BUG: Invalid request for appearance data (10532/10493) from client version 453
BYOND(453.1035) BUG: Invalid request for appearance data (3030/10408) from client version 454
BYOND(453.1035) BUG: Invalid request for appearance data (3933/10409) from client version 454
BYOND(453.1035) BUG: Invalid request for appearance data (9509/10785) from client version 454
BYOND(453.1035) BUG: Invalid request for appearance data (10874/10785) from client version 454
BYOND(453.1035) BUG: Invalid request for appearance data (11289/10785) from client version 454
BYOND(453.1035) BUG: Invalid request for appearance data (5435/10785) from client version 454
BYOND(453.1035) BUG: Invalid request for appearance data (4352/10785) from client version 454
BYOND(453.1035) BUG: Invalid request for appearance data (4673/10785) from client version 454
BYOND(453.1035) BUG: Invalid request for appearance data (11057/10785) from client version 454
BYOND(453.1035) BUG: Invalid request for appearance data (10245/10785) from client version 454
BYOND(453.1035) BUG: Invalid request for appearance data (5080/10785) from client version 454
BYOND(453.1035) BUG: Invalid request for appearance data (8058/10785) from client version 454
BYOND(453.1035) BUG: Invalid request for appearance data (10343/10784) from client version 454
#1 Oct 19 2009, 3:07 pm
Bugs should be reported here. Please search before posting because this particular bug has been reported several times.
#2 Oct 19 2009, 3:13 pm
Have the host upgrade their BYOND version to the latest, it's a newer client sending invalid data to an older server.
#3 Oct 19 2009, 3:18 pm
In response to Nadrew (#2)
woulf if he was hosting with the latest linux bulid?
#4 Oct 19 2009, 3:22 pm
In response to Darker Emerald (#3)
Have the players update then.
#5 Oct 19 2009, 3:22 pm
This message is not a bug, although there was a bug related to the cases where it appears, and that has been fixed in 455. Since the message is describing what can be a normal circumstance, 455 will also no longer report it.

For future reference, it's a good idea to look for matching bugs (including resolved ones) in the bug tracker before posting new report.

Lummox JR
#6 Oct 19 2009, 3:39 pm
In response to Nadrew (#2)
Nadrew wrote:
Have the host upgrade their BYOND version to the latest, it's a newer client sending invalid data to an older server.

That's not the problem; older servers can handle newer clients. The problem is that the appearance IDs in question are being recycled between the time the client is told they exist and the time the client's request for their info reaches the server. The message is printed in those situations even though it's nothing important. The bigger problem is that the client is never told about the ID being recycled, so it waits on a response from the server that's never coming. Version 455 fixes these issues by having the server tell the client about the change, and the client will re-request the information the next time it sees that ID.

Lummox JR