Debugging - Loading Errors
Assuming that everything went smooth commiting the files to test, and the mob
and world files are converted, loading errors refers to anything that happens
when you reboot that prevents the mud from coming back up. You should ALWAYS
leave the mud up and running when you're finished, if you can't figure out the problem
then comment out your zone from the appropriate files.
~/testmud/DMS.ERR Errors
~/testmud/lib/logs/log/debug Errors
~/testmud/DMS.ERR Errors
Run the SojC mobile/room converter on this zone,
ERROR! Mobile for for zone: areas/zones/calvault/calvault.mob has not been run through the mobile converter.
Wed Aug 20 18:51:15 2008::Run the SojC mobile/room converter on this zone, from areas/ type 'sojc -b [zone_name]
Mud crashed again, eh? [1] + Killed ./testboot
Either you haven't converted the file yet, or you've removed the first line from the file.
The .mob and .wld files (and only those 2) should have as the first line,
<*> File Version 1 <*>
Although the version # doesn't matter, that line must be there.
Duplicate room entry: (49112)Mud crashed again, eh?
Loading zone table.
Control Knobs: ........................................................................................................................
Loading rooms.
Duplicate room entry: (49112)Mud crashed again, eh?
There are 2 instances of 49112. Incase it wasn't obvious..
~/testmud/lib/logs/log/debug Errors
Mon Aug 25 00:11:11 2008::Error in boot quest: quester 49132, letter=#
Error in the .qst file, specifically for mob #49132. Note you can almost figure this out from the
DMS.ERR file because it would have stopped right before loading the quest for m49132.