[288] lastcorrectstate default: The thing that should not be

While looking through my logs I noticed something curious. While most console logs amount to somewhere between 10 and 200kbs of data, one was over a mb.

Curious as to what could cause it (Surely I've never played KAG that long in one setting?), I checked it out. It was the title repeated ad nauseum for several thousand lines. Along with;

Code:

[283] setNetworkID: wrong id 0

[I](Repeat hundreds of times) [/I]

[283] setNetworkID: wrong id 0

[283] Packet index moved too far 27596 / 1176
[283] Unknown packet 50
[283] *Match Started*
[284] Packet index moved too far 27596 / 1176
[284] Unknown packet 50
[285] Packet index moved too far 27596 / 1360
[285] Unknown packet 52
[286] Packet index moved too far 27596 / 1360
[286] Unknown packet 52
[287] Packet index moved too far 27596 / 1648
[287] Unknown packet 52
[287] <RCON> Unnamed player is now known as MOLE Beef

This is dated the 17/11/2011. Anyone have any idea what the hell was going on?

 

Just got this again. 4mbs worth of console log this time before I stopped it.

Code:

[709] lastcorrectstate default: The thing that should not be
[709] lastcorrectstate default: The thing that should not be
[709] lastcorrectstate default: The thing that should not be
[709] lastcorrectstate default: The thing that should not be
[709] lastcorrectstate default: The thing that should not be
[709] lastcorrectstate default: The thing that should not be
[709] lastcorrectstate default: The thing that should not be
[709] lastcorrectstate default: The thing that should not be
[709] lastcorrectstate default: The thing that should not be
[709] SwitchTool: wrong team!
[709] convertToolToClass: wrong team 12/2
[709] getTeam: Team (12) out of bounds
[709] lastcorrectstate default: The thing that should not be
[709] lastcorrectstate default: The thing that should not be
[709] lastcorrectstate default: The thing that should not be
[709] lastcorrectstate default: The thing that should not be
[709] lastcorrectstate default: The thing that should not be
[709] lastcorrectstate default: The thing that should not be
[709] lastcorrectstate default: The thing that should not be
[709] lastcorrectstate default: The thing that should not be
[709] lastcorrectstate default: The thing that should not be
[709] lastcorrectstate default: The thing that should not be
[709] lastcorrectstate default: The thing that should not be
[709] convertToolToClass: wrong team 9/2
[709] getTeam: Team (9) out of bounds
[709] lastcorrectstate default: The thing that should not be
[709] lastcorrectstate default: The thing that should not be
[709] lastcorrectstate default: The thing that should not be
[709] SwitchTool: wrong team!
[709] convertToolToClass: wrong team 14/2
[709] getTeam: Team (14) out of bounds
[709] lastcorrectstate default: The thing that should not be
[709] lastcorrectstate default: The thing that should not be
[709] lastcorrectstate default: The thing that should not be
[709] lastcorrectstate default: The thing that should not be
[709] lastcorrectstate default: The thing that should not be
[709] lastcorrectstate default: The thing that should not be
[709] lastcorrectstate default: The thing that should not be
[709] SwitchTool: wrong team!
[709] convertToolToClass: wrong team 8/2
[709] getTeam: Team (8) out of bounds

As a taster. Any ideas anyone?

 

I think I've gotten this before. Were you on a server that had more than 32 slots?

I think I went on one of Jaedizzle's servers and that happens from time to time. The server ends up having to be reset because it goes crazy after running with that many people for a while.

 

I have had and known about this for a long time, but thought it was common knowledge. Whenever you get one of those maps where you see the tent in the top left and you crash out, this is the error that you get.

 

@Kouji; It was indeed Jaedizzles 48. Interesting

@Luigi; Never heard of it before. Are you sure it's the tent thing? I didn't get a chance to look at the map before it spazzed.

Hopefully it won't happen again. Seems a rare bug if nothing else.

 

Could be unrelated to the tent, but I get this whenever I have the problem, next time I run into it (it's been a while) I will check it and post the exact numbers and such.

 

Well there you go. Netcode for servers is only optimal for 32 slots, any higher than that and after a while the server will start freaking out. Teemo may probably have to restart it, if he hasn't already.