The value of rapid prototyping
The highly subjective musings of a game designer / programmer.
Prototype of a cancelled game. While the idea was intriguing at the time, I quickly realized it was just too similar to other games after prototyping it.
As a game developer you've more than likely at some point come across an idea that just seems perfect. Some mechanic or gameplay that seems so cool that you cannot fathom that no one has done it before. Often, a quick google search will reveal that it has in fact been done before, and that your idea is just one in the sea of many, but every once in a while you'll find that, hey, I might just be the first to think of this. As creators, this discovery is often followed by a body pumped full of adrenaline, and a brain rapidly filling up with eureka moments. In a fit of insane inspiration you start jotting down idea after idea, until your notebook looks like a lunatic asylum's wall. In this divine state of madness, everything goes! The ideas are getting more and more out there, and at the very end you stare down at your Dali-esque magnus opus, and suddenly it hits you: this is totally crazy; none of this even remotely works together. And why is the main character the ghost of a goose?
Sounds familiar? No? Then you have nothing to worry about.
But on the off chance that seems like something you'd do, I have a proposition that might help; prototype it.
Rapidly prototyping might save you a great deal of time. Not every idea will work as you imagine it.This was supposed to be a simple math game. Does it look simple to you?!
Not the crazy-ass ghost of a goose character, of course, but that very idea that sent you into the whirl of insane inspiration; that adrenaline-inducing mechanic. Simplify it down to its very core, and try it out. Doesn't matter if it's a game prototype or not. You just need to somehow prove that is what you believed it to be.
If it works; great! You can carry on with your lunatic schemes, and maybe something works out in the end. (Maybe the ghost of the goose is really a metaphor for lost innocence? Just throwing it out there.)
If it doesn't; also great! You've potentially saved yourself weeks of work that could have led nowhere.
This idea I gave up because of the complicated controls. But I might revisit it in the future if I feel like crossing that barrier.
I've found that rapid prototyping helps immensely to filter through "great" ideas, as long as they're simple. The more complex the thought, the harder it will be to prototype it. If your idea has several elements that are vital for the whole, then a spread sheet and some critical eyes might be the better way to go. The wanted outcome will be the same; to spare yourself that feeling of failure when you've spent weeks, or even months, on a project that goes nowhere, or better yet; confirmation that your idea isn't a madman's insane ramblings.
A hybrid between a dungeon crawler and mine sweeper! How bonkers is that?! Yeah, after prototyping it, it sort of dawned on me. It’s not a ghost of a goose, but not far from it.
Upon closing I'll just mention that even if you at first post-prototype glance find an idea to be garbage, coming back to it later might inspire you to change it into something that isn't. Maybe the ghost of the goose is just an npc now? Maybe it's no longer is a goose? Could it be a swan? Who knows!
This one I’d like to revisit at some point. The reason I abandoned it was partly the visuals, partly the slow gameplay. Both easily redeemable with some work.
That is all. Go forth and create.
Bonus: an early look at one of the current games I’m working on. After prototyping it, I came to the realization that it had become too complex, and that I would need to simplify it.
FIN