Miscellaneous: Error 1018 conditions are possibly not implemented correctly

[arosian]

Related Patch Note History
See http://www.project1999.org/forums/sh...highlight=1018
On February 14, 2010, a patch rolled out that included these two notes:

• Rogean: The infamous Error 1018 is making its return; Attempting to enter the server with an active character will no longer be possible until that character is removed from the world.
• Rogean: Due to the above change, Linkdead characters will now be kicked after 30 seconds of no aggro, or 3 minutes on aggro.

See: http://www.project1999.org/forums/sh...highlight=1018
On March 9, 2010, a patch rolled out that included this note:

• Rogean: Attempting to enter the server while previously being disconnected during zoning will allow you to enter, and will kick off the zoning character, instead of receiving 1018. Upcoming.

Since then, no other mention to Error 1018 has been made in any patch notes. There is a buggy implementation of this specific "active character" check that cannot be explained by anything other than a server side implementation. Let me explain why.

Problem Description
I have two accounts that will experience this problem at random times from any computer, IP, or location even when the characters are never logged into the world. I have tried every "solution" presented on the forums from other users such as re-installation of EQ, trying different computers, trying different routers, and deleting character UI/.ini files without any success. See my tests performed below (bold indicates uniqueness of the test).

Tests Performed
Test 1, Setup: Main computer, main router, main modem, main IP.
Test 1, Login: Type in user/pass combination, click Login, success to server select. Select P1999, Error 1018 will present itself.

Test 2, Setup: Secondary computer, main router, main modem, main IP.
Test 2, Login: Type in user/pass combination, click Login, success to server select. Select P1999, Error 1018 will present itself.

Test 3, Setup: Main computer, main router, main modem, renewed IP.
Test 2, Login: Type in user/pass combination, click Login, success to server select. Select P1999, Error 1018 will present itself.

Test 3, Setup: Friend's computer 1000+ miles away, friend's router, friend's modem, friend's IP.
Test 3, Login: Type in user/pass combination, click Login, success to server select. Select P1999, Error 1018 will present itself.

Wait 1 hour, repeat tests, same results.
Wait 6 hours, repeat tests, same results.
Wait 24 hours, repeat tests, Error 1018 does not present itself, logout without selecting a character.
Wait 24 more hours, repeat tests, Error 1018 resurfaces even though no character has been selected to enter the world at the character select screen.

Conclusion and Thoughts

• I have never experienced this error on any other EQEmu server.
• Two of my three LS accounts are affected. The working account has never seen this problem.
• Changes to network setup have no effect.
• Changes to EverQuest installation have no effect.
• Error 1018 will persist for hours and hours (patch note says character should be dropped after 3 minutes).
• Using /camp will not prevent this error from occurring.

I have no way of confirming the exact behavior of the conditions under which Error 1018 occurs, because I don't have access to the P1999 source code. However, I think it's fairly suspect that a straggling crossed-out patch note is the final indication of any change made to its behavior. This problem is persistent, affects a moderate amount of people, and completely negates the ability to play on this server. As such, I feel this bug should at least be researched and/or addressed.