Hitting Things

Here's some stuff I did this week:

We started with this screen shot on 10/14/12

We fixed some bugs. THIS ISN'T HOW IT HAS TO BE ANYMORE

We achieved this minor milestone

We revised our script substantially

We got to this point before I got totally sick and couldn't write coherent code

Everything is still bugged out with the AI file parser but it's really close. A couple more days of work and some stuff like adding placeholder SFX & music plus a title screen and I'll be done with WOL 1, cut a quick not-for-release demo to The Bosses, and ready to expand into WOL 2. "Now with interesting content."

Someone else post Gruedorf stuuuuuuff

AIiiiiie

A lot of work since last time, but not enough! I've gotten to the point where I need to code AI stuff, and there's a terrible niggling bug somewhere in the way the program loads AI strings into structures. I'd hoped to figure it out before posting this, but no luck, and I gotta do other stuff now. Here are some shots:

This is the prototype for a game design that hopefully can be made into something with maybe commercial legs. Since it's more important to get the central systems right than to do something super polished, I decided to approach this as a series of short games with progressively more complex designs. The first of which is pretty easy, basically a puzzle/tutorial, but getting it working requires having a lot of basic systems at least sort of operational. This image represents the ENTIRE MAP for the first game, and the ENTIRE CAST.

Here's new concept art via character artist Xerxes Verdammt, dropped wholesale into the game. Note the new big red arrow indicating which menu thing you've selected.

There are still a lot of bugs, however.

Stuff remaining to do on WOL 1 before I call it "done":

• finish the rest of the AI string loading
• debug the existing AI string loading
• finish writing, revising, and AI-coding the dialogue so the game is "complete" start to finish
• add whatever art comes in to the game
• make fun Pac-Man style title and ending screens

Then I think of a more complex design to make for WOL 2. I don't know how many it will take before I figure that the design is (1) done, and (2) fun. But right now it's enjoyable to work on!

(Oh, for those interested, I got interviewed. Mostly it's about like Scientology and Tarot cards.)

Rainbow Dash

I've been away, moving apartments, working on paying freelance projects, working on getting some really overdue creative stuff to various agents/associates. So here is some more of Mystery Project WOL. Not that much is impressive looking/visible, but some new stuff:

Slightly better use of old Chocolate Sauce tiles; brightening up the test map!

Why is there a menu full of random colors? What is this supposed to mean?

And finally, COPYRIGHT INFRINGEMENT IS CREATIVITY. Some kind of status menu, or possibly battle screen? What is this game going to be?

OH HEY ALSO: I've published a novel since last post! You can buy it here from the publisher, O/R Books! It's about quasi-Scientology cults and girls in love, and Eileen Myles likes it.

Menu + mean girl

Some work, not much. Here is a menu and a mean girl.

W. O. L., working title

COMPETITION ISN'T OVER

I got out of making video games altogether and mostly did some comics and such things. BUT a friend of mine is running a pretty neat game company and I have a pretty neat game idea, so I need to build a quick and dirty prototype to test out game logic and build up some sense of how the game will feel. WHAT BETTER TECHNOLOGY THAN VERGE?

As you can see I'm using old Chocolate Sauce assets and code like crazy. What does it mean that these people are rainbow colored? I have to remain more secret about this one, but will post screen shots here and stuff.

Let's Cut Our Losses

Sometime after the last post here my computer stopped booting forever, taking with it (1) my entire novel and (2) all of Chocolate Sauce RPG. After three months or so plus numerous attempts to get the data off of the hard drive and onto a bunch of temporary computers, I got together the money for data retrieval. The answer: if I pay $3,000 and have the hard drive shipped upstate to a clean room, there's a chance of recovering maybe 30% of the data in a raw format, meaning no directory structure, no file names, no file types. Basically fuck that.

Since that time I've managed to go through an additional temporary computer (still works, the screen just doesn't work.) I've reconstructed the novel, but there doesn't seem to be any point in working on a project like Chocolate Sauce when I can't afford a computer that doesn't completely bite and that will fail in a matter of months. I did have two backups: one on a USB drive that is now lost, and one on the Fiction Circus web server which is missing the last month or so of work I did on the game, mostly on graphics, maps, and fine-tuning battle/enemy spawn code. Basically a massively incomplete mess.

It's the latter that I'm releasing for the public curiosity as of this post, here.

Be advised:

• The battle system doesn't work at all. It looks like the only reason for this is that the enemy art directory is missing, so I guess if you edit enemies.dat (which contains the names of the image files for the enemies) you could try it out. Just change the lines that start with @ to any .pcx image file, ideally one around 40x40 px, and put that image file into a subdirectory of /gfx called /enemies.
  
• None of the title screen options other than "New Game" and "Debug Game" work.
  
• There's a major gameplay bug on choosing New Game: the controls won't be hooked up correctly after the opening scenes are over and the game gives you control. To see the menus/to use the map spells, go talk to the shopkeeper one house to the left of your starting location: once the shop script runs the controls get hooked up normally.
  
• You can play through the game up to the point where Illcup gives you your first assignment. After that you'll almost certainly end up getting into fights in the desert and the game will crash. If you want to see the rest of the story for this installment, cruise through the text_data folder; text_church.dat and text_cutscenes.dat have I think all of the story text and dialogue in the game.
  
• The map tiles aren't entirely finished for most maps and look terrible. The sprites aren't finished, most glaringly on Cass.
  
• The music files are copyright Long Dao; do not use them without asking him. If the enemy graphics are somewhere in this zip file at all, they're copyright Xerxes Verdammt and shouldn't be used without asking her. (Some of them are just ripped temporary Dragon Quest art.) I don't mind if you use my images or code.
  

I don't know when I'm going to work on this project again--it's a hugely ambitious thing, something I was obsessed with working on for a few months, and I'm not sure when I'll be similarly obsessed again. I'd like to put at least a temporary cap on it while I worry about money, writing, and my other projects. Losing my novel and a lot of work on Chocolate Sauce was horrible, but given the choice to work on restoring one or the other, I worked on the novel, and that probably has to count for something.

Goodness Gracious

So again we're experiencing major computer problems which gives the game a frame rate of something like 2 fps. This is obviously bullshit, but until I can get a new computer or somehow fix this one, I can't really do the stuff that's remaining on Chocolate Sauce for the first release. I have some new enemy art to load in, and that's about it.

One thing that has been done or is about to be done: I was talking with Paul about wanting to write a cutscene parser for VERGE as part of the work on Demon Lord Adventure III, which I could then use for all future cutscenes on Chocolate Sauce since writing cutscenes is horrible. He came up with an idea for a better "wait for entity" function that's pixel-perfect rather than relying on the entity movecode strings, which cause problems when you do a lot of things where entities stagger backward one step, etc. I've been writing cutscenes just by choosing an arbitrary number of ticks to pause the engine for entities to move and then trial-and-erroring that number, which is senselessly tedious. A parser is the ultimate goal, but implementing it would be crazy since it involves some kind of metacode. I'll figure it out.

That's mostly it--I've been busy with other stuff lately, mostly a new internship and the revival of my webcomic, The Man Who Hates Fun. I have so little stuff left to do on Chocolate Sauce Part I that it's stupid I haven't yet done it--until I can somehow get a computer setup that lets me check things at a reasonable frame rate, though, there's not really a point. That's not a good excuse but it remains an excuse.

Art I can do at least. I'll try to at least make the maps look cooler/finished by next week.