The one year game develpoment duel



Refactor, Health Bars and Ranged Combat

This post is a status update, which is how I track progress specific to my game. Check out my timeline to see what I've recently accomplished.

    Key Events
  • Refactor FSM
  • Health bars
  • Ranged Combat

I’m finally able to start writing game code, and it is fun. Now that learning and performance issues are almost behind me, I was able to implement  ranged combat and death, which is great to see in action. In addition to that, steady progress has been made on the world map, and early story boards are coming along. This update also marks the end of the first contract with Scott, my illustrator, but we’ll be entering a second contract shortly.


As I mentioned in my last update, I have to constantly worry about performance because that will determine how many units I have on screen. I just wanted to make a quick note here that there has been a lot of progress on that front. Between Swift compiler optimizations and caching enumerateChildNodesWithName, I’ve seen significant gains.

I haven’t tried max units again, but I will sometime in the near future. I still have a few ideas to improve things, so we’ll see how efficient I can get it.

Death and Health

I recently began ranged combat, but it was just a rough proof of concept instead of a proper implementation. Over the past two weeks, it has progressed nicely. Let’s start by seeing it in action.

A couple of things to note:

There are a bunch of minor details too that can’t be seen. Specifically, how to notify a squad and unit that you are engaging, attacking, disengaging, or have died. There is a bunch of cleanup to do when changing targets, so I broke that logic out into an EngageService to make sure it stays together. I wouldn’t call this 100% ready to launch, but it is in a good enough spot to move on for now.


Rewriting code is never sexy, but it is a necessity. I feel like rewrites will never stop happening, even as I start to believe I know what I’m doing. Anyway, the major change here is to move towards a hierarchical finite state machine. I strongly considered behavior trees, but given my performance issues I thought they would only hurt more. I’m not confident that I made the perfect choice, but ranged combat was much easier to implement with my new code. So for that reason, I’m happy about the current state.

Next Up

Melee combat. Such a simple goal, but a tough task. To get melee right, I have to do a few experiments with physics and performance. In particular, making sure the units space out correctly so that it looks like natural combat, and so that the player can see what’s going on. Let’s see how far I can get.

Speak Freely

Thank you

Your comment will be published once it has been approved.

Click here to see the pull request you generated.