A hard mechanic is not the problem.

A mechanic that feels random is.

That’s why Celeste works so well as a clarity example.

It’s hard, fast, and demanding — but most of the time you understand why you failed.

You jump too early.

You dash too late.

You miss spacing by a little.

And the game teaches you that without stopping to explain it.

✅ Good feedback teaches when it does 3 things:

- It confirms your input

You instantly feel that the game registered the jump, dash, grab, or climb.

- It shows the result clearly

You don’t just fail.

You see how you failed: bad timing, bad spacing, wrong direction.

- It helps you adjust the next try

The feedback is clear enough to improve your next attempt, not just punish the current one.

That’s the key:

good feedback turns trial-and-error into trial-and-learning.

⚠️ When feedback is weak:

every failed attempt feels the same.

So the player stops learning and starts brute-forcing.

🧰 Quick test for your game:

Take one mechanic and ask:

- Can the player feel the input clearly?

- Can they tell why the result happened?

- Can they improve on the very next try?

If not, your feedback is too flat.

🧪 Do this now (5 minutes):

Pick one interaction in your game that feels “off”.

Add one stronger feedback layer:

sound, flash, hit reaction, pause, animation, or state change.

Then test if the next attempt feels more teachable.