Ok it looks like my problem with Feerrott is something else. I set it to launch in the launcher along with a dozen other zones. All the other zones worked. I am getting a problem with feerrott still not working.
The only thing I can think of is that I removed the powerful undead from the spawntables in feerrott because they were a nuisance for newbs. Could that have screwed up a script or something that would cause the zone to crash?
Here is the last part of zone-feerrott.log:
[Debug] [RULES__CHANGE] Set rule Zone:EnableMQGateDetector to value true
[Debug] [RULES__CHANGE] Set rule Zone:EnableMQGhostDetector to value true
[Debug] [RULES__CHANGE] Set rule Zone:MQWarpDetectorDistance to value 4900.0000000000000
[Debug] [RULES__CHANGE] Set rule Zone:MQWarpLagThreshold to value 140.0000000000000
[Debug] [RULES__CHANGE] Set rule Zone:MQWarpThresholdTimer to value 90000.0000000000000
[Debug] [RULES__CHANGE] Set rule[Debug] [WORLD__CLIENT] New connection from 72.50.164.134:60852
[Debug] [NET__IDENT_TRACE] 72.50.164.134:60852: First opcode 0x7752 did not match expected 0x2792
[Debug] [NET__IDENT_TRACE] 72.50.164.134:60852: Tried patch 6.2_world, and it did not match.
[Debug] [NET__IDENT_TRACE] 72.50.164.134:60852: First opcode 0x7213 did not match expected 0x2ec9
[Debug] [NET__IDENT_TRACE] 72.50.164.134:60852: Tried patch 6.2_zone, and it did not match.
[Debug] [NET__IDENT_TRACE] 72.50.164.134:60852: First opcode 0x7752 did not match expected 0x4dd0
[Debug] [NET__IDENT_TRACE] 72.50.164.134:60852: Tried patch Titanium_world, and it did not match.
[Debug] [NET__IDENT_TRACE] 72.50.164.134:60852: First opcode matched 0x7213 and length matched 68
[Debug] [NET__IDENTIFY] Identified stream 72.50.164.134:60852 with signature Titanium_zone
[Debug] [WORLD__CLIENT] New client from 72.50.164.134:60852
[Debug] AIYellForHelp("Dar_Guard_Lraktol000","a_water_mocc asin006") #Shin_Master_Grubbus000 attacking a_water_moccasin006 Di
|