How often will it rain in my game if the weather follows yesterday's weather?

Weather, moods and enemy behaviour that depend on what happened just before are easy to set up and hard to predict: you pick small numbers and end up with a world that is always rainy. This entry tells you the share of each state before the player sees it.

Why this works

When tomorrow depends on today, the share of time spent in each state is set by how likely the world is to stay put versus move on, not by where it began. So you can read the long-run mix straight off the table of chances, before anyone plays.

When not to use it

Skip it when the next step depends on more than the last one, like seasons, a time of day, or what the player did, or when you need an exact schedule. Use a fixed calendar or a clock-driven rule there.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• 26 lines of example code with 4 checks that pass
• How your AI shows you that it works

Say this to your AI

Use the Spielerando entry "How often will it rain in my game if the weather follows yesterday's weather?" (read_entry weather-chain-long-run-share) in my game. Build it step by step, and show me how you checked that it works.

Or skip this and connect the MCP: your AI then finds all of this by itself.Connect the MCP