Not everything I test for a profile makes it into the final version. Commandos 2 is my clearest example. A command has to prove it's needed before it ships. One didn't.
The rule I test every command against
Before I call a command "done," it needs at least two clearly different ways to say it. Neither one can get confused with anything else in the profile.
One phrase isn't enough. Maybe you're tired, or in a rush, or wearing a headset with a weak mic. If there's only one way to trigger a command, a small change like that can make it stop working — and you won't know why. You'll think the command is broken, when the only thing broken is that you only ever gave it one way to recognize you.
For Commandos 2, that meant building real alternate phrases, not just similar-sounding words:
- "Blade" and "dagger" both had to trigger the same melee attack.
- "Execute" and "eliminate" both had to trigger the same silent takedown.
- "Gun" and "long gun" both had to select the same weapon, without accidentally matching a different one.
I tested each pair several times before I trusted it. I said each version many times, in different orders, and checked that neither one ever fired the wrong command. I also tested them mixed in with the rest of the profile's vocabulary, not in isolation — a pair of phrases can get along fine on their own and start colliding the moment the full profile has 70 active commands.
The command I pulled
Early in this same profile, I added a voice command to open the in-game map. It made sense — hunting for the map key mid-mission breaks your focus. I built it, tested it, and pulled it the same week.
It didn't fail because it was impossible. It didn't meet my own standard. In real sessions, it wasn't reliable enough for the critical moment of a mission — exactly when you need a command to just work. So instead of shipping something that could fail you when it mattered most, I pulled it. The map stays on its normal key for now.
I tested it against the same rule as always: two clearly different phrases, zero confusion with the rest of the vocabulary. The first phrase worked fine on its own. The second, the alternate it needed to pass, kept getting confused with two different movement commands no matter how I adjusted it. I could have forced a third, stranger option, but that would have changed the problem, not solved it.
This is the part of testing nobody sees from outside. For every command that ships, there's usually one that got built, tested, and quietly dropped.
Why I'd rather a profile do less than be less reliable
I'd rather a profile do less, every time, than do more and fail you once, right when it matters.
If a game profile ever feels lighter than you expected, this is usually why. A missing command was tested, not forgotten. See the full Commandos 2 command list and check what stayed in.