The Firebird
Commoner
Hi folks, I’ve been working on a project generating weather in RPGs and I wanted to share it. The concept is—given some environment, can we realistically generate its weather in a way that is easy to use at the table? I'll start out with my answer, which looks something like this. The idea is, each day is reduced to a weather code, giving temperature, cloud cover, and rain. Then you get a d100 table for that type of day, which determines how you transition to the next day. (The percentages on the first column give the average probability of encountering that type of day).
Now the background: I wanted to make a system that (1) relies on real data; (2) is algorithmic; and (3) is easy to apply to new environments. The idea being, then I can make it work anywhere we want.
To do so, I took data from the ERA5 dataset (accessed via Open-Meteo)—this is a big global weather database, that has weather for any location in the world since 1940. People generated this by taking weather records from different stations, combined with modeling efforts, to get global coverage. That means there is a record we can use for the weather of any place we want, with decades of data.
Then, I reduced each data to a code, for temperature, precipitation, and cloud cover. (I missed out on wind—which is complicated—and fog—where the data is poor). I then computed the day-by-day transition probabilities: e.g., if it is hot and overcast today, how likely is it to be hot, overcast, and rainy, tomorrow?
Here is a breakdown of the thresholds I used:
Temperature
Cloud Cover
Precipitation
Doing this, and ignoring low probability (<1%) days, gives you a ‘transition matrix’ for a particular locale. I then cast these into d100 tables. The idea here is, you find the type of day you are on, roll on the corresponding column, and use it to pick the new kind of day.
With a d100 transition matrix, you end up matching the transition probabilities pretty exactly. Here, for example, are the transition probabilities you get by rolling vs the data for Chicago winter (NB: transposed from the above).
Match to Real Data
And some other examples that I've generated.
Cairo Summer:
Seattle Autumn
Singapore Spring
I’m planning to build these for a wider variety of locales (e.g., 1 for each of the major climate classifications). But before I do I wanted to share these and get feedback about parts that are missing or ways they could be improved. I’ve written more about the process, mostly for my own edification, if anyone is interested in more depth (part 1, part 2, part 3, part 4, part 5). I’d love to hear any feedback or comments, positive or negative.
Some outstanding questions I have:
- Seasons will differ for different locales. How do I move past Spring/Summer/Autumn/Winter? I suppose location specific?
-Are the temperature, precipitation, and cloud cover cutoffs reasonable? Does anyone have clever ideas to get fog or wind?
-Is the presentation intuitive or confusing? Are there ways to improve it?
-Is 1% a reasonable cutoff, or would including more extreme (or less extreme) weather be preferable?
-Are there any locations you’re interested in seeing a table for?
Now the background: I wanted to make a system that (1) relies on real data; (2) is algorithmic; and (3) is easy to apply to new environments. The idea being, then I can make it work anywhere we want.
To do so, I took data from the ERA5 dataset (accessed via Open-Meteo)—this is a big global weather database, that has weather for any location in the world since 1940. People generated this by taking weather records from different stations, combined with modeling efforts, to get global coverage. That means there is a record we can use for the weather of any place we want, with decades of data.
Then, I reduced each data to a code, for temperature, precipitation, and cloud cover. (I missed out on wind—which is complicated—and fog—where the data is poor). I then computed the day-by-day transition probabilities: e.g., if it is hot and overcast today, how likely is it to be hot, overcast, and rainy, tomorrow?
Here is a breakdown of the thresholds I used:
Temperature
Over 100 F: Extreme Heat
Over 80 F: Hot
Over 55 F: Warm
Over 35 F: Cool
Over 0 F: Cold
Under 0 F: Extreme Cold
Over 80 F: Hot
Over 55 F: Warm
Over 35 F: Cool
Over 0 F: Cold
Under 0 F: Extreme Cold
Cloud Cover
Over 60%: Overcast
Over 25%: Partly Cloudy
Under 25%: Clear
Over 25%: Partly Cloudy
Under 25%: Clear
Precipitation
Over 0.8” rain: Heavy rain
Over 0.2” rain: Rain
Over 3” snow: Heavy snow
Over 0.3” snow: Snow
Under 0.2” rain and Under 0.3” snow: No precipitation
Over 0.2” rain: Rain
Over 3” snow: Heavy snow
Over 0.3” snow: Snow
Under 0.2” rain and Under 0.3” snow: No precipitation
Doing this, and ignoring low probability (<1%) days, gives you a ‘transition matrix’ for a particular locale. I then cast these into d100 tables. The idea here is, you find the type of day you are on, roll on the corresponding column, and use it to pick the new kind of day.
With a d100 transition matrix, you end up matching the transition probabilities pretty exactly. Here, for example, are the transition probabilities you get by rolling vs the data for Chicago winter (NB: transposed from the above).
Match to Real Data
And some other examples that I've generated.
Cairo Summer:
Seattle Autumn
Singapore Spring
I’m planning to build these for a wider variety of locales (e.g., 1 for each of the major climate classifications). But before I do I wanted to share these and get feedback about parts that are missing or ways they could be improved. I’ve written more about the process, mostly for my own edification, if anyone is interested in more depth (part 1, part 2, part 3, part 4, part 5). I’d love to hear any feedback or comments, positive or negative.
Some outstanding questions I have:
- Seasons will differ for different locales. How do I move past Spring/Summer/Autumn/Winter? I suppose location specific?
-Are the temperature, precipitation, and cloud cover cutoffs reasonable? Does anyone have clever ideas to get fog or wind?
-Is the presentation intuitive or confusing? Are there ways to improve it?
-Is 1% a reasonable cutoff, or would including more extreme (or less extreme) weather be preferable?
-Are there any locations you’re interested in seeing a table for?

