My opponent had just put three creatures onto the board in one turn. It was my move, and I was going through my hand — block, kill one before combat, take the hit and swing back later? — when the game, without me saying a word, passed to the next turn.
I hadn't touched the keyboard. I hadn't said any of my commands, at least not that I remember. The turn was just gone, with all three creatures still sitting there and my answer half-decided.
A profile EchoControl doesn't ship with
Magic: The Gathering Online isn't one of our supported games — it's not even the kind of game people picture when they think of voice control. That wasn't going to stop me from playing it: I built my own profile with the Custom Profile Builder, the same tool we already covered here — a table, no code, where each phrase maps to a key.
What we don't always mention is that none of this is built for shooters only. A voice command doesn't know whether it's in the middle of a firefight or waiting its turn in a card game — it just hears a phrase and presses a key, whichever key that is. I set up "next"/"pass"/"continue" to pass priority and end my turn, a couple more phrases for combat steps, and one to open the game log. Five minutes, same as with any of our supported games — same form, no difference just because it's a card game instead of a shooter.
The mode that listens hardest
EchoControl has three ways of listening, and the difference between them isn't just the name:
- Sensitive — picks up a quiet voice, and doesn't need much confidence from the engine before it accepts a command. Built for when you're not going to speak loudly.
- Standard — the middle ground. You need to speak at a normal, clear volume, no shouting or whispering.
- Push-to-Talk — only listens while you hold down a key. Zero accidental commands, at the cost of remembering to press it every time.
Sensitive made sense for a card game: I'm not shouting "reload" mid-firefight, I'm slouched in my chair, Magic Online in one window and the game log in another, talking quietly. I turned it on without a second thought the first time I opened the profile.
What actually happened
My wife said something to me — not a command, just an ordinary sentence people say on the couch — while I was still looking at my hand. And somewhere in that sentence, the engine found something close enough to one of mine. "Next". "Pass". "Continue". Three ordinary words that slip into any conversation without anyone noticing, and all three were on my command list.
I don't know the exact word that triggered it, and I'm not going to pretend I do. What I do know is the result: while I was still working out how to defend, the turn had already passed, three creatures still sitting there and no answer played.
The engine doesn't tell "this is a command" apart from "this sounds like one". It just matches.
Not just a shooter problem
It's easy to assume commands only slip in during noisy matches — music playing, people shouting over team voice chat. This happened in my living room, in silence, with Sensitive turned on precisely because there was no noise to talk over. The same setting that let me play at a whisper is what let through a sentence that was never meant for the game at all.
I don't have a clean fix for this, and I'm not going to pretend I do. What I did afterward: I dropped "yes" and "right" from the list I'd first tried — too close to anything you might say without meaning to — and kept just "next" and "pass," words I use less often in normal conversation than in the game. And if I know someone's going to be talking near me while I play something that actually matters, I switch to Standard before I sit down, even if that means speaking a little more clearly than I'd like.
Next time my opponent drops three creatures at once, I want to be the one who decides when my turn ends. Not the background noise in my own living room.