Zugg Software :: View topic

Newbie Joined: 18 May 2003 Posts: 2 Location: USA

After upgrading to 6.62, I've been playing with database features for the first time and started by trying to create a new zone in my .mdb map and annotate in that map what monsters were in the room and I rapidly ran into problems.

Problem #1: When I try to add new monsters to the database, when it asks me to enter what Zone the monster is in, the drop-down doesn't show newly-created Zones, only old Zones I created a while ago. Also, I tried saving my map files and database files, exiting and restarting Zmud and the database still doesn't recognize my 'new' zones.

Problem #2: When I created my second monster in the database, I had problems leaving the Zone entry blank. Whenever I do so, I get a little Zmud error window saying: "List index out of bounds (0)". Oddly, it didn't seem to complain about a blank zone for the first monster I created. I created a third monster and left the Zone field for it blank, and that was OK, but once I switched it to another value, saved it, then tried to switch it blank again, I got the same error. (I wanted to leave the entries blank so I wouldn't have to put in bogus old zone names rather than new ones since I can't put in new ones... at least not without switching the database field to something like plain text which kinda defeats the point of the Zone datatype.)

Problem #3: Well, I don't know whether this is really a problem (I don't care about it because I was just exploring, not trying to do something), but when I was playing around with options in the database tools, there's an "Actions" choice in the menubar, and the "Set Fields..." choice on that gives me an errorbox saying "Class DBSetD not found".

Any comments on how I'm doing things wrong, or confirmation that these need fixing would be appreciated. Thanks!

GURU Joined: 10 Oct 2000 Posts: 4379 Location: USA

The database no longer supports the new map format, so the Zone and Room field types for the database will no longer work correctly. A rewrite of the database module to a new format that does support the new mapper format is on the to-do list, but it went down a lot on the list seeing as how the mapper rewrite took so much more time than expected to complete. It's possible that in the future it might happen, but right now we should not expect it to happen.

So, you need another method of storing and using the information you need in the database. For your case, you can create a new text field in the database that will contain the name of the zone that has the monster. You may also use a field with a list, in which you have added all of the zone names, and you update each time you create a new zone. Finally, using the mapper functions and commands, or SQL, you can act upon this information by looking up the zone by name in the map's database, if one of your scripts needs it.

Kjata