NPC & Loot Editor revision

[GeorgeS]

Hi Trevius,

I think it is not a problem for the first request, adding spawns to multiple existing spawngroups.

For the second request, that is something I need to think over - how best to approach that. In any event, the first one should not be a huge task, and the supporting code is mostly there for this.
I'll code something up and see how it works..

GeorgeS

[trevius]

Sounds good. The first request was the main one. It isn't overly hard to adjust a zone with queries in most cases.

I was thinking a bit more about it and some ideas for loading respawn time into the main display are:

1. If there are varying respawn times with the same NPCID, you could just have it display something like 0 or -1 signifying that it varies.

2. To prevent extra load that may not be needed 99% of the time, you could have a checkbox or button to enable/disable the queries for respawntime to display, otherwise they are left blank.

[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.

[blackdragonsdg]

The same loottable issue is happening to me as well. The last time it worked correctly for me was when I was using base db rev1667 updated to 1753 with emu rev1753. It stopped working correctly after I changed the base db revision to 1751 then updated to database rev1753 using emu rev1753.

[Huppy]

Just wanted to say thanks for the awesome tools. I've been using the npc
editor for awhile now, and just tried out the spell import/export tool.
I have all spells in my DB up to HoT now thanks to that tool
And most of all it gave me some older missing spells, (such as Temerity).
Thank You.

[trevius]

Very awesome, GeorgeS! I love that we can now see all NPC fields

I will test out the new stuff and let you know if I see any issues or think of anything else. very nice update so far, though!

[Kayen]

If I run this on Vista/Windows7 I get the initial graphic with the start option, but it does not allow me click start, nor does it give any errors.

Previous version worked fine...

Any ideas?

Kayen

[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!