Home Creators Posts Import Register Favorites Logout

Content

Hm. Turns out that temporary stat changes are slightly more complicated than I thought they would be I’m sure I’ll figure it out—it’s probably as easy as having a constant I can reference and then using a variable to adjust it from within the status effect—but it’s not there yet. Since the code for the status effects runs every frame, if I get the formulas wrong I’ll absolutely nuke the target’s stats into the dirt, which isn’t ideal.

After last week’s success with the Burn status I quickly threw together the Bleed status effect, a stronger version of Burn. This status is special in that it’s exclusive to Critical Hits, providing more payoffs to that playstyle.

Speaking of the Critical Hit system, I adjusted that code to make it a bit more robust, and to allow it to interact with the rest of the damage code, allowing me to create other payoffs that trigger when you land a critical hit, for example, the bleed status, or healing the player.

Around this time I encountered a bizarre glitch that crashed the game if I shot a destructible crate, something that isn’t currently in any builds but that I implemented ages ago. At the time I couldn’t figure out what was causing it, but I ended up fixing it later incidentally while fixing another game crashing problem.

With no idea what’s causing the crate problem I continued working on the upgrades that I’d been working on already, the ones I mentioned a moment ago: healing on Crits and inflicting Bleed on Crits. I also added the upgrades that allow you to actually inflict Burn status, as well as an upgrade that increases your chances of inflicting a Status Effect.

Around this point I remembered/discovered that due to the fact that my bullets and explosions share a damage code, explosions now crash the game because they lack about 90% of the functionality that bullets have now. Fixing this was simple but took me a bit longer than I’d like. All I did was add a few conditional statements that made sure the relevant variables existed before trying to call them. For some reason this also fixed the crate problem.

I am now, however, faced with a problem. Certain upgrades are only meant to be acquired once, such as the added Burn status. You can’t add that twice. I thought I already had a way around this, but I don’t actually think it will work the way I want it to. The way that I shuffle the upgrades is by storing them all inside of an array which I can then randomize into a temporary copy of the array, allowing me to use a reference to the original array, ensuring they do the thing they’re supposed to do. I think that the solution I was already planning on using will still work, but in a slightly more roundabout way.

Much like how I store the name, description, and effect of each upgrade as a variable so I can reference them later when the player gets them, I intend on having a variable that checks how many times the player can get any one upgrade, and then go through the array and remove any that can no longer be chosen. If I remove them from the main array, their positions will shift and the variable references won’t work, but I should be able to remove them from the temporary array that shuffles them all.

We’re almost at the end of June now; this is the last DevLog before July, which means sometime this week I’ll have the next build posted and the next What We Can Learn article.

No rest for the wicked.

Until next Devlog!

-DeusVerve

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

Comments

No comments found for this post.