Tool: Migrate NPC's (ID, Spawn, Loot, etc). from Lucin DB to Current EQ

Zengez · #1 08-13-2006, 11:01 AM

possibly a silly question but... does it work in reverse? (i.e. take mob info from eq DB and insert it into PEQ db?)

Angelox · #2 08-13-2006, 11:06 AM

Quote:

Originally Posted by Zengez

possibly a silly question but... does it work in reverse? (i.e. take mob info from eq DB and insert it into PEQ db?)

I don't see why not , just so long as the Databases you use , have all the updates to what ever version EQEMU he's using.

zephyr325 · #3 08-13-2006, 02:45 PM

Found out my key problem is that the records you pull from the PEQ Lucin database sometimes steps on key fields in the exising Cavedude's database, so you can't just take one and move it over. I'm trying to work through how to do that key field adjustment in a systematic fashion.

#4 08-13-2006, 03:15 PM

moved to correct forum

Zengez · #5 08-13-2006, 03:40 PM

I just recently successfully added all the spawns from cavedude's database into PEQ's.... i took all teh differing id's multiplied all the unique id's by 1000 (except spawngroupid which i did 100 for lack of character space) and pulled them over, no overlaps, no problems sourced in perfect first try.

zephyr325 · #6 08-13-2006, 03:47 PM

Sent you a couple of PM's about that - shoot me a note in email or I'm zephyr325@hotmail.com on msn chat.

zephyr325 · #7 08-14-2006, 04:18 AM

I've put the tool back up at the link above. It is working fine.

The issue this script doesn't handle is sourcing records from PEQ to EQ (Cavedude) where there is a key field already in use. It assumes those records will work correctly based off of the id's that are in PEQ. It looks like a lot of the later zone's NPC's will work fine as there isn't a crosseover between those two. It can also be useful if you just want to pull specific items from one to the other format as there are a few slight differences in the npc_types table between the two databases.

I'm still going to work on a programmatic way to adjust the key field's ids, hopefully in a way that will allow future PEQ updates past lucin to come in cleanly. Its also going to handle some of the other differences (i.e., spell tables are different, etc.).