Home Creators Posts Import Register Favorites Logout

Content

There were some real-life complications that means this Devlog doesn’t have quite the progress that I would like, namely how long it took me to get feedback on my experiments. 70 mph windstorms can do that, apparently. The good news is that nobody was harmed, and damage was minimal.

To recap, I found three possible directions for Project RBH, and I promised to settle on one of them and write up a Game Design Document (GDD). And I have reached my conclusion from probably-not-extensive-enough playtesting.

Project RBH will involve the player starting out with a basic attack that they steadily upgrade over the course of a run, until by the end they are filling the screen with bullets like an angry god.

So the next step is writing out the GDD to make sure that the game actually reflects this idea.

I touched on it last time, but I feel like there’s more to say about GDDs and what makes them such useful tools for game design and development.

Conveniently, Game Maker’s Toolkit recently put out this video on means of analyzing games which ties directly into this subject. 

The short version of this video is that a game’s systems and mechanics lead to dynamic interactions with the player(s), in turn coloring their emotional response. For example, a game where you have big guns and lots of bullets will probably make you feel like an unstoppable action movie hero, while a game with limited ammunition and powerful enemies will make you feel disempowered and cautious.

The GDD is a way for the development team and the designers to coordinate the systems and mechanics to steer the dynamics and achieve the desired emotional response. It’s an incredible tool for focusing design and development to a single, sharpened point. A way to ‘fail faster,’ so to speak.

Failing Faster refers to the practice of constant iteration as quickly as possible, in order to achieve more feedback and learn from the parts that don’t work. It’s the entire reason I threw together my current prototype even though I haven’t done my GDD yet. And yes, the GDD itself can be used to fail faster. Getting ideas out of your head and onto the page forces you to think of how to communicate those ideas, and gives you something tangible to show people and receive feedback on.

It's a way to prevent Perfect from being the enemy of Good.

But what’s included in a GDD? Yes. Yup, that too.

I’ve still got a template from my college professors while I was getting my degree in game design, and it includes:

· The World,

· Intended Audience,

· Unique Selling Point

· Multiple sections on plot and characters

· Means of narrative progression

· Locations, Layout, Maps

· Intended Gameplay Experience

· Enemies

· Combat

· Obstacles

· Items and Equipment

· User Interface

· Art Style

· Music and Sound

Among several other things.

As you can see, it’s a lot. Luckily, it’s divided into sections which makes it a heck of a lot easier to get through, especially because I don’t need to write an entire essay per section. The GDD is a living document, meant to be edited and updated throughout the lifespan of a project. I also won’t necessarily need every section.

This does, however, lead us to our next problem with the design. Story.

I’m the kind of person who really likes narrative in his games. Traditionally, Roguelike/lites are not known for being exactly narrative heavy. The cyclical nature of dying, restarting for zero, dying again, repeat, doesn’t always lend itself to storytelling.

Luckily this is a problem that has been solved multiple times. The recent Hades, for example, turns that very thing I listed as an obstacle to storytelling into a vehicle to drive the story forward. Heat Signature gives each of your playable characters a motivation; a specific goal they wish to achieve before dying or retiring, letting the player craft each character’s narrative through their successes and failures. Cult of the Lamb has a narrative explanation for your immortality and your runs with a plot that continues through the whole game, albeit a simple one. And, of course, the Mystery Dungeon games have been telling stories with roguelike elements for a long, long time.

The issue is not that it is impossible to tell a story in this kind of game. The problem is that calling my budget ‘shoestring’ is a gross exaggeration. Having a simple excuse plot like the one in Orbital Bullet would dramatically reduce the development time of Project RBH.

On the other hand, making this game the way I am is already enough of a pipe dream that it might be worth going all-in on it.

So that’s where things stand at the end of Week 1. Next week I’ll be checking in with the progress of my GDD, and deciding how and where to start actually making this thing.

Until next Devlog!

-DeusVerve

Special thanks to my Tier 3 Patron Haelerin!

Comments

No comments found for this post.