I think I understand this better - and just to clarify , I would need to:
(I'm using an example zone -- mmca, The Forlorn Caverns)
(user specified version #1 as a starting source#)
(1) Find spawngroups from 'mmca' version#1, (I count 106) , and
make copies of these version#1 106 spawngroups.
-- Assign a new version # (user specified) into the 'spawn2' table field='version'.
(2) Find distinct NPC's in 'mmca' version#1,
-- Make copies of those NPC's.
-- Insert a version# in the version field. The user will specify which version# to use as a destination. (1-20 already exist in this case). Say the user selects a new version#21
(2a) Place these new npc's in the spawnentry table using the new spawngroup id's made before
--modify spawngroup with new spawngroup.id and add a new spawngroup.name
--spawn2.version=21, and add spawngroupID to = new 106 spawngroups
--spawnentry.spawngroupID set to new 106 spawngroups
--spawnentry.npcID change to new NPC's we made before
(3) Allow field editing as Trevius mentioned before in main tool
I think this looks right. The order of the workflow is/will be determined later, but I already looked at the db structure and see what's going on.
GeorgeS
|
Threaded Mode
