If you are planning to do your own collect for a zone your database already has spawns for, then you need to nuke the existing entries in your database.
By default, the extractor uses insert IDs (for npc_types, spawngroup, spawnentry, spawn2, gridid, merchantid, groundspawns and objects) of the form <zone id number>000.
So for example if you had a collect for freeportwest, the ids would start at 383000.
The generated SQL includes deletes for these ranges, e.g 383000-383999, however. PEQ uses the same convention only for npc_types, so when replacing a PEQ zone, you need to manually delete the existing entries from the other tables yourself, e.g.:
Code:
delete from doors where zone like 'freeportwest';
delete from spawngroup where name like 'freeportwest%';
delete from spawnentry where npcID >= 383000 and npcID <= 383999;
delete from spawn2 where zone like 'freeportwest';
delete from grid where zoneid = 383;
delete from grid_entries where zoneid = 383;
delete from ground_spawns where zoneid = 383;
delete from object where zoneid = 383;
If you don't do this, you will likely end up with the zone being populated both with the spawns from your packet collect, and the spawns that were already in the database.
I don't know if that is what happened to Vampire1212, but it is the only way spawns would be anywhere else other than where they should be (unless a patch has bugged the collector, but I am pretty sure I did a test import after the last live patch).
Threaded Mode
