The valley doesn't move.
The air does.
At first, nothing happens. A leaf just sits there, caught between two stones, like it's waiting for something you can't see yet.
Then you draw a line. A soft current forms. The leaf shifts… slowly… then faster — carried by something that was never visible to begin with.
Wind Valley isn't about speed. It's about understanding how motion begins.
Where the idea
came from
This game didn't start with mechanics. It started with a question — what if movement wasn't controlled directly?
What if you never touch the object… only the force behind it?
I was just doodling physics stuff when I noticed all this dust floating around outside my window - construction next door, I think. Watching how it moved around... that's when I figured it out. That's the exact vibe I wanted to capture.
Not as a game. As a behavior.
You don't move objects.
You move what moves them.
Each level's basically its own little world with its own rules.
You create currents — simple at first. A direction. A push. A gentle
flow.
-
Leaves drift
Light and responsive to gentle currents
-
Gliders soar
Catch momentum and glide far
-
Balloons rise
Float upward and curve with the wind
-
Your goal is simple — guide
them home.But the way you
get there… never is.Nothing is forced.Everything reacts.
What you actually do
-
1
Draw wind paths
-
2
Rotate airflow nodes
-
3
Manage energy
-
4
Use terrain
You'll start thinking in straight lines.
Then curves. Then timing. Then chain reactions.
Eventually, you stop thinking
in moves
— and start
thinking in systems.
Yeah, it's trickier than it looks at first
The first levels teach you control.
The next ones take it away.
-
Limited moves
-
Multi-object coordination
-
Delayed reactions
-
Chain-based solutions
There's no single answer.
Only better understanding.