Shadow Tactics: Blades of the Shogun has five playable characters. The first time I tested their names out loud, all five gave me a different problem.
Not because the names are hard to pronounce. Speech recognition doesn't hear words the way you'd expect, and short names are the hardest case for it.
The bug: saying a name fired the wrong command
I tested the character "Hayato." I said "go to Hayato" to switch to him mid-mission. Instead, the game made him crouch. I tried again. Same result.
The recognition engine wasn't hearing "Hayato" at all. It was hearing "get up," or sometimes just "to," hidden inside the name. One of those pieces matched the crouch command instead.
That was the part that surprised me most, after years of testing software: the engine doesn't fail loudly when it mishears something. It just picks the closest command it did recognize, and runs it. Say a name wrong enough, and you don't get an error. You get the wrong action.
The first time it happened to me, I assumed there was a bug in how the "select" command was set up. I spent almost an hour looking there before I suspected the name itself. It's a kind of failure that doesn't look like any other bug you'll have seen in normal software — there's no error trace to follow, just an action different from the one you expected.
I checked the rest of the characters too, once I knew what to look for:
- "Mugen" was often mistaken for the number "one."
- "Tanuki" came through as "down yuki."
- "Sake" (a command word, not a character) was heard as "use cycle."
None of these are strange, rare mistakes. This is what happens every time a short, foreign-sounding word gets compared against a list of short English commands. Something on that list will always sound similar enough.
The fix: give the name more to work with
One short word is easy to mishear. A full phrase almost never is.
I stopped listening for "Hayato" on its own. Instead, I rebuilt it to only respond to full phrases: "go to Hayato," "camera on Hayato," "find Hayato." The bare name no longer triggers anything by itself. The extra words give the engine more to compare against, so a "get up" hidden inside the name doesn't win anymore.
I also had to undo an earlier fix. An early version let "to" work as a shortcut on its own. It started selecting a character on nothing but background noise, because "to" is a very common sound. Removing that shortcut fixed more problems than adding the full phrases did.
I tested the fix across all five characters, over several sessions, checking two things each time: did the right character get picked, and did nothing fire on background noise. I also recorded a session with music playing on purpose, since that's a lot closer to how most people actually play than the quiet room I usually test in.
What this means for any other game with unusual names
If a game you love has character or item names that don't sound like normal English, you'd have this exact same problem. Voice control can still handle it. Short, unusual words just need to live inside a full sentence to work reliably. That's a design choice, not something you simply have to accept.
Want to see this handled for a specific game? Try EchoControl on a profile with a cast just as unusual as this one — the full Shadow Tactics command guide lists every phrase that made it through testing.