Hey guys. I've had problems with one of the characters who regularly plays on my server (and has for over six months) repeatedly crashing upon trying to load.
This poor girl has put up with her buggy bard for ages, and it really hurts me that she has so many problems and that I can't help her. I've tried nearly everything. I'm going to give the list of all the fixes I've tried, and of the recent error messages that I have been able to find.
I'll say now that typically she will crash between the character select screen and actually loading into the game. Lately, she's been taking an entire zone with her when she does it. In fact, I've looked many, many times in the past and never seen any weird indications in the logs. This is the first time I have, and I'm pasting it here now:
Quote:
[01.30. - 22:56:53] [WORLD__CLIENT] New connection from 216.68.234.122:49734
[Trimming this next section down... It's a lot of lines and won't let me post it all.]
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: Tried patch Live_zone, and it did not match.
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: First opcode 0x7752 did not match expected 0x2792
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: Tried patch 6.2_world, and it did not match.
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: First opcode 0x7752 did not match expected 0x4dd0
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: Tried patch Titanium_world, and it did not match.
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: First opcode 0x7752 did not match expected 0x61c9
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: Tried patch Anniversary_world, and it did not match.
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: First opcode 0x7752 did not match expected 0x61d6
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: Tried patch Anniversary_zone, and it did not match.
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: First opcode 0x7752 did not match expected 0x2154
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: Tried patch Live_world, and it did not match.
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: First opcode 0x7752 did not match expected 0x7772
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: Tried patch Live_zone, and it did not match.
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: First opcode 0x7752 did not match expected 0x2792
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: Tried patch 6.2_world, and it did not match.
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: First opcode 0x7752 did not match expected 0x4dd0
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: Tried patch Titanium_world, and it did not match.
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: First opcode 0x7752 did not match expected 0x61c9
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: Tried patch Anniversary_world, and it did not match.
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: First opcode 0x7752 did not match expected 0x61d6
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: Tried patch Anniversary_zone, and it did not match.
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: First opcode 0x7752 did not match expected 0x2154
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: Tried patch Live_world, and it did not match.
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: First opcode 0x7752 did not match expected 0x7772
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: Tried patch Live_zone, and it did not match.
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: First opcode 0x7752 did not match expected 0x2792
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: Tried patch 6.2_world, and it did not match.
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: First opcode 0x7752 did not match expected 0x4dd0
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: Tried patch Titanium_world, and it did not match.
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: First opcode 0x7752 did not match expected 0x61c9
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: Tried patch Anniversary_world, and it did not match.
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: First opcode 0x7752 did not match expected 0x61d6
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: Tried patch Anniversary_zone, and it did not match.
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: First opcode 0x7752 did not match expected 0x2154
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: Tried patch Live_world, and it did not match.
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: First opcode 0x7752 did not match expected 0x7772
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: Tried patch Live_zone, and it did not match.
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: First opcode 0x7752 did not match expected 0x2792
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: Tried patch 6.2_world, and it did not match.
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: First opcode 0x7752 did not match expected 0x4dd0
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: Tried patch Titanium_world, and it did not match.
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: First opcode 0x7752 did not match expected 0x61c9
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: Tried patch Anniversary_world, and it did not match.
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: First opcode 0x7752 did not match expected 0x61d6
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: Tried patch Anniversary_zone, and it did not match.
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: First opcode 0x7752 did not match expected 0x2154
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: Tried patch Live_world, and it did not match.
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: First opcode 0x7752 did not match expected 0x7772
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: Tried patch Live_zone, and it did not match.
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: First opcode 0x7752 did not match expected 0x2792
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: Tried patch 6.2_world, and it did not match.
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: First opcode 0x7213 did not match expected 0x2ec9
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: Tried patch 6.2_zone, and it did not match.
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: First opcode 0x7752 did not match expected 0x4dd0
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: Tried patch Titanium_world, and it did not match.
[01.30. - 22:56:53] [NET__IDENT_TRACE] 216.68.234.122:49734: First opcode matched 0x7213 and length matched 68
[01.30. - 22:56:53] [NET__IDENTIFY] Identified stream 216.68.234.122:49734 with signature Titanium_zone
[01.30. - 22:56:53] [WORLD__CLIENT] New client from 216.68.234.122:49734
[01.30. - 22:56:53] Client 'Tissi' was destroyed before reaching the connected state:
[01.30. - 22:56:53] The rest of the zone contents were successfully sent, waiting for client ready notification.
|
The first question is, I see that spam quite often; is that something wrong right there? Is there anything I can do to fix it? I know that it should normally try six times, once for each client. But seeing it repeatedly like that, is there something I can tweak to correct it?
The real question, though, is the highlighted portion. That's the first time I've ever seen that, and I've no idea what it means or if it's an indicator of how I can fix her.
So far, the fixes have included:
- #movechar to a different zone and have her log in again. This works maybe 10% of the time.
- Deleting her Character_Server.ini and UI_Character_Server.ini files for the character. This works maybe 30% of the time.
- Remaking her character. This stopped the issue for a short time.
- Rebooting the server (which I do if no one else is around but us). Maybe a 20% success rate.
- Rebooting her laptop.
She has two other accounts played from the same machine that never exhibit issues like this at all. They all run from the same EQ folder. No one else on the server experiences issues like this. This issue persists with both the 0.6.2 client and the Titanium client.
I'm about at the end of my rope on this one, and feel like a shitty GM. My only other suggestion is for her to reinstall Titanium. Any other ideas welcomed.
And forgive me for not posting any server setup or other pertinent information, but of all those playing on the server, she's the only one glitched like this. Damn bards.
Repeatedly Crashing Character:
Threaded Mode
