Disconnect on Death

[Perenti]

I'm having an issue where when a char dies they go linkdead. I've searched the forums, and (i) it doesn't seem to depend on the GM flag being set and (ii) it is independent of what zone I'm bound in.

I'm using the Titanium client, my own server, std build but with newer perl libraries (I had to comment out the linux code and preprocessor directives in the perl parser code in zone), and with a random loot drop on some mobs (default.pl).

Using bots - makes no difference if they're up or not.

This client used to work (over 2 years ago).

Any ideas?

[lerxst2112]

Look in you logs for errors or clues.

[Perenti]

It seems (from the logs) that the zone is crashing. There's also a mysterious log entry:

9457 [12.22. - 20:01:09] [WORLD__CLIENT] John: LS Account #3
9457 [12.22. - 20:02:34] [WORLD__CLIENT] John: Entering zone fieldofbone (78:0)
9457 [12.22. - 20:02:34] [WORLD__ZONE] [10] [fieldofbone] Setting to 'fieldofbone' (78:0) (Static)
9457 [12.22. - 20:02:34] [WORLD__CLIENT] John: Sending client to zone fieldofbone (78:0) at 127.0.0.1:7009
9457 [12.22. - 20:02:34] [WORLD__CLIENT] John: Client disconnected (not active in process)
9457 [12.22. - 20:04:45] [WORLD__ZONELIST] Removing zoneserver #10 at :7009
9457 [12.22. - 20:04:45] [WORLD__ZONELIST] Hold Zones mode is ON - rebooting lost zone
9457 [12.22. - 20:04:45] [WORLD__ZONELIST] Rebooting static zone with the ID of: 78
9457 [12.22. - 20:04:46] [WORLD__LAUNCH] zone: fieldofbone reported state STOPPED (2 starts)
9457 [12.22. - 20:04:55] [WORLD__LAUNCH] zone: fieldofbone reported state STARTED (3 starts)
9457 [12.22. - 20:04:57] [WORLD__ZONE] New TCP connection from 127.0.0.1:45108
9457 [12.22. - 20:04:57] [WORLD__CONSOLE] New zoneserver #11 from 127.0.0.1:45108
9457 [12.22. - 20:04:59] [WORLD__ZONE] [11] Zone started with name fieldofbone by launcher zone
9457 [12.22. - 20:04:59] [WORLD__ZONE] [11] Auto zone port configuration.  Telling zone to use port 7010
9457 [12.22. - 20:04:59] [WORLD__ZONE] [11] Setting to 'fieldofbone' (78:0) (Static)
9457 [12.22. - 20:04:59] [WORLD__ZONE] [11] [fieldofbone] Broadcasting a world time update
9457 [12.22. - 20:08:13] [WORLD__CLIENT] New connection from 127.0.0.1:57747
9457 [12.22. - 20:08:13] [NET__IDENT_TRACE] 127.0.0.1:57747: First opcode 0x4dd0 did not match expected 0x2792
9457 [12.22. - 20:08:13] [NET__IDENT_TRACE] 127.0.0.1:57747: Tried patch 6.2_world, and it did not match.
9457 [12.22. - 20:08:13] [NET__IDENT_TRACE] 127.0.0.1:57747: First opcode 0x4dd0 did not match expected 0x2ec9
9457 [12.22. - 20:08:13] [NET__IDENT_TRACE] 127.0.0.1:57747: Tried patch 6.2_zone, and it did not match.
9457 [12.22. - 20:08:13] [NET__IDENT_TRACE] 127.0.0.1:57747: First opcode matched 0x4dd0 and length matched 464
9457 [12.22. - 20:08:13] [NET__IDENTIFY] Identified stream 127.0.0.1:57747 with signature Titanium_world
9457 [12.22. - 20:08:13] [WORLD__CLIENT] Checking inbound connection 127.0.0.1 against BannedIPs table
9457 [12.22. - 20:08:13] [WORLD__CLIENT] Connection 127.0.0.1 PASSED banned IPs check.  Processing connection.
9457 [12.22. - 20:08:13] [WORLD__CLIENT_ERR] NOCLE: Bad/Expired session key '3'

[lerxst2112]

Does the zone log have anything useful in it? If it is crashing and there's no info in the log that's useful, the best bet it to catch the crash in the debugger so you can see what happened.