NPC & Loot Editor revision

[WkimWes]

Originally Posted by trevius

Not sure when this started, but I just noticed that in the version I am running of the NPC Loot Editor, and on Rev 1824 of the source, it seems something is wrong. When an NPC has a loot table, it shows in the correct column of the editor, but I don't see the loot table details at the top when the NPC is selected. I noticed if I click in that field, it says that they are "A Merchant!" at the top of the editor. Since the merchant_id field is to the right of loottable_id, I tried moving the loottable_id field to the mana_regen field to its left. After moving it, I could then see the loot table in the editor.

It seems that the fields all show correctly, but that the loot table display is linked to the wrong field in the list. The version of the editor shows 08.24.12.

I've had the same problem, I thought it was the dB until I actually dug deeper via the table entries. So that makes three, I think it started at 1751, I updated my dB with the latest peqdB rev.

[GeorgeS]

Definitely sounds like a schema issue- a shift in the field order most likely. I'll need to download and update to this db version to check the issue.

I'm working on this tonight, and I'll report when I discover the fix

GeorgeS

[GeorgeS]

Ok, discovered the problem, and it's easy to fix (short term), however whenever a schema change occurs, this will always break the tool. I have decided to rewrite the core schema decoding code to accept new schemas, but will take a few days to re-write. It's a big task, but should be better in the long run.


GeorgeS

[WkimWes]

Thanks George!

[GeorgeS]

I fixed the schema issue, and the program now checks database builds against itself, and won't run when a table issue is encountered.

I'm working on the spawngroup editor now - adding npc's to multiple groups at once, etc..and other features.


A build should be available saturday.


..I did notice quite a few field changes in the latest db build. Stuff like this will break every tool out there.

GeorgeS

[GeorgeS]

Mass editing and pruning of npc's in selected spawngroups now works!

What it can do?

You can search for all "bats" in zone=commons and then add/remove a npc of your choice.
You can search for all "bats" by either the word "bat" or a specific npc ID within a zone or global (all zones in game) and then add/remove a npc of your choice to the entire spawngroup set.

for example, If you create a high ranking "orc", you are able to add it to all selected spawngroups at one shot where npc name="orc" in the spawnentry table.

This is a feature Trevius requested, and I am working on the rest of the feature list now

GeorgeS

I have another request if it is possible and if you find the time to check into it. The request is to add a way to edit multiple spawngroups at once. What I am looking for is to use the spawngroup editor to search for all spawngroups for a single NPCID (which the tool already does). Then, to be able to add another NPCID to all of those spawngroups all at once. So, say the NPC I am looking up is a_bear, and I find that it has 10 spawngroups in the zone. Then, I want to add a_snake to all of those 10 spawngroups at once. Assuming a_bear was the only thing in the existing spawngroups, it would then just add a_snake to all of them and maybe allow setting a chance for the new a_snake to be added in with. If I set a_snake to be added with a 40% chance, it would adjust all of a_bear chances to 60%. If there are more than just a_bear in the original spawngroup, it would adjust all of the existing spawns to equal 60% chance total (by scaling each existing one down proportionately) and then add a_snake in at 40% chance still.

[GeorgeS]

NPC and Loot Editor
08.25.01 - Adding/Removing of NPC's to all selected spawngroups is added. Resetting respawntime to selected spawngroups is also added. Look in spawngroup editor under tools

Should be live in about 10 minutes

GeorgeS


..also built in is the new schema checker on the splash screen. If your npc_types table is different from what the program expects, it will not run.