Project RBH Devlog 0038 (Patreon)
Content
As you might recall, last week, I stated that I needed to think about the balance and encounter design of Project RBH. Well, I didn’t use those exact words, but that is what I said I needed to work on.
Project RBH is a dungeon-crawling Roguelike twin-stick shooter, based around the idea that the player will spend much of their time Running And Gunning. This one-sentence pitch is an invaluable tool for refocusing myself on what’s most important about the game and the gameplay.
For example, in dungeon crawlers like the older Legend of Zelda games, there were only a few enemies in any given room, and there was a chance of healing when defeated enemies dropped collectible hearts that would restore the player’s health. You could also break pots for hearts and other items. I feel as if this approach would work best for Project RBH.
Something I’ve noticed about the project is that, paradoxically, the more enemies there are the more likely I am to stand still. This is because the enemy AI is so simple that they all bunch together so it’s easy to just point at them and shoot.
If you’ve played any of the public builds of the project, or even just watched some of the GIFs, you can probably tell how the AI works. It moves in a straight line towards the player, completely ignoring any obstacles or distance between the enemy and the player. When the AI is close enough, it will occasionally stop in place and perform its attack—or, in the case of the Bambs, will simply approach the player until it gets close enough to start its detonation sequence.
This AI is way too stupid for what I want. For one thing, enemies will come in from other rooms if they can allowing them to swarm the player. For another, as mentioned, because they’re simply moving towards the player constantly, they tend to bunch together, and that’s no good either.
There’s also a problem with how the enemies are spawned in. Namely, that they aren’t. They were manually placed in the level and then randomized between two lists of ‘attackers’ and ‘support’ depending on where in the level they are. This is bad because you can start up the game already surrounded by enemies.
So that’s the next two big items on the to-do list: fixing the enemy spawn system and the enemy AI so that the game will feel better to play. After that, I can make the enemies have a small chance to drop health. I don’t know what the chances will be yet, but probably about 5% to 10%.
Once that’s done, the next thing on the list will be my Upgrade system. You might remember that I got some help so now I can quickly turn an excel spreadsheet into workable code, right? Well, I need to familiarize myself with the program that lets me do that, as well as finalize the list of variables that I want to manipulate so that the assisting program won’t need any further tweaking. That’ll come last, though.
Until next Devlog!
-DeusVerve
Special thanks to my $7 Patron(s), Haelerin!