It looks like there was a nasty bug in the zone converter for two of the three format types that we convert that caused the “wear flags” to be mapped into the “extra 2” flags.  The wearable flags include the “carryable” flag, so with those being broken, that’s why things could not be picked up in most (but not all) zones.

I spent some time on the zone editor today. Here’s a list of changes and fixes:

• Justice type is now selectable on the zone settings screen.
• In walkthrough mode, the ‘help’ and ‘commands’ commands now show a list of the available commands.
• Various minor text and appearance improvements, including adding a program icon.
• Added the ability to edit object values so you can actually set things like weapon damage amount or armor factor.
• Fixed a nasty bug in editing repops that would cause data corruption.
• Added the old Basternae 2 zone guides to the help file.
• Fixed a very nasty circular reference bug that would prevent a zone from saving in certain cases.

Repop editing is still pretty cryptic, but at least changes show up in the repop’s description in real time now.

The really confusing thing at the moment is editing object values. In DikuEdit, the values would change description when the object type changed so you could see what you were editing. The new editor does not do that yet, so you either have to already know what you’re doing or you have to guess, neither one of which could be much fun, so that’s going to be something fairly high up on the to-do list for future changes.

You can get the new version HERE.

Gharl was nice enough to grant permission to use his zones on Basternae 3.  This includes “The Church of Eternal Dusk”, “The Motte and Bailey of Duke Delwyn”, and “Zalkapfaan, City of the Headless”.   Thank you, sir.  Forward progress!

Generating maps on Basternae 2 was a bit of a pain.  It was done with about 1000 lines of hacked-together C code that I wrote that read in an ASCII file, asked you the dimensions and map type (surface, underdark, etc), and then brute-forced it into a simple zone file.  It was not elegant, but it worked, usually.  Unless, of course, you entered a wrong number, had an extra character on one line, or anything like that.

The surface map I showed yesterday is just an enlarged 120 x 50 bitmap.  I only used 9 colors when creating it — one for each terrain type.  There is no accompanying ASCII text file.

It’s entirely possible with a lot of grunting and swearing that I could convert it into an ASCII file which I could then import into that old C program.  Why bother?  There has to be a better way.  Turns out there is.

Last night I created a small application that does one thing and only one thing — generates maps for Basternae.

Here’s how it works:

1. Load in a bitmap of any size.
2. Select a menu item and the program analyzes the bitmap and generates a list of all the different colors used in it.
3. Use that list to generate a room template for each color — title, description, and terrain type.
4. Let the user edit the list of templates so you can say light green is “The Forest of Evil” and dark green is “Drachenwald Forest”.
5. Select another menu item to have the program use the template file as it goes through the image pixel by pixel and generates a room for each pixel.

The obligatory screenshot:

I’m a bit surprised that it only took a couple hours to write.  It’s the sort of thing that the serialization, bitmap, list, and datagrid classes built into .NET make very easy to do.

It is missing one major thing — it doesn’t connect the rooms together via exits yet.  That will be easy enough to add (probably about an hour to do).  It does, however, generate a zone that loads into the editor and can be tweaked and refined further.

There’s also one neat thing about the design — the room templates can be saved off to a file and loaded again, so you don’t have to edit it all in one sitting, risk losing your work if the power goes out, and can use the same room definitions with different image variations (provided you used the same colors).

I have a few goals with the Basternae 3 surface map:

1. Has to be fairly small. No epic 90,000-room maps that take half an hour to get to the next zone.
2. Has to have both raidable and non-raidable sections. The raidable sections should be easy to get to for both sides. The non-raidable sections should be more-or-less “safe”.
3. Should be contiguous — no randomly-spaced islands, be they large or small.

In short — I want it to be small enough that the world doesn’t feel empty when there are only a few people on, but large enough to have room a good number of zones, and for people to chase each other around a bit.  If there is an error to be made in sizing I’d prefer to err on the side of too small.

Here’s what I’ve come up with. It’s subject to modification, of course, but it captures the general idea:

It will be a while before it’s in the game, so it may evolve. There will also be cavern (underdark) map at some point.

I’ve finished converting two zones and attached them to the MUD:

Yurgoth’s Estate by Sarlac
The Defense of Longhollow by Drevarr and Ilshad

For now they’ve been attached where the Gypsy Encampment meets the Kobold pond.  Things will of course move when we get world maps in place.