POL 097 rc3
On a test server set in pol.cfg:

MinCmdlevelToLogin=5

(also tried MinCmdlevelToLogin=1)

Then try to logon as a player, ie cmdlevel 0.

Exception and crash in pol with no error cause in the logs or on console.

I still get this problem.
MinCmdlevelToLogin=1
will cause a pol crash when I logon even with cmdlevel 5.

I have it too

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.

I am using the latest core.
Strangely enough it's not hard to script so I'm not bothered.

I am wondering if it's one of the packethooks doing it to me as it was the last script that was run before it did a stack backtrace.

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.

still going on or what? hehe

Ups, I did it again...

with a dmp file this time ;p

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

Yes, I do. I hooked it when I tried to use uogateway and totaly forgot about it.

I disabled it right a way.

Later I post the result.

Any news, coltain?

It`s ok. Works as it should be.

Tested it for a week with players online, without players, players trying to connect... in every way.

Thx for a advice.

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.

Is there a way to check if there is a IGR status ??? I would like to add this info to www to check it.

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?

I'll look over this script real quick (should still be in Custom Script Releases)

IGR is just a leftover thing in the client. According to EA, its not even used on the official shards anymore.

http://support.ea.com/cgi-bin/ea.cfg/ph ... faqid=1588