News & Development Blog

In this part I will describe in more detail what abstract, or “hidden,” balancing is and how it can be used in your game. This is the last part I’ll post for a while, since I’m going on vacation for a few weeks, but I’ll be back next year!

What is Abstract Balancing?

As already mentioned, abstract balancing is changing how well a unit performs by modifiying calculations that take place “under the hood” in your game. Examples of abstract balancing are damage values, health counts, armor values, attack accuracies (attack probabilities), armor types and so on.

Abstract balancing is used when – to the player – two equivalent actions should yield different results. For example, a swordman attacking a horseman may not give the same effect as a pikeman attacking the same horseman. This is based on the “pikemen should deal more damage to cavalry” type of abstract balancing.

Damage Modifiers

This is abstract balancing at its purest form. Damage modifiers are needed to keep certain unit abilities in check and help mixing up an otherwise single-unit army. The problem with them is that they require practice on the player’s part to fully understand. When they are used, they should be kept as consistent as possible. For example, in C&C 3 all bullet type weapons are efficient against all infantry units.

Starcraft uses a fairly simple table for attack modifiers. It has four armor types and three damage types, as seen below:

”Concussive” attacks deal full damage to soft armor, half damage to medium armor and one quarter damage to hard armor

In other words, one attack type is effective against small and organic units and another is effective against armored units and buildings, and a third that deals full damage to everything. This kind of system should suffice for most games, unless there are different kinds of instant-kill weapons, such as sniper rifles (which usually are completely ineffective against armored units). However, keep in mind that visible balancing is always better than abstract balancing, so an “Unable to attack target” message is better than dealing insignificant damage.

Chance to Hit Probabilities

Projectile accuracy is something that can be designed to be visible to the player. Age of Empires 2 does this beautifully, which I will describe in the part about visible balancing. However, projectile accuracy can also be designed as an abstract modifier called “chance to hit probability.”

Essential this kind of probability is a modifier which changes how much damage a unit inflicts when it attacks. This doesn’t need to be a bad thing, but it’s very important to make sure that it’s easy to recognize when an attack has hit or missed. In Dawn of War it can sometimes be hard to tell when this happens because 1) a missed shot may sometimes fly through a unit, 2) hits also fly through units because of a render bug and 3) units have a high rate of fire making it less relevant which of the shots that miss.

Hit Points

Health meters are so common in games that most players know exactly what they represent and how they work. That is not necessarily the case for new or casual gamers, but generally it’s a lesson quickly learned. However, health is still use of a kind of hidden balancing since people rarely memorize the health counts for all units in the game.

Using Feedback to Transform Abstract into Concrete Balancing

The problem with hidden balancing is that it can be difficult for players to understand why something is going well or bad for them. This can be remedied by including appropriate feedback for the events in the game. For example, if an attack with a “good” damage type is used on a target, show it to the player with a more spectacular impact effect and sound. Try to keep all units of the same armor type similarly-looking. Try to match hit points with the unit’s size. And so on…

In the indie game, Project: Aftermath (2008, Gamesfaction), they represent different damage/armor types with colors (red armor protects versus red attacks etc). Though simple, it works well and is an integral part of the game (unfortunately a little bothersome as well due to how the user interface is designed). You could consider something along those lines if you use a lot of abstract balancing in your game.

Hey, this has been very informative so far. Looking at making an RTS myself. I was wondering if you would talk about how you might start planning out an RTS from say a design perspective? For example, how would you take a general idea and plan it out before you begin working on a game engine? Do you have a sample document that might be used to assist in this aspect of the game creation?

Jeb, I played and Loved WiA! Was waiting for more when the servers shut down. When the source was released I created my own Akarra which took off like i never believed. Have been hoping for Daria since and still have nothing :cries: Any ideas of just letting the alpha server stay up for people to play on?

The server is no longer up. I had to go on and shut her down bc my ISP didn’t want to handle the bandwidth anymore. I wish it were, I didn’t get to play Daria when it WAS released, but I played WiA and heard they were similar.

I think with more work, this series could quite good. It has been an enjoyable read, thought-stimulating, but not quite developed. Reminds me of a prepared fried chicken meal purchased from a supermarket: looks good, seasoned-well, and lacking in meat.

This is a great series on RTS games. I have learned a lot and thank you for sharing your knowledge. The only thing that I felt missing were diagrams describing various strategies and scenarios which would have made understanding a lot more quicker.