Project RBH Devlog 0 – The Story So Far (Patreon)
Content
I’ve wanted to make video games for approximately two-thirds of my life at this point. I hear a lot of indie developers who make devlogs and videos and posts talking about their Dream Game that they’ve always wanted to make.
I don’t have one of those.
I just really want to make games. Plural.
I do however happen to have a budget of zero dollars. Which is, I will admit, something of an issue when it comes to game development and design. Don’t get me wrong there are a lot of powerful free tools out there. Unity, Unreal, Blender, I’m not exactly short on options. Okay, so I was put off of Unity from their CEO calling people who don’t monetize their games ‘idiots,’ but the point stands.
I was also fortunate enough to be gifted Game Maker Studio 2 right before they updated their Terms of Service to a subscription system or whatever nonsense YoYo did. What matters is that I own the engine and don’t have to pay subscription because they were nice enough to not try and retroactively alter legal user agreements, unlike some game companies I could name did recently.
But enough digs at the evils of capitalism, let’s talk about Project RBH.
Project RBH is a placeholder name I’m giving this game while we’re in development until I can come up with a better one. It stands for Reverse Bullet Hell, which is a decent summary of the main goal. Project RBH is a top-down twin-stick roguelike. The Reverse Bullet Hell comes from the main mechanical twist I’m putting on similar roguelikes, like Enter the Gungeon. The upgrades and pick-ups found during your run aren’t better weapons or equipment, but upgrades to the behavior of your primary attack. Most of them will do basic things like increasing the speed of the projectile or making it bigger, but there are other things that can be done to really make your attacks crazy.
The goal is to have a game where it is possible, over the course of a run, to build a gun that shoots a gun that shoots chainsaw bullets.
So Where To Start?
Like I mentioned earlier, I’ve watched multiple devlogs on YouTube, read Devlog posts, etc. And I see many of them running into what seems to be the same or similar problems: a lack of focus.
I also happen to have a degree in game design. And fortunately we had industry veterans in the course, so one of the things they taught us was the importance of a Game Design Document, or GDD.
Warren Spector, one of the leads on the classic Deus Ex, talks a lot about having a GDD during the development of that project. It’s an incredibly useful tool for pre-production, as well as for ensuring that people from across the project all have the same understanding of the creative vision. Obviously, I am a solo developer because I am broke and insane, so that last one won’t be much of an issue. But that first one is extremely important to combating many issues that crop up during game design and development, like feature creep and decision paralysis.
Which is why I haven’t made one.
Okay, no, that’s not the reason, and I will, but it was too good a transition to pass up.
The real reason I haven’t made a GDD yet is because there is another way that one can start a project. I would not recommend you do this, the GDD is a really good idea and I’ll go into more detail about it in a future Devlog, probably the next one. The reason I have chosen to do things this way is because I wasn’t confidant about the planned gameplay, so I wanted to quickly prototype it and experiment with it to see if it was actually, you know, fun. It’s nothing fancy, I have no background and the character sprites are squares, but it gives me something I can mess with.
This prototype is where I’m at right now. There isn’t even Procedural Generation, just a giant room with some walls and a whole lot of enemies.
You know what, I didn’t even realize the player and enemies are both green.
So that’s where Project RBH stands right now, a single prototype that I’ve been toying with so I can decide where and how I want to focus this game. From my experiments so far, I’ve noticed a few different directions I can take the project.
A game with a wide variety of weapons which the player can loot during runs. The player’s collected weapon improvements carry over between weapons. This has the pro of providing things for the player to unlock from runs without affecting game balance, but comes with the con that certain upgrades will make weapons feel too similar.
The original plan, in which the player has a single weapon which is reset after each run. The pro of this is that the random weapon upgrades can do some crazy stuff to this weapon, but comes at the con of being very same-y at the start of each run.
Additionally, my experiments have lead me to the realization that having a lot of powerups that drastically alter your weapon leads to a chaotic mess as you rain doom and destruction upon your pathetic enemies. This leads to the third direction I’m considering.
Much like the first one, there are a variety of weapons, however these weapons are far more powerful and do not upgrade. The player mows down hordes and hordes of foes and has a power fantasy.
Here is me with no upgrades versus me with many upgrades.
As we are so early in preproduction, I don’t feel like showing off video is strictly necessary yet, but yes, it’s more obvious what’s happening in motion.
Which is where we will end this Devlog. I’ll run some more tests, maybe ask some people I know to try my experiments to get some more opinions, decide on a direction for the project, and make a GDD.
Until next Devlog!
DeusVerve