This blog has moved! Redirecting...

You should be automatically redirected. If not, visit http://orangeriverstudio.com/monksbrew/ and update your bookmarks.

May 21, 2009

The One Thing He Forgot To Mention

It's blog post number 100, so time to catch my breath. Crazy string of weeks there from April through mid-May, trying to make deadlines, having those deadlines pushed back, trying to make the deadlines again, and so forth. Some successes, some failures, but you can't argue with the fact that deadlines are great for getting shit done, even if you don't get it all done.

It's a little weird because my day job is filled with deadlines. Basically, it's like a slow march from one deadline to the next, and every so often I get caught up in it and spend massive amounts of time working like crazy to finish under the wire. But that's work. This was a deadline for a hobby. None of the panic, despair, and regret to deal with. It was a very different experience.

One of those deadlines was for the last Utah Indie Night, back at the end of April. I missed the last couple, so it was nice to be back, and to have another rare opportunity to present Vespers in public -- even if we didn't get everything for the full demo done. TRC had some nice things to say, which I appreciated, even if the game isn't very playable yet. Now that Aaron Reed has finished Blue Lacuna, it's now down to me and Jay to see who finishes last. Sorry, Jay, that flying car is all mine, so better start saving up now.

On a related note, at the start of the Utah Indie Night there was a short presentation by Darius Ouderkirk on how to choose an indie game project, with the key being a project that you can finish and release. As Jay blogged, it was simple but hit a lot of very good points -- even if, as pointed out to me later, he hasn't shipped a game himself yet (d'oh!). It was filled with good advice; a collection of fairly common sense approaches that have been mentioned in one context or another in various places around the 'tubes, but assembled and presented in a nice way.

But as I think about it now, there was one thing he forgot to mention.

With most projects, especially those you put a lot of yourself into over an extended period of time, there are peaks and valleys. And sometimes, those valleys can really suck. Sometimes, as Jay mentioned in another of his blogs, it has a lot to do with motivation. All games have fun parts and tedious parts, and those tedious parts can start to feel like chores after a while. Designing and implementing dialog boxes. Placing endless numbers of decorative objects, like walls or leaves. Modifying terrain. It can get pretty dull, but there are ways to fight through it, mixing the dull parts in with the fun parts. The target is always in front of you, so you just plug away until you get there.

But then there's the other type of valley: the periods of self-doubt that grow insidiously the longer you work on a project. Often you end up spending so much time working with all of the pieces at the microscopic level that you go long periods without taking a step back to see things at the macroscopic level. But then sometimes, when you do, the view doesn't seem so pretty anymore.

The usual questions start popping up, questions like "What am I doing?", or "Why am I doing this?" You have a clear view of all of the flaws, and none of the virtues. Nothing looks as good as you thought. The game doesn't seem very fun. The interface sucks. And of course, nobody is going to want to play it.

And that can be a really deep valley, because now you're not just dealing with the motivation to push through the boring crap, you're dealing with the motivation for the whole project. It's the kind of valley that can kill a project.

Of course, as with many things, it's never as good or as bad as you think, and sometimes it just takes a little perseverance to get through those periods. Maybe getting back to the microscopic level until the bad mojo passes. Or maybe taking a little time off from things and recharging the batteries. Or, perhaps, using the opportunity to get other people involved -- letting fresh eyes take a look at things to see what works and what doesn't, recalibrating your inner barometer.

I don't know what proportion of game projects go through valleys like these, but I imagine it's fairly high. I think it's probably more of an issue for individual developers and smaller indie groups, since there are fewer eyes looking at things from wider angles. Regardless, I think it's an important issue to mention to aspiring developers. Hell, it applies to anyone working on any kind of creative project. Be ready to hit at least one, and decide whether you're gonna suck it up and fight through it, or let the project wither away.

So I'm in one of those valleys right now. The closer it seems that we get to a working demo, the less I think this is actually going to work. It's hard to imagine people thinking the game is fun. The performance will stink, the animations and voice acting will disappoint, and the interface will be nothing but a confusing mess. What's to love?

I've taken about a week off from the game, but I'll be getting back to it soon. And I think maybe the best thing to do right now is to start getting some new eyes to look at the game. Do some testing, see if it really does stink. Maybe see what parts can be improved, and what parts just don't work at all. It's getting to be that time. And so I may need some help with that.

3 comments:

georgeolivergo said...

From the comments on this blog I know you've received a lot of positive feedback, but I wonder if you feel you get enough of a cheering section in the day to day? I mean simple positive feedback, not constructive criticism or anything like that. From what I've seen it seems like that can help row a project along too, and one good place for something like it that I've found is a well-attended and active forum.

Mike Rozak said...

Not to be too depressing, but...

It's like climbing a mountain. You get to a level area, look up, see a bit more elevation to go, and conclude the summit must be just above (and behind) the ridge you can see.

You climb up to the ridge, notice yourself on a level patch, look up, and realize the summit must be just past the next ridge.

Ad infitum... a maze of twisty ridges, all alike... or so it is in my case...

But this time, I'm sure, I'll actually see the summit after the next milestone.

El Clérigo Urbatain said...

I'm in a valley in my actual project:

(self promotion)

http://www.caad.es/spac/spip.php?rubrique16

A comic about a text adventure that I intent to build in a flash game. All is in Spanish, but maybe you can enjoy my vectorial art. See the stripes under the topic "El anillo".

(end of self promotion)

That is because I'm designing the characters right now. It's like slope step for me that never before make drawing art. The sensation of "I'm doing it very bad, This stinks, I'm stink" is so high. So it is very important to have fresh eyes to give the proper vision to your work. Not only fresh eyes, but two pairs or three of good friends, good at the matter at hand (design videogames), that could give you the proper criticism, or the proper praise for a work well done.

When you work on something for so long time, could give you two kinds of syndrome: the syndrome of being accustomed to something you have created and believe that it is ok, or that it is very very good; or the opposite effect, to believe that what you are doing is really really bad. In both cases, both fresh eyes and knowing eyes are quite helpful to pull the cord and get you out of your valley.

So yes... you need alpha tester now! Rubes!. And you need to concentrate in a prototype of game play so tester and you could feel if the game is going to work or not. So, to finish that demo with the day one, seems a good idea to me, but in a game like Vespers, that demo is almost 60% of the game. It's a too much effort for a prototype to test before you get into a deep valley. Maybe you could handle a one room test for some good friends, later a more than one room but less than five test, etc.

Later, make successive iterations in the interface and game-play until everybody (testers, staff of the protect and you) are really satisfy. Then proceed to complete a real demo. Iterate de testing. Then proceed to complete the whole game.

In my work at hand, first I made only one strip. I was satisfy, so I made another. Now I'm trying to make a whole comic. I was in the valley until I discovered thanks to the iteration and my friends, that my characters are cool :P

Keep on pulling the cord Rubes!