Monthly Archives: August 2009

Another Editor Update

Two zone editor updates in 24 hours — I’m on a roll here.

Here’s what’s changed in version 0.42:

— Select list dropdown now updates its text on navigate (< and >) for all object types.
— Fixed a save-on-navigate issue that caused some information loss.
— Set edit windows to have controls disabled when no items exist for editing.  This will prevent editing empty objects (which there would be no way to save).
— Can now delete items of all types, not just mobs.
— “Known Issues” has been added to the help menu.  It will show what I know is broken.
— Use flags and wear flags on objects can now be edited via the flag editor window.

You can get it here.

An Update To The Editor

I admit it.  The last release of the zone editor (0.40) was pretty much unusable.  This one (0.41) should be quite a bit better.

Things fixed/improved in this version:

— Will now rebuild item select drop down list on create new items for all types.
— Resets, shops, and quests now save current item on navigate forward/backward.
— Current edit window contents were not saved when clicking “new” for all types.  They are now.
— Rooms and objects would not autonumber.  They do now.
— Update status bar on add new items for all types.
— Fixed crash on clicking greyed out ‘edit special’ buttons.

Ignore the little brown boxes that show up on the map window.  I started working on map generation from the room list, but it’s nowhere near done yet and will look completely wrong for now.

You can get it here. Feel free to report any bugs/glitches/inconveniences. One known issue is that the “delete” buttons aren’t functional yet (if you create a room, shop, or obj you’re stuck with it for now :P)

I Must Be Cursed

It’s bad enough that I can’t run Windows natively on either of my computers. Well, now the Vista virtual machine on my laptop is hosed up and bluescreens on boot up. This wouldn’t be such a big deal, but that VM has the most recent version of the Basternae codebase. If I can’t get it working, I lose 2-3 days of work, including all of the changes/fixes for the test that I posted about a few days ago.

Does this mean that my WinXP laptop at work is next?

Test Port Turned Off Now

The experiment is over for now. I more-or-less have the data I was looking for — what the most major issues are, where the crashes happen, what’s super-broken, and what needs a lot of work.  If you have any other results from your experimentation, feel free to send them to xangis at the yahoo email service.  Thank you for what you’ve sent in so far.

The main crashy issues have to do with object deletion and some odd who list thing.  I’ll have to get those sorted out before the next test, whenever that is, but it shouldn’t be too tough.

After this batch of issues is worked out I’ll have to think about finding someone to be zone chief, and/or someone to be the highfalutin’ potentate of overlorditude.

Removing Hard-Coded Rooms, Objects, and Mobs

The old codebase had plenty of references to hard-coded room numbers. For instance, “Limbo” and the “default start room” for races without hometowns were set to room number 200.

Well, having those etched permanently into code is a bad idea, since it ties you inextricably to certain specific area files, and more importantly, it forces “zone gods” to dig into code if they want to change some things with how rooms are used. Bad idea.

The interim solution I’ve come up with isn’t great, but it does at least take the specific numbers out of code. I’ve created some XML files that load at boot time: StaticRooms.xml, StaticObjects.xml, and StaticMobs.xml. They contains a list of room, object, or mob names and their numbers, storing them in a Dictionary type. This makes it easy to refer to “ROOM_NUMBER_START” or “ROOM_NUMBER_LIMBO” in code and not worry too much about where it actually points. Of course, those names are still hard-coded, but at least they can be administered by non-programmers now.

I’d like to have them load dynamically as part of the zones, but there’s a bit of a problem there — some bits are just far too tightly integrated, especially things that revolve around locations, such as shifting to the astral or prime material plane. Those problems are better tackled in a future design change. This incremental improvement is good enough for now.

A Batch of Fixes

Between tester reports and the logs I’ve managed to track down and fix a handful of issues, some of which were so nasty as to make things untestable.  Here’s the list:

1 – Fix for removing an object from a room when that object points to a room but the room does not have the object in its content list.
2 – MUD now automatically creates player directories on boot if they don’t exist.  There was a problem with saving players when that dir didn’t exist yet that caused at least one crash.
3 – Changed “_name” to “name” at the login prompt.
4 – Fixed a crash bug that caused the world to explode when some spellcasting classes (i.e. Psionicist) entered the game for the first time.  It was a problem with setting initial spell proficiency values.
5 – Fixed a problem with the way age and total playing time was calculated.
6 – Fixed a problem where the petition command would make the MUD explode by calling itself.
7 – Fixed a problem with “get all”.
8 – Fixed a problem with clearing a mob’s hate list when it is killed.
9 – Fixed a glitch that would occasionally come up when taking an object out of another object.

Please try again and keep the observations coming.

InnoSetup Is Most Excellent

For a couple months back in 2003 I had a full-time job doing nothing but building InstallShield installers.  It was a pretty arduous process even for simple applications.

I wanted to build an installer for the Basternae Editor, which is a very simple program in that it doesn’t need any registry entries, license keys, services, or database objects.  It’s just data files and an executable.

This means that I really didn’t want to fire up my ancient (2003) copy of InstallShield to build an installer.  Instead I decided to give InnoSetup another chance.  I had tried it back when it was “brand spankin’ new” and didn’t really care for it, but that was a very very long time ago (before 2003).

I downloaded Inno Setup 5 and within minutes I was building an installer for the Basternae Editor.  I just ran through the wizard, added my files and executables, and fired it up.

Well, things were a little off on the first try — I wanted to run my app from the /bin directory and not the root program install directory.  Easy enough, the paths were right in front of me and I changed “{app}” to “{app}\bin” where it needed to be changed.

Next I found that it wasn’t using the executable’s directory as the working directory.  Yet again this was easy — I just added WorkingDir: “{app}\bin” to the icon setting and I’m good to go.  Total time spent building the installer, including Google searches and test install/uninstalls was about half an hour.  Nice.

The true test is whether it’s easy to maintain an install script.  I made a new build of the Basternae Editor today and wanted to update the installer.  The editor had no functional changes, just icons added to the menu so it’s a little clearer what button does what.

So I fire up InnoSetup, change the version at the top of the script from 0.39 to 0.40, hit “compile” and let it do its magic.  Seconds later I have a working install.  The best part is that this install cleanly installs over the top of an existing install, updates the listing in add/remove programs, and is COMPLETELY HASSLE FREE, a concept that was pretty alien to me given my InstallShield and WISE Installer experience.

So, here’s the new build of the Basternae Editor:  http://www.basternae.org/Basternae3EditorSetup_v0.40.exe

Basternae 3 Test Port Currently Running

I have a test port of Basternae 3 running on basternae.org port 4502.  This is only temporary for the purpose of testing.

Here’s a list of things that need to be tested.  Feel free to spend as little as 1 minute testing, or as long as the server is up.  I only plan to have it up for a few days or less.  Please report any results to xangis at the yahoo dot com email service.  One big email is far better than lots of little emails.  Also let me know the name you’d like to be listed in the credits as (up to you whether you want to use your handle/nickname or your real name).  As I receive testing reports I’ll post what sections of this list have been covered so there’s not too much overlap of effort between testers.

1. Tester: Create one character of each race and one of each class to make sure that:

– The help file/info is displayed properly for each race and makes sense.
– The help file/info is displayed properly for each class and makes sense.
– The character creation process is logical, sensible, and user-frieldy enough that someone who has never played a MUD could make sense of it.
– Nothing weird happens.
– Nothing looks too un-customized.
– You actually start in the Kobold Village instead of a room with no exits.
– Text formatting glitches are under control.

Report any ideas/suggestions/observances during the process.

2. Tester: Check help entries for all commands and report any that don’t exist.

The “commands” command will give you a list of the commands available.  “help <command_name>” should display the help for that command.

3. Tester: Check help entries for all skills and report any that don’t exist.

Type “skills” to show the skills available for your character.  “help <skill_name>” should display the help for that skill.

4. Tester: Check help entries for all spells and report any that don’t exist.

Type “spells” to show the spells available for your character.  “help <spell_name>” should display the help for that spell.

5. Tester: Test all spells available to you and report any that don’t work.

Until I have the “auto advance to max level” stuff going there’s not a whole lot you can test with this.  In addition, spellbook/scribe classes will have trouble.  Just do what you can.

6. Tester: Try all commands without arguments and report any that malfunction, fail to give any feedback, give badly-formatted responses, or give responses that look like a stock codebase.

For instance, try “score”, “attributes”, “who”, and any other commands shown when you type “commands”.

7. Tester: Try all socials and report any that malfunction, print output that is garbled or nonsensical, or looks like a stock codebase.

Type “socials” to get a list of the available socials.  Then try these different combinations with each social:
<social_name>
<social_name> me
<social_name> <some_mobile_in_the_room>

8. Tester:  Try combat and see whether you’re able to successfully kill a mobile.  If anything strange happens, report it.  This includes messages that don’t make sense, like getting kicked by a creature with no legs, bitten by a creature without a head, etc.

During the history of Basternae (1 through 3) there have been issues with combat round timing, corpse creation, and deathblows.  I’d like to identify any of those as early as possible.

9. Tester:  Try combat and see whether you’re able to successfully get killed by a mobile.

During the history of Basternae (1 through 3) there have been issues with combat round timing, corpse creation, and deathblows.  I’d like to identify any of those as early as possible.

10. Tester: Log in with two characters and see whether you can successfully kill another player in PvP combat.  If anything strange happens or if you’re unable to fight another player, report it.  Try with characters on the same racewar side (i.e. Troll vs. Ogre) and with characters on opposite racewar sides (i.e. Dwarf vs. Orc)

There’s all kinds of extra logic involved in PvP combat and there’s plenty of room for weirdness.

11. Tester: Check help entries for all bard songs and report any that don’t exist.

This assumes you’ll be able to create a Bard and that they actually have songs defined..  I haven’t tried.

12. Tester: Walk through a zone looking at mobiles, objects, and rooms and report anything that is formatted weird or doesn’t display properly.

Although issues of that nature are usually zone file related, it’s entirely possible that with our entirely-new socket and text formatting code that something will look wrong.

13. Tester: Download the Basternae client and try using it with Basternae 3.

It’s available here:  http://www.basternae.org/BasternaeClientPreview_08-04-09.exe

I know it’s only barely functional (none of the extra windows do anything yet), but it’d be nice to get a little feedback, and to know what it would require before you’d consider using it as your main MUD client (if you’d consider using it).  And, of course, if it doesn’t run on your main OS that’d be nice to know too.  It’s probably worth running it side-by-side with another MUD/telnet client to make sure that text comes across OK (it’s entirely likely that the text parser isn’t 100% right).  If anything looks wonky, screenshots might be helpful.

14. Tester: Download and try to use the Basternae zone editor and take note of what parts of it are confusing and/or unclear.

The basternae editor can be downloaded here: http://www.basternae.org/Basternae3EditorSetup_v0.39.exe

There isn’t any documentation for the zone editor yet, so it might help to have some input as to what a new zone writer would want to know how to do and what guidelines should be made clear.  If you’re feeling really brave you could write a basic conceptual overview or intro tutorial.

The editor currently only runs on Windows and requires the .NET framework (you’ll already have it if you have Windows).

15: Tester:  Download the Basternae zone editor and try creating a 2-3 room zone with a mob, a quest, and an object.

Just try it out and see if it works, offer usability suggestions, and/or report anything weird.  Once you’re done, send me the test zone and I’ll see if it actually loads in the MUD engine.  Quality does not count — this is only a test.  You could create an entire zone if you want to, but I don’t recommend it until after these tests are done because there could be some breaking file format changes.

A few things to be aware of:

The code was written and compiled on Windows and is currently running on Linux under Mono.  Since Mono doesn’t have full support for everything in .NET there’s a chance something will go haywire at some point.  While doing some initial testing a few weeks ago I saw CPU usage on the server spike to 100% for no obvious reason.  If this happens, I’ll have to kill the process because I have about 15 or so other sites running on the server and I can’t let them be taken down.

I’m sure some of these tests will not really be able to be run effectively without some code changes/fixes.

THIS IS NOT A FULLY FUNCTIONAL MUD.  THIS IS JUST SO I CAN BUILD MY “TO DO” LIST OF THINGS THAT MUST BE FIXED OR REWRITTEN.