There's a specific feeling that's easy to love in games. It's that half-second of horror just after you've grabbed something you were absolutely certain was good - and it wasn't. Your brain says yes, your instincts say yes, and then the game says no, actually.
Most game designers treat deception as a cheap trick. A gimmick. I think they're wrong, and I'll tell you why.
The Problem with Obvious Danger
Think about how most games communicate threat. Red means bad. Skulls mean death. Spiky things hurt you. It's all very legible, very safe, and honestly a bit boring once you've played for five minutes.
When danger is obvious, the player's job becomes pattern recognition on easy mode. You see the thing, you avoid the thing. Done. There's no genuine tension there - just a checklist.
The more interesting question is: what happens when danger looks like something you want?
Mimicry as Mechanic
Nature figured this out millions of years before game designers did. Plenty of animals and plants survive by looking like something they're not - harmless things that look dangerous, dangerous things that look harmless. It's called mimicry, and it works because the cost of being wrong is high enough to keep the behaviour honest.
Games can borrow this directly. And the best ones do.
When Jolly Good Apps built Swipeloot, one of the things that took a surprising amount of time was what ended up being called the deceptiveness rating for traps. Every trap in the game has a score from 0 to 1 reflecting how closely it resembles a genuine treasure. Dynamite is a 0.1 - it's obviously a trap, nobody's fooled. But the skull sits at 0.9, because it looks almost identical to a pearl at speed. And you're moving fast. Everything's moving fast.
It's easy to be sceptical at first about whether players would find that frustrating rather than fun. There's a fine line. But the pattern that emerges is that when the deception is fair - when you can, in theory, tell them apart if you're paying close enough attention - players don't feel cheated. They feel like they made a mistake. That's a completely different emotional response, and it's a much better one.
The Difference Between Unfair and Difficult
This is where a lot of game designers get it wrong. There's an important distinction between a trap that's deceptive and a trap that's unfair.
Unfair means the player had no reasonable chance of knowing. No visual cue, no prior warning, nothing. That's just punishment for existing. Players hate it, and rightly so.
Difficult means the information was there, but using it requires skill, attention, or experience. That's a completely different thing. That's a game.
The skull-versus-pearl problem in Swipeloot is solvable. Experienced players learn to spot the difference. New players get burned a few times and then start paying closer attention. The deception teaches you something. It raises the skill ceiling without raising the floor - beginners can still play, they just haven't earned the reflexes yet.
This connects to something I wrote about in more depth when thinking about risk and reward as a game mechanic - the key is that the player always needs to feel like their decision mattered, even when it went wrong.
Speed Changes Everything
Here's a wrinkle that doesn't get talked about enough: deception is harder to process under time pressure. Obviously. But the interesting thing is that how much harder depends on the player's familiarity with the visual vocabulary of the game.
Early rounds in Swipeloot are slow. You've got time to look. But as rounds advance, items speed up, more traps appear, and your health stops refilling as reliably. The same deceptive trap that was merely tricky in round two becomes genuinely dangerous in round seven, not because it got harder to identify, but because the conditions around it changed.
That's elegant game design, I think. The trap didn't change. You did. Or rather, the environment did, and you have to adapt.
Anyway. The broader point is that speed is basically a difficulty dial for any deception-based mechanic. Slow things down and players can reason through it. Speed things up and it becomes pure pattern-matching instinct. Both are valid, and mixing them across a session creates a genuinely varied experience.
Why Players Actually Like Being Fooled
Here's the thing that stands out when you watch people play: they laugh when they get caught by a good trap. Not always immediately - sometimes there's a groan first - but they laugh.
That reaction tells you something important. Being deceived well feels like a compliment. It means the game was paying attention, that it had something up its sleeve, that there was more going on than you initially realised. It creates a kind of respect.
Compare that to losing because an enemy just had more health than you, or because RNG went against you. That doesn't generate laughter. It generates mild resentment and a desire to quit.
Good deception mechanics make failure feel interesting. And interesting failure is one of the hardest things to design. Get it sorted, and you've got something players will keep coming back to - not despite the traps, but because of them.