New Tool: Migrate NPC's (spells/faction/loot/spawn/move/items) from PEQ <=> Cavedude

[John Adams]

Originally Posted by zephyr325

npc_types.id: increment by 350,000 rather than 500,000
spawngroup.id: increment by 300,000 rather than 3,000,000
spawn2.id: incremebt by 125,000 rather than 500,000
npc_spells.id: increment by 300 rather than 5,000
npc_spells_entries.id: increment by 1,800 rather than 5,000
loottable.id: increment by 13,000 rather than 500,000
lootdrop.id: increment by 50,000 rather than 500,000
faction_list.id: increment by 1,000 rather than 5,000
items.id: increment by 100,000 rather than 500,000

I'm still not seeing the logic behind not using PEQ's standard ID numbering convention of zoneid * 1000 where applicable. There is no risk of running into their numbering scheme if this combined effort becomes "the new base" standard. I'd prefer my NPCs in zone 202 to start at 202000 - 202999.

Nice work, still. Very helpful scripting.

[John Adams]

Zephyr, one more thing. MySQL 4.1 doesn't seem to be handling this header line very well:

print FILE "-----------------------------------------------------------------------\n";

Likely the fact it doesn't think it's a comment due to no space after the first two "--"s.

I edited my .pl and re-ran the scripts and MySQL can import the file ok. Not sure if this is everyone, or just my version (MySQL - 4.1.20-community-nt).

[zephyr325]

Originally Posted by John Adams

Zephyr, one more thing. MySQL 4.1 doesn't seem to be handling this header line very well:

print FILE "-----------------------------------------------------------------------\n";

Likely the fact it doesn't think it's a comment due to no space after the first two "--"s.

I edited my .pl and re-ran the scripts and MySQL can import the file ok. Not sure if this is everyone, or just my version (MySQL - 4.1.20-community-nt).

Whoops - thanks for the catch.

I've patched the program and re-posted it.

[John Adams]

Excellent. Thank you again for this. This script kicks ass!

[zephyr325]

Originally Posted by John Adams

I'm still not seeing the logic behind not using PEQ's standard ID numbering convention of zoneid * 1000 where applicable. There is no risk of running into their numbering scheme if this combined effort becomes "the new base" standard. I'd prefer my NPCs in zone 202 to start at 202000 - 202999.

Nice work, still. Very helpful scripting.

Understood - that would be a nice "next feature"; currently, I'm not trying to look at the npc_id's field at that detail to see what would be the next available ID number. To make it simpler (for me!) I just found a range for each table that would work with both the Cavedude and PEQ databases. We'll see what I can do on that front, as it's already got a "all mobs in this zone" mode.