I don't know from which date rc3 was, but i tried this on the the latest release
POL097-2008-09-01 and it didn't crash. Perhaps you could use this core to avoid the problem.
It's really stable, i never had a crash on the live shard since this one gone public.
Strange. Sounds a bit like a bug we had since pol 94. But more vice versa.
When a player connects at a certain point when the server was started,
pol crashes. We never found that specific point, so we set for the first
20 min. after server start the MinCmdlevelToLogin=2 and after that time
back to zero to avoid that crash.
This dump file is pointing to an exported packet hook function.I can say it is a Variable Length Packet. Do you hook the 0x82 packet by chance? (Login Denied) ? Just curious.......
Spot on MuadDib.
I still had Shinigami's UOGateway packetinfo hook enabled that hooks 0x82 SendFunction.
Removed and MinCmdlevelToLogin works as expected now.
I am not sure if this means there is still a core bug or that hooking 0x82 should be avoided.
Now what the heck does "The IGR time limit has been met" mean? That's the charming message you get when you can't logon with a v5 client. Suddenly that other conversation about the new uoexpansions comes to mind.
What is IGR? I don't think it's supported by core.
The IGR timeout error is the MISC_ERROR value core uses. It's used for any case that's not a wrong password, etc. Is there a better error to use in these cases?