Shadow Strategist

You don't like head-on fights. Not because you can't win them — because they're 'stupid.' Why contest mechanics when you can win before the opponent even realizes the game has started? You're the one who raids the enemy mine at minute three in an RTS, who identifies the werewolf on round one in social deduction, who uses diplomacy to make two opponents declare war on each other in grand strategy. Your weapon isn't mechanics — it's information asymmetry. You see what they can't, and you exploit the gap.

In Dota, you don't pick the mid carry — you pick that 'incredibly annoying' support hero and destroy the enemy team's tempo. In Civilization, you use your spy network more than your army. In puzzle games, you never take the intended path — you hunt for shortcuts the designers 'forgot to block.' Your joy doesn't come from 'winning' — it comes from 'the opponent not knowing how they lost.' Somewhere in your chat history, you've definitely typed: 'All according to plan.'

Teammates can never quite 'read' you. You say 'trust me, I have a plan,' but you never tell them what it is. Then things play out exactly as you predicted — and they're impressed but uneasy. You don't like explaining your thinking because explaining takes longer than executing. Your problem in teams is this: when your plan requires teammate cooperation and a teammate does something 'unexpected,' your entire scheme collapses instantly — not because the scheme is bad, but because your scheme doesn't account for the variable called 'surprise.'

The scene: you designed a perfect three-prong pincer in a team strategy game. Who goes where, when to move, attack sequence — you ran it three times in your head to confirm. Then teammate A took the wrong path and teammate B opened fire early. Your perfect plan turned into chaos in 30 seconds. You're furious — not because you lost, but because your 'masterpiece' was destroyed. For the first time you realize: you weren't 'cooperating with teammates,' you were 'using teammates as chess pieces.' Growth path: next time you make a plan, share it with your team — not as orders, but as a discussion. Let them give input. Yes, their input might be dumb — but 'a good plan with error tolerance' is more useful than 'a perfect plan that breaks on any surprise.' Leave 10% room for improvisation.