Trial By Fire.

15 days left. The gameplay is done and in “test” (a bunch of friends are playing through it). Thus, I had that terrifying moment where you send out your creation to the world and hope that it works.

…then someone reports that there’s a serious bug which you quickly fix.

That’s how it goes.


The Gameplay Prototype

So when last we spoke, I had set my schedule. I had just a few short weeks to get a complete gameplay prototype running. So I started where every game developer seems to start: With the graphics.

I mentioned before that the graphics were simple. Polygonal, no textures. Writing that took about a day (very, very simple code). I checked it in on August 12th.

Next up: Input. No sense in gameplay if you can’t PLAY it. I took the input code that I wrote for my old NES emulator and modified it slightly for my new uses. That gave me automatic keyboard/joystick control.

Side note: Never initialize DirectInput after initializing Direct3D, because it does bad, bad things to the window interface. DirectInput subclasses the window, which Direct3D doesn’t like, so D3D doesn’t like to restore the state of the window correctly after doing a Reset (i.e. for switching between fullscreen/windowed).

Blah blah blah, wrote a bunch of stuff, got the gameplay test done. Only a few days behind schedule, on September 4th.

A Note on the Art Path

So, my original “art path,” as it were, was amazingly complex.
It kinda went like this:

  1. Create object in AutoCAD.
  2. Export from AutoCAD to .3ds
  3. Use a 3D modeling package to import the .3ds
  4. Manually fix up the incorrectly exported colors
  5. Export to .ase
  6. Run custom converter from .ase (an easily parseable ASCII file format) to my own mesh format.
  7. Profit!

This eight-hojillion step process was a pain and, moreover, had one fatal flaw in it.

Check out step number 3. AutoCAD was incorrectly exporting the object colors.

As it turns out, AutoCAD has the ability to set truecolor values to objects, but it also has a built-in 256 color palette (likely left over from the olden days). Now, when ACAD would export, instead of exporting my delicious true colors, it would export the nearest match in the color palette. Consequently, I had to fix them up later.

This became a problem when I tried to do my first test background – Fixing up all of the colors was way too time-consuming, so I had to find a better way.

FIRST I tried to import the DXF directly into the 3D modeler. However, it ALSO screwed up the import.
SECOND I tried to write my own DXF reader. As it turns out, the object that I’m using as my building block (the REGION) is one of the only TWO types of ACAD object that are encrypted in the DXF. Which is stupid.
THIRD I found a third-party program to convert REGIONs into PolyLines, which I WOULD be able to read. However, this program also dropped the same color information I was trying to preserve, thus ensuring that every last person in the universe has screwed up the color import/export with ACAD files.

The Solution!

I found out that AutoCAD has its own API for writing plugins called ObjectARX. Essentially, I downloaded it and wrote an export function from AutoCAD directly into my mesh format. It does the following things: Scan the scene for regions, and for each region it finds, triangulate it (using ear clipping) then write that to the file.

So now, my art path has become:

  1. Create object in AutoCAD
  2. Export directly to my mesh format, with correct colors intact.

Much better.


I don’t have any new screenshots. What I *DO* have are two of the songs from the game.

The first one is the song that will play during the main menu on game startup. It’s the piano version of the main theme.

Piano of Destiny

The second is the first-level music, which IS the main theme (thus, both songs have the same melody).

Theme of Destiny

Anyway, it’s amazingly late and I work tomorrow, so that’s all I have time for today. Backgrounds truly begin tomorrow!

Concept of Destiny

So, the Four Elements V contest was announced in June. The rules are simple: Create a game, include the four elements:

  • Europe
  • Emblem
  • Economy
  • Emotion

Have it done by November 30th.

That said, I thought “well, those elements sound hard, screw that.” And I went along my merry way. Sometimes after that, I moved cross country and started a new job. But I had been watching the forums, and I noticed a few things:

Everyone seemed to go “I can do that! I’m making a…” followed either by “RPG” or “Strategy/Simulation game.” I began to think about what I could do that would be DIFFERENT from anything else in the competiton. It took a week or so before I came up with an idea, but I did:

Mop of Destiny: Lead the Palace of Westminster’s Caretaker, Jack Scroggins, on an epic battle against the advancing armies of The Shadow. It’s essentially a 2D action/platformer, along the lines of the original Castlevania games.

The four elements were as follows:

  • Europe – I set it in (and beneath) the Palace of Westminster, with the final level being a frantic climb up the turning gears inside of the clock tower colloquially known as Big Ben.
  • Emblem – At the completion of each level, Jack must touch the Emblem of Light. Each emblem is a seal on the gate to the Shadow Realm, and must be re-activated by Jack.
  • Economy – Again, at the completion of each level, a spiritual shopkeeper will appear, allowing the caretaker to purchase (or sell) special weapons and healing items using the souls of enemies vanquished along the way.
  • Emotion – Instead of being able to physically harm Jack, the Shadows can only cause him to become more afraid. As he becomes more afraid, his perceptions of the surroundings change (the world becomes a bit less colorful), and he recoils farther and farther in horror. If he becomes TOO afraid, he loses his sanity and becomes a shadow himself, and the game ends.

Since I was moving, I did not really have computer/Internet access, so I spent alot of time jotting notes and drawing concept sketches of various worlds. Initially, there were to be 8 levels (though this has been pared down to 6 for time), starting in the Palace of Westminster, taking Jack through the caves leading to the gateway into the Shadow Realm itself, then on a quick, frantic escape from the Shadow Realm, and finally up the clocktower to do battle with the Shadow King himself.

I determined what the big “problem areas” of gameplay would be, and decided to frontload most of them, to ensure that I knew that I had a chance of finishing. The main problem area had to do with the final level: Jumping from gear to gear would require some crazy collision detection and platform motion response. So that became the first goal: to get a “Control Test” working. This would have a bunch of platforms for the main character (represented by a fantastically drawn rectangle) to jump around on, including horizontal/vertically moving platforms and a spinning gear.

By this point, it was near the end of July, and I knew I had to get started. I initially started working on a basic level editor. I made a decision early on that the graphics would be 100% polygonal. Excepting the render targets, there is not a single texture in the entire game. This made the graphics code easy (all of the major graphics code was written in about a day), and made level editing easy (each vertex is a 2D position and a color). However, the level editor soon proved to be very complex – an interface that would allow me to do what I wanted would be a real pain to design.

I did some tests with some 3D modeling applications, and none of them were as simple to use as I’d like. However, my wife is an interior designer, and has AutoCAD, which proved to be amazingly simple. It was exactly the type of 2D model/level editor that I needed (with one major exception that I’ll talk about in a later post). Thus, I scrapped the whole editor I’d been working on and switched over to using AutoCAD.

By this point, it was mid-August. I needed to really get started, and I needed to get started fast; my design was very ambitious, so I needed to get working. My schedule was set as follows:

By the end of August, I wanted to have a gameplay test, complete with moving gears and working controls.

By the end of September, I wanted all of the major subsystems done. Sound, music, fonts, levels, animation, enemies, the HUD, the ability to walk to the next zone in the level, stuff like that.

By the end of October, I wanted to have the entire game playable (only no art assets would be done). You’ll see in a moment that this didn’t entirely happen (I ended up doing all of the character art in October, because making the actual enemies would have sucked without their art).

then, finally, it had to all be done by the end of November.

Currently it’s November 14th, and I have just completed my first complete playthrough of the game. None of the background art is done, and only 2 of the songs are done, but the game is playable. I have 16 days to do all of the art (I’m not an artist, really), and the music (I am, however, a composer), and the voice acting (which I can do), and the sound effects.

It’s going to be rough, but I think I can do it.

And now, to some SCREENSHOTS!

Keep in mind, of course, that I have not done any of the background art, so the screenshots kinda look like decent sprites running around on an Atari 2600 playing field, but the background art is going to start to get done soon.

Click to enlarge

Anyway, I’ll be continuing to post about the history of the project through when I (hopefully) finish it ontime for a victorious first place!

Long time, no update!

So, wow. It’s been what…over a year? How time flies when life is throwing buckets at you.

Well, I’m going to start updating this journal with information on the (currently) continuing development efforts of my 4e5 entry entitled Mop of Destiny.

No, I haven’t given up on that racing game. Content creation got the better of me, but it’s not a dead project. I figured I had a chance to FINISH a 4e5 entry, so I switched gears a bit.

More info to come shortly (tonight).