I’ve added some text damage indicators to show the player how much murder they’re dishing out. When they shoot a robot, a number pops up to show the resulting damage. On one hand, screen clutter is bad. On the other hand, if players don’t understand the mechanics it can lead to frustration and confusion. Oh sure, I could just TELL the player about how laser power, energy drain, and armor interact, but showing the player some math outside of gameplay is going to be a lot harder to understand than just showing them how hard they’re hitting.
I sent this version out to my testers last week. We’ll see what they say.
My guess? “Make it an option”. Everyone says to make things an option. It’s often good advice, but making EVERYTHING an option makes for complicated interfaces, complicated debugging, and gutless design. If possible, the game designer should really just figure out what kind of game they want to make. Telling the user, “There’s a good game in here someplace once you get all these sliders and checkboxes sorted out and adjusted” is probably not the most direct route to fun. Some things must be options, some things should be options, some things can be options, and some things just waste the user’s time and fill them with doubt. A simple checkbox at the start of the game for “permadeath mode” probably won’t overwhelm the user. But adding a dozen checkboxes and sliders? That’s fine for strategy games, but it’s probably bad form in a simple action game.
But like I said: We’ll see what testers say.
The biggest trouble spot in my game is the missile system. We’ve done half a dozen builds now, and I don’t think we’ve had a single iteration where missiles weren’t a problem. At first the entire missile skill was useless and a waste of skill points, because there weren’t enough missile to make use of it and they didn’t do enough damage.
I sort of assumed that the missiles would work here the way they did in Descent. They would be used to clear out clusters of weak foes, or to soften up something big. I didn’t intend for them to be used all the time. But this game isn’t Descent. Good Robot has a faster pace and more foes. You can see all around you, so dogfighting in the middle of a room is a viable and fun approach instead of suicidal.
During testing, one person tried to do a “missile build” by ignoring the laser and putting all his points into missiles. He frequently ran out of missiles and found himself unable to fight. The build was broken, but there was nothing to indicate to the player that this wasn’t a reasonable way to develop their character. You’ve got two weapons, why is one the “main” weapon and not the other?
In response to this, I fiddled with missiles a bit. I made them more plentiful. I enlarged the blast radius. I upped the damage. But that only led to a new problem…
I had a homing missile powerup in the game. If you had it, you could fire a missile into a crowded room and it would blow everyone to bits. You didn’t need to aim or even expose yourself to enemy fire. All you had to do was fire a missile into an open space and back away. Once everyone was dead, you could gather up all the dropped XP, shields, and missiles and begin bombing the next room. It was overpowered, boring, and not the game I was trying to make.
Without the homing powerup, missiles were very, very hard to aim. Even with a mouse. Using a controller, they were almost impossible. You had to get close, and even if your aim was true the robot was likely to have moved around a bit by the time the missile got where it was going.
This was one of the things I hated about FTL: You were at the mercy of the stuff you found. Only this is WORSE than FTL, since you can LOSE powerups. You could get the homing powerup and yawn your way to victory with missiles. But then you make a mistake, die, and lose the powerup. Suddenly your build is invalid and the game is ten times harder. Suddenly the whole game hinges on this one powerup and not on player skill. The experience becomes very volatile and driven by random chance.
No no no. This is not what I want.
Sure, I could probably salvage the feature if I was willing to spend a ton of time fussing with it. Maybe foes should drop missiles based on how many you have? Maybe AI should hold still if a missile is heading for it? Maybe speed the missiles up? Maybe take out the homing powerup and just make homing a property of the missile skill? Maybe mess with the blast radius? Maybe try different text to explain missiles to the player?
I could make all these changes in an attempt to make missiles more situationally useful. Maybe if I tweaked the numbers just right, eventually I’d make missiles useful in situation A, less useful in situation B, and the player would understand the difference. I think this would take a long time and involve a lot of arbitrary rules. The feedback I’m seeing is telling me the entire premise is flawed and at odds with the game I’m trying to build.
So let’s try something else:
I wanted missiles to be a special-case problem solver for bosses and clustered foes, so why not just build a system around that assumption? I rip out the whole missile system and replace it with a “smartbomb”. Smartbombs automatically home in on foes. When they destroy a foe it causes an explosion. If that explosion kills something, it triggers another. So now the player can chain explosions if they can get foes to bunch up.
(Okay, this does require one slightly arbitrary rule: When a robot fires a missile, the explosion instantly does damage to everything in the blast radius. But a smartbomb has the explosion animate first, and does the damage at the END of the explosion animation instead of at the start. I admit this is kind of bullshit, but without this distinction we’d either have the player be able escape explosions without taking damage, or chain explosions going off all at once instead of being, you know, a chain. I’m not too worried abut this discrepancy in behavior. The AI is too dumb to fly out of the blast, so the delayed damage works in the player’s favor by letting more victims bunch up in the killzone.)
I don’t want the player to sit around sucking their thumb waiting for the smartbomb to recharge, so it recharges based on kills. Just blast bad robots with the laser and every few minutes you get a “smartbomb ready!” message and can start looking for a good opportunity to pull the trigger.
If you can kill a really big group at once then it’s just barely possible to have the smartbomb recharge instantly. I’m okay with that. It’s really only possible in the huge crowds in the latter stages of the game, and even then it’s kind of a risky thing to do.
This improves the game right away. I find there’s a certain tension to smartbomb use. You want foes to bunch up as much as possible to make a chain nice and big. This generally involves rounding up a really big and dangerous group of foes. This creates another incentive for the player to get in the and dogfight instead of trying to hang back and engage foes through a choke point. You can play that way if you want to (and if you’re playing on hardcore mode, it’s probably advisable) but your smartbombs will be less satisfying to use. If players are like me, they’ll probably be tempted to stick their neck out a bit and try to make the mob larger before they pull the trigger.
The other change to the game is based entirely on feedback and suggestions from people in the comments. Earlier in the series I remarked that foes can’t hurt each other with missiles. Late in the game, you’ll encounter big crowds of missile-based foes. If their missiles could hurt each other, then the entire group would detonate instantly as the guys in the back began shooting. I could have the ones in the back hold fire if an ally was in the way, but this would make it so large groups weren’t really more dangerous than small ones, because most foes would just patiently sit at the back and wait for the field to open up. Making the AI smart enough to spread out and not get in each other’s way would be prohibitively difficult and time-consuming. And even if I did all that work, it wouldn’t really make the game more fun. The player is likely looking for a chance to be clever and turn missiles on their enemies, and all this fussing wouldn’t bring us any closer to that goal.
Some people suggested having missiles act sort of like torpedoes. Missiles are harmless until they get close to the player, at which point they become armed and can hurt anyone. I tried it. It works.
Like smartbombs, this is a feature that encourages reckless behavior in the name of fun. Blowing up some robots with their own missiles is really fun, but you have to be willing to dance with missiles to pull it off.
This is exactly the sort of thing I was hoping to work on when I started this project. I don’t know if the final product will be any good, but at least I’m doing something interesting and different. Of all the projects I’ve worked on here, this is my favorite.
Top 64 Videogames
Lists of 'best games ever' are dumb and annoying. But like a self-loathing hipster I made one anyway.
Push the Button!
Scenes from Half-Life 2:Episode 2, showing Gordon Freeman being a jerk.
Why Batman Can't Kill
His problem isn't that he's dumb, the problem is that he bends the world he inhabits.
Mass Effect Retrospective
A novel-sized analysis of the Mass Effect series that explains where it all went wrong. Spoiler: It was long before the ending.
There are two major schools of thought about how you should write software. Here's what they are and why people argue about it.