Recently, when the server lags and I accidently click an npc multiple times while waiting for a reply, it'll boot me out to the login screen with the dialog pixels remaining on screen. Here's the error dump when it occurs: 00:43:07.063: First chance exception 0xE06D7363 (Microsoft C++ Exception) occurred in "KERNEL32.DLL" at address 0x7C812FD3 by thread 0x698. 00:43:07.110: First chance exception 0xE06D7363 (Microsoft C++ Exception) occurred in "KERNEL32.DLL" at address 0x7C812FD3 by thread 0x698. 00:43:07.110: First chance exception 0xE06D7363 (Microsoft C++ Exception) occurred in "KERNEL32.DLL" at address 0x7C812FD3 by thread 0x698. 00:43:08.094: GetProcAddress(0x7E410000 [USER32.DLL], "PostMessageA") called from "WS2_32.DLL" at address 0x71AC23B1 and returned 0x7E42AAFD by thread 0x770. 00:43:08.157: GetProcAddress(0x7E410000 [USER32.DLL], "PostMessageA") called from "WS2_32.DLL" at address 0x71AC23B1 and returned 0x7E42AAFD by thread 0x770. 00:43:08.157: GetProcAddress(0x7E410000 [USER32.DLL], "PostMessageA") called from "WS2_32.DLL" at address 0x71AC23B1 and returned 0x7E42AAFD by thread 0x770. 00:43:08.219: GetProcAddress(0x7E410000 [USER32.DLL], "PostMessageA") called from "WS2_32.DLL" at address 0x71AC23B1 and returned 0x7E42AAFD by thread 0x770. 00:43:08.672: First chance exception 0xE06D7363 (Microsoft C++ Exception) occurred in "KERNEL32.DLL" at address 0x7C812FD3 by thread 0x698. Let me know if these error codes are completely worthless to you hehe.
Unfortunately they are worthless as these are exceptions occurring with the client, not something the server can remedy. Since we can't reverse engineer the client or recode it (or at least not yet) there's really nothing we can do.
