Home Creators Posts Import Register Favorites Logout

Content

We’re a week down, three to go. I have no idea if I’m still on target or not because there’s one rather sizeable part of this project that I can’t even begin to run a time estimate on, but more on that later. For now, let’s check in on my progress.

As a refresher, by Week 6 I hope to have a fully playable micro-demo of this game. To get that to happen, the following needs to get done:

1 ‘dungeon’

Hub Area

Menus

7 enemies - COMPLETE

1 boss

The basic powerups - COMPLETE

SE + Music

Art

As you can see, I’ve finished the last three enemies, who I’ll introduce shortly. I also made some adjustments to the enemies showcased previously, mostly by increasing the range of their attacks. I also made terrain block the shockwave attack, so that cover will cause it to break up and create gaps in the ring.

As for the new enemies, we can start with a basic turret that repeatedly fires missiles at the player before taking a few second of cooldown between volleys.

I’m quite happy with how the missiles slow to a stop before detonating. There’s currently a minor bug with the missiles and how they interact with the player’s mercy invincibility, but it’s an easy fix I can change with a few keystrokes, I just haven’t yet. It was a fix I had to implement because of a different enemy we’ll see later.

Next we’ve got another area denial enemy. This one’s pretty simple, they fire in a circle, rotating their fire to create something of a spiral. They aren’t even aiming at the player, but the volume of bullets could prove to be something of an issue.

Not exactly a threat alone but dangerous in swarms.

Finally we have another enemy that doesn’t actually use bullets to shoot at the player. They instead have a cone attack of floor spikes.

This is the reason I needed that one fix I mentioned earlier. My damage code would recognize the attack as dealing zero damage when the attack was charging up (that is to say, when the spikes are still in the ground), and trigger mercy invincibility even though no HP was lost. This wasn’t a hard fix; I just added an exit to the damage function if the damage equals zero. That missile issue I mentioned is that the missile does not do zero damage, so the player is invincible for the actual explosion.

Next up is a minor bugfix. Previously, if you died, you would keep all of your powerups. I overcomplicated fixing this at first by trying to make a second set of variables to set the player variables equal to, but manually resetting them all is way more efficient.

While I was fixing the damage thing, I realized I forgot a powerup last week, so I added that really quick. They’re not exactly difficult additions.

Next up was the addition of Hitstop and camera shake. These are tools to help emphasize feedback to player, to make it easier to understand that you have been hit and where. Now when the player takes damage, the game pauses for a fraction of a second followed by a shaking effect with the camera. This is technically a bug, actually, as they’re supposed to happen simultaneously. I think I know how to fix it but I haven’t gotten around to it yet.

I had some issues with the hitstop actually, since the bullets use some of Game Maker Studios physics handling, and therefore will continue to move even while running no code, but I sorted that out with an empty While loop.

Which leaves us now onto the next hurdle. And it’s the big one. If anything is going to cut my time a bit close to that release date goal, it’s this.

Procedural Generation.

I plan to use the simple method of gluing premade rooms together like The Binding of Isaac rather than something more like how Nuclear Throne creates a totally random space. This gives me quite a bit of control over the encounters the player can have, as well as the environment. This is a game based around RUN AND GUN, as you might recall, and a more randomized organic shape might result in environments that clash with that gameplay.

The problem with that is that I’m not exactly a programming genius. I’m a designer, I design the backend and work with programmers who bring my design to life. Doing it myself is something I have to do because I am a solo developer but we are well outside my typical wheelhouse.

(I should note that designers should know at least a little bit of how to program, both for ease of communications with developers and coders, and to help with testing design such as parameter changes. Doing everything alone is a bit different.)

Researching how to pull this off was a pain. I mentioned before the Nuclear Throne method, and that’s the method that about 90% of tutorials cover. The method I want to use is mostly reduced to theory instead of practical implementation. However, I found a promising lead so I think I’ll be able to pull this off.

With any luck, next week I’ll be showing off some kind of procedural generation. The faster I get it done, the more variation I can add to it.

Three weeks to go.

Until next Devlog!

-DeusVerve

Special thanks to my Tier 3 Patron Haelerin!

Files

Comments

No comments found for this post.