Here's some LoY work for PEQ

[Angelox]

Thanks for all the help - Sesmar's query puts me on the proper track of thinking. The query/sort works well, but still has data spread out through the given table. What I need is, to put them in zone groups, for extraction.
I noticed in npc_types , theres a loottable_id column , and also the zone id is in npc_types.id ,as it appears the first numbers contain the zone in them - example : an entry in npc_types.id 224035 means the npc is from zone 224, and he's entry number 035. So, maybe I could use the zone data from npc_types.id , and loot data from npc_types.lootable_id to sort the other loot-related tables by zone?

[sesmar]

I am not exactly sure on how the PEQ does their numbering but I do not think an NPC can belong to a zone based on the npc_types.id because a given NPC can appear in any number of zones. Such as a Gnoll Pup can be in North Qeynos and Qeynos Hills.

In order to get Loot Table information for the mob in a particular zone you will have to start with Spawn2 to get all the Spawn Groups in that zone as any NPC that spawns in the zone will be an entry in a spawn group. Then you link to npc_types using the ID and from there to LootTable information which is spread out over multiple tables.

I used one query to display some of the information you need but my suggestion would be to write the query in stages pull out all the information from each table you need so you can reinsert the loot information with new ID's to fit your DB.

[Angelox]

Originally Posted by sesmar

I am not exactly sure on how the PEQ does their numbering but I do not think an NPC can belong to a zone based on the npc_types.id because a given NPC can appear in any number of zones. Such as a Gnoll Pup can be in North Qeynos and Qeynos Hills.

In order to get Loot Table information for the mob in a particular zone you will have to start with Spawn2 to get all the Spawn Groups in that zone as any NPC that spawns in the zone will be an entry in a spawn group. Then you link to npc_types using the ID and from there to LootTable information which is spread out over multiple tables.

I used one query to display some of the information you need but my suggestion would be to write the query in stages pull out all the information from each table you need so you can reinsert the loot information with new ID's to fit your DB.

Actually, the data I pulled from Cavedude's was what had the zoneID in the npc_types.id number - which is a very good idea . Maybe it was done for some other reason, but very effective in isolating the data by zone. It wouldn't be a bad idea to reserve the first three digits in the npc_types.id for the zone number - it also would be a good idea to include zone name in places like loottable.name and lootdrop.name; I'm going back through what I have done and adding this.

[GeorgeS]

I have added 'zonename_loottable_id' to the loottable.name in my editor. It uses that convention as default now, and allows you to change the default under tools menu.

As Sesmar mentioned, npc_id's are reused in many zones, so that convention in the tables is strictly for the datatable developers and may not apply to everyone. Also in the db, I see so many types of level 1 skeleton's it makes you understand why loottables and npc_id's should be shared. Although I do think Angelox's system of unique npc_id's for each specific zone is also a good idea to tracking and managing specific zone's mobs. I use both methods.


GeorgeS

[fathernitwit]

PEQ makes all NPCs start with zoneID*1000 (and I hope cavedude did this as well). So it makes finding some things easier. if a npc is in multiple zones, we have multiple copies of the NPC... mainly a side effect of packet collects. Anyhow, this is an established rule and can be used. Unfortunately, we did not make such a rule on any of the other tables... although an ambitious perl/php/python person could write a script to re-number all the loot tables and spawn tables base on some rules, which would make it a lot easier to dump entire zones in the future.

[cavedude]

Yep, I did the same thing with my NPCs. zoneID *1000

[tallerin]

I know that you can pull dumps from cavedudes database and source them into PEQ with out changing things and get no errors. I just spent yesterday and this morning dumping npc_types spawn2 spawn entry and spawngroup from cavedudes DB. Removed all spawns that were already in PEQ from cavedudes DB and sourced them into PEQ DB. Now i have PEQ DB upto luclin and all the other zones after luclin that are in cavedudes DB So best of both DBs combined now. Now just to do faction tables and loot tables for the newly added zones.

If the SQL files that i have dumped from cavedudes DB and weeded out all entries Of luclin and before will help you out let me know i'll find a place to upload them for you. Would make it easier on you then all you have to do is loot tables and faction for the zones.