Field notes

Weather is the second player

The weather began as decoration. Then it started making decisions. A short field note on building a sky that participates.

SystemsOctober 21, 20267 min readBy the developer

In the first prototype, rain was a particle effect. It fell in front of the tree, made a pleasant sound, and changed nothing. The tree still needed the same amount of water. It took about ten minutes of playing to notice that the sky was lying.

Weather only becomes interesting when it joins the argument. Now rain raises the soil moisture and can spare you a watering day. A heatwave pulls water out of the ground and makes a young canopy brittle. A storm brings water and damage in the same gust. Frost does not care how much you love the tree; it cares whether the soil was mulched and whether the roots had time to settle.

Nine skies, one grammar

The game has nine weather states: clear, breeze, overcast, rain, storm, heat, mist, frost, and snow. Each has a small set of effects, a palette, a sound profile, and a way of moving the tree. The states are intentionally limited. A larger list would make the sky feel like a random number generator. A smaller one would make it feel like a wallpaper.

  • Rain and storms refill the soil, but storms test the canopy and leave the meadow flattened.
  • Heat is dry, bright, and slow. It is the only weather that makes watering feel urgent rather than pleasant.
  • Frost is quiet and structural. Mulch, roots, and timing matter more than effort on the day itself.
  • Mist does almost nothing to the numbers. It changes how the tree looks, which is its own kind of effect.
  • Breeze is the visual signature of the game: leaves moving before anything else does.

The forecast is always visible for today and tomorrow. This is a deliberate kindness. I want players to plan around the weather, not be ambushed by it. The story can still surprise you with a long heatwave or a gale, but the surprise is in the accumulation, not in a hidden dice roll.

The sky is not a difficulty slider. It is the other character in the scene, and it does not owe you an easy day.

Making wind visible

Wind is the hardest weather to make legible in a browser game. On a still screen, a vector of moving air is invisible until it touches something. So the tree does most of the acting. Its canopy leans first, then the grass, then the loose leaves. In a storm, the motion becomes slightly wrong on purpose — the canopy lags behind the trunk, as if the tree is being pulled in two directions.

The 3D scene uses a deliberately limited vocabulary: a low-poly tree, flat-shaded leaves, fog, and a few moving particles. Most of the drama comes from light and color rather than polygon count. That choice keeps the download small — the game engine is loaded only when you press play — and keeps the tree readable on a phone.

Weather as memory

At the end of the story, the summary does not only tell you what you did. It tells you what the sky did. The week you were away, the storm that arrived after you pruned. The frost you prepared for. The heat you did not.

That is the secret reason the weather exists. It gives the season a memory that is larger than the player. You are not the only author of what happened here. You were one of two.