zone fails to load
i am trying to edit spawns and stuff in a specific zone. something happened along the way and now im getting the following error
[Error] Error in LoadSpawn2 query 'SELECT id, spawngroupID, x, y, z, heading, respawntime, variance, pathgrid, _condition, cond_value FROM spawn2 WHERE id=58855 ': Error in LoadZoneState: spawn2_loaded[174] == 0 [Error] Loading zone state failed. Zone->Init failed [Debug] [ZONE__INIT_ERR] Zone bootup FAILED! not really sure what is going on here |
From a quick glance at the code, the way that can fail if is:
Code:
SELECT id, spawngroupID, x, y, z, heading, respawntime, variance, pathgrid, _condition, cond_value FROM spawn2 WHERE id=58855 That query on a standard PEQ DB returns this: Code:
mysql> SELECT id, spawngroupID, x, y, z, heading, respawntime, variance, pathgrid, _condition, cond_value FROM spawn2 WHERE id=58855 ; |
erasing it
so is there a way i can stop the zone.exe from even lookfor this entry?? I've changed that id number to a totally differnt number altogether and i dont want the old id even being checked for
|
error
so is there a way i can stop the zone.exe from even lookfor this entry?? I've changed that id number to a totally differnt number altogether and i dont want the old id even being checked for. This didn't happen with any of the other changes i made to spawns in a zone. (what i was doing was moving all spawngroup, spawnentry and spawn2 id's to a differnt range) this error happened with this last mob spawnpoint i edited.
|
try
Code:
truncate zone_state_dump; |
wonderful
that is wonderful. my zone now boots up. what exactly did this command do??
|
You had PersistentZoneState set to 1, which saved all the spawns that where up when the zone last closed down. You then must have deleted one of those spawns, and when the zone next booted up, it tried to load the spawn from the last saved state and couldn't find it in the spawn2 table.
The truncate command just cleared out the saved zone state. EDIT: I missed your post where you changed the spawn IDs, that would cause a mismatch between the spawn tables and the saved zone state which would also cause this problem. |
All times are GMT -4. The time now is 10:00 PM. |
Powered by vBulletin®, Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.