And I even said traps would follow the versioning concept, but hadn't tested it.

Here's my progress on this beta version -


NPC and Loot Editor
08.22.04 - Incorporated a Zone & Adventure Editor - under special window menu. This is used for Adventure zone copying and also for normal zones


SO, I tested the tool under the PEQ mirc and mmca zones - and it appears to work fine. NPC's are copied as well as spawngroups. There's a function to delete 'old' versions - this will wipe the relevant version NPC, spawngroup,spawn2 and spawnentries. I also tested it for copying a 'normal' zone - such as oasis version '0', and it does it fine.

There's no "special" editing of npc stats yet, and as Trevius mentioned, the version# will be included for editing. version # now appears in the last field in the main window. You can filter out the unwanted versions if you want.

btw - it's a beta still, and things will break if your there's a missmatch between spawnentry,spawn2 and related NPC's. The program has error checking built in, and whenever an error occurs, I found the best thing to do is delete that version, and figure out why it happened.

GeorgeS

Thanks for working on this tool!

Unfortunately, I've run into a problem. Whenever I work on a new instance, I wipe spawn2, spawnentry, spawngroup, and npc_types so the only data in those tables are the zone I am currently working on. In this case, I have 30 npc_types (all set to version 1), 30 spawngroup entries, 30 spawnentries, and 120 spawn2 entries (all version 1.) The version populates fine in-game, and I am seeing 120 spawnpoints all properly placed.

Identify reports:

Anyway, I change the New Version # to 2, and hit Start Process. I get "Error in Spawngroup Table. Looks like a reference lookup error." and then "Error in Spawn2 Table. Looks like a reference lookup error." Here is the output:

The NPCs all copy beautifully. I see 30 new spawnentry entries, 1 for each NPC created. Only the first gets assigned a spawngroupid, which is correctly the next available spawngroup id. The rest are left at 0. No spawngroups or spawn2 entries are created/copied. I'm not sure what could be wrong as the DB is as basic as we can get. If you want, I can post my DB tables to help troubleshoot.

Hi Cavedude, please send me a link to download those related tables that are causing the problem. I'll source these in and take a look.

npc_types
spawngroup
spawnentry
spawn2

I'll know the problem once I take a look at this - and code in fixes.

Thanks
GeorgeS

Here you are. Thanks! http://projecteq.net/spawn.sql

Ok, I wiped
npc_types
spawngroup
spawnentry
spawn2

then sourced in your 4 tables in the zip - that went fine.
With the most recent version of the tool, there's a great deal of debugging built in - Your mmcd zone version 1 will show the following -
(I made the version 2 with the tool)


Let me know if this version helps, or if you get different debug data

GeorgeS

Rats, still getting the same exact errors as before. I do however get all OKs on the identify screen. It looks exactly like yours except for the single version. Would you mind sending me your table schema for those 4 tables? That's about the only thing it could be at this point. I reset my auto_increment on spawn2 and spawngroup to no avail, not sure what else it could be.

I exported the schema with drop tables before inserts so you can get an exact copy
cavedude_schema.zip
Since you report the program reported all 30 spawngroups -were linked ok, it most likely must mean an index problem - as in auto-increment is on.
My program looks at the last index then adds 1. Everything created after that uses this index reference, till it's done.
If this method does not work, then a last index method needs to be called each time it tries to write data.

If it still fails using this exact schema, then I think I will have to rewrite the way I query and write indices.

you can quickly check if this works -
use the number from the previous query into the next one - replace the 51963-51965 with the your value, and increment+1

if it works, then the problem is something else

Thanks for helping,
George

Thank you! I've found my problem, but I am not certain why it's an issue. Before, I was connecting to my MySQL 5.0 database that was being served from a Linux box. It didn't work with my schema or yours despite everything being OK. However, once I moved the database to the same box as the editor, it worked perfectly. I'm not certain if it's a Linux/Windows difference, or the editor just doesn't like connecting to a database on a different host. Either way, it's working great now and I can get back to the grind! Thank you very much for this tool, even in its current state it will save me a TON of time!

That's great it works in Windows - I spent a better part of the day working on this and think that differences are capitalization of specific tables. For example "SELECT * FROM Spawnentry" will fail, where "SELECT * FROM spawnentry" should work in Linux. It's fixed in the recent revision.

Anyway - version .07 is the recent one which has more optimisation done.

GeorgeS

Yeah, in linux, everything is case sensitive.

Got a chance to try this, it now works perfectly when the DB is hosted on Linux!

When trying to copy I'm getting runtime error 3265 "item cannot be found in the collection corresponding to the requested name or ordinal"

Tried several zones, and getting that everytime.

Any ideas?

Bah sorry can't edit...I just realized I'm getting this error with the latest version of the tool trying to pull up any zones. I'm not completely sure what version I had before(think it was .03) but it was working fine.

Sorry, which tool is this for and what part of the tool crashes?

GeorgeS