Home Creators Posts Import Register Favorites Logout

Content

Following the cataclysmic discovery that the Procedural Generation code no longer worked, I had a few options available to me.

I could’ve switched gears to a Vampire Survivors clone. While the original Vampire Survivors did not feature any dedicated attack button, instead preferring automatic attacks, at least one of the game’s many successors has been a twin-stick shooter like Project RBH, and the upgrade system would be well-suited to this style of game while staying in the idea of being a reverse bullet hell.

I could also have gone with something like Nuclear Throne, which procedurally generates a single combat arena and then throws a wave of enemies at you, which also would’ve worked out well within the framework I’ve already established.

But in the end I did neither of those things.

I don’t remember if I mentioned it before—I should have, but I don’t remember if I did—but the procedural generation code I’m using is not my own. It was publicly provided by another member of the GameMaker Studio community, Cloaked Games, who has continued to work on it for the past few years now and has recently started their own DevLog series on Youtube dedicated to their own roguelike.

I reached out to Cloaked Games about the problem and within hours they had replied and patched the code to work again. It turns out the some of the code was using depreciated functions that had been replaced as GameMaker itself updated through the years, so replacing those old functions with the new equivalents made everything work again. Problem solved!

To celebrate I started messing around with the camera; the very thing I’d been trying to do back when I discovered the problem. The new camera isn’t perfect, but I have successfully made it so that the camera will offset from the player towards their cursor. Unfortunately, this doesn’t seem to have worked the way I wanted, as it isn’t very reactive until you cross an invisible threshold that separates the screen into four quadrants. I’ll figure out some way to fix it, since I don’t want it to cause any motionsickness, and I’d rather err on the side of caution there.

Following that, I finally got around to fixing some bullet behaviors that have been in the game almost since the beginning. Specifically, Piercing and Ricochet.

See, I want both of these to happen a limited number of times so that I can dynamically change them via the upgrade system, so you can get +3 Piercing or something and hit a bunch of enemies in one shot, but not every enemy in that line, or go through too many walls. Unfortunately, my code for that was based around preventing the bullet from seeing that it had a confirmed hit against a target, which triggers them to delete themselves. All I had to do was slightly adjust the code I’d previously tried to unconfirm that it had hit something and decrease a variable tracking how many things it can go through. And now it works!

Ricochet had a similar problem in that I wanted it to only happen a few times, but it was unlimited. However, this is because I was using the in-engine physics to handle their bouncing so I wouldn’t have to figure out the geometry calculations myself. As a result, they never registered that they were actually hitting the walls. This fix was a bit more involved. I had to go into the damage script that registers that the bullets hit something and add in an If statement checking if they still had ricochets left and if so, to bounce, and if not, to move onto the next step (deleting itself or piercing).

And now it works!

My final bullet behavior is one that I’ve wanted from the start but I didn’t know how easy it would be. Homing Projectiles, but ones that I could also dynamically adjust. Turns out it was easy, actually. I tried several different math formulas to adjust the bullet’s direction mid-flight, which was easy because I am again using the engine physics for their movement, so they already preserved velocity. Some of them worked better than others, but I found one that also allowed me to assign a variable to how fast it would turn towards the nearest enemy, and that means I can upgrade it!

Unfortunately this all means that I no longer have any excuse to not stare at my spreadsheet and plan more upgrades. Well, except for fixing my camera, but I doubt that will take very long. So back into the tank for dry office work, I guess.

But on the bright side, the core gameplay is coming along nicely!

Speaking of which, I almost completely forgot, but it’s the last Monday of the month! That means it’s time for this month’s release of the early build for my Tier 2 and 3 Patrons!

Until next Devlog!

-DeusVerve

Special thanks to my Tier 3 Patrons, Haelerin and Christos Kempf!

Files

Comments

No comments found for this post.