Home Creators Posts Import Register Favorites Logout

Content

I keep forgetting to mention when discussing the game art and inspiration that the top-down perspective on the wall tiles is based heavily on Legend of Zelda: A Link to the Past, which I will likely be using as reference for perspective in the future as well, for character and enemy sprites.

No need to reinvent the wheel.

As for what I’ve been up to this last week… well it’s nothing surprising. I’m up to 25 possible perks/upgrades that I’ve been preplanning. We’re still well pre-alpha, for anyone keeping track, and the minimum number of perks I want for the alpha release is 100. A daunting number I admit, but I’m already making good progress towards it.

The trick is going to be implementation.

Since this is all pre-planning that I’ve been doing, I haven’t touched the code since the launch a few weeks ago. Even so I can predict where I’m going to have difficulty with adding in some of the new features. My bullet and damage system is versatile enough that adding in damage types and critical hits should be pretty simple. I’ll also need to have a way to check for critical hits, as I want certain perks that grant bonuses when you land a critical hit, and that’s either going to be very easy or very difficult with no in-between.

The thing I’m really concerned about is having multiple damage types. Let’s say you pick up a perk that adds Fire damage to your bullets and then one that adds Ice damage. What happens? Does the Ice override the existing Fire? Do you get both? If you get both, I’m not entirely certain how to check an array for a specific value. Do they mix together into a new damage type like how Warframe does it? If so, then what happens when you get a third?

I’ll honestly have an easier time with the status conditions. Another thing I intend to add, status effects and conditions will provide a great deal of variance between different builds on different runs of the dungeons. I only have a few of them at the moment, but I intend on adding more. It should also be easy to implement. Anything that can get a status effect just needs a single line of code, telling it to run all the functions listed in an array, with the array containing every status currently affecting them.

Speaking of status effects, did you know that in Pokemon, the Burn status halves the damage of affected Pokemon’s physical attacks? I did not until recently, and that’s a shame, because that’s a whole layer of strategy I was entirely unaware of. And it’s so good that I’ll be stealing the basic idea. Common status effects like Burning or Freezing will apply secondary effects as well, to help change up each elemental type/status build from the others.

Sadly, at this moment, I only have three of those planned.

I’ll also have certain status effects that are only applied by landing a critical hit, like a perk that grants you a chance of inflicting Bleed on a crit. Variance and strategy is the point here, and I’m excited for the way my plans are shaping up.

Of course, this is all predicated on the idea that I can figure out a way to preview a handful of perks for the player to choose between, as mentioned in last week’s DevLog.

Speaking of strategy, there’s another thing that I want to implement that I have no idea where to start with.

I don’t know this for certain, but I believe it was Slay the Spire that first invented this style of Roguelike/lite progression, but I’ve seen it more and more, and it’s honestly brilliant. Basically, between each floor of Slay the Spire, you’re shown a map of your progress, presented almost like a flowchart. This map works like a board game, where you select the next space to move to, and then complete that floor. And each floor is labelled to tell you what to expect, from merchants to healing to fights, etc. with some spaces marked as a Question Mark just to keep you on your toes.

This adds a lot of thought and long-term strategy into the basic progression model of any given run and if I can, I would love to implement it.

However, that’s a ways off. First, I want the actual upgrades and combat to work.

Hopefully the code for the upgrade choice system will help me figure out how menus work, because I currently lack a main menu or options menu. And that last one is a big deal because I want to have some accessibility options for this by the time of the full release. I’ve already put in the framework for difficulty adjustment wherever I can so that players can customize the damage and health of the enemies and player to their hearts’ content.

But first, the perk choice system. I need that system to be as versatile as possible so that adding in new upgrades in the future is extremely straightforward.

And that’s all before I get into thinking about the art style and the problems I’m facing on that front with keeping to the hand-drawn stylization.

Well, no one ever said that game design and development was easy.

Until next Devlog!

-DeusVerve

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

Files

Comments

No comments found for this post.