Weather Sandbox includes a weather collection that records discoveries. The developer also says players can find rare weather combinations. Public sources do not expose the collection’s complete current entry list, total, categories, rarity labels, hidden slots, discovery conditions, or rewards, so this page uses a currently documented Dex rather than pretending to know every item.
Your in-game Collection is the authority for names and completion in the current build. Copy its labels exactly, connect each discovered entry to a repeatable experiment, and keep undiscovered silhouettes or blank slots separate from confirmed weather.
Current discovery Dex
This is not a claim that the four rows are the complete Collection. They are the public feature groups currently supported by the official description. Individual entries belong in the Dex only after the current UI supplies a name or a developer source publishes it.
Record every discovery with useful fields
For each entry, capture the exact name, visible category, discovered or locked state, displayed rarity if any, discovery hint, biome, tool, starting temperature, wind, humidity, pressure, action sequence, elapsed time, date, and current update context. Leave a field blank when the UI does not provide it.
The most important connection is between the Collection entry and the experiment that triggered it. A screenshot of a filled slot proves discovery, but not the route. A screenshot of values proves the inputs, but not that the Collection recognized the result. Record both parts in the same trial.
If the game reveals a hint after discovery, preserve its wording separately from your own explanation. Your route can describe what you did; the in-game hint remains the source for what the developer chose to disclose.
Build a clean collection run
Start from a recorded baseline in one biome. Test each variable alone and check the Collection after every repeatable visible change. Then test two-input combinations around the responses you already understand. This is slower than randomizing all four inputs, but it makes every new entry easier to reproduce.
When you discover something, reset the simulation and repeat the exact sequence. Confirm whether the Collection entry remains unlocked and whether the weather can appear again. Persistence and repeatability are separate facts.
Move to another biome only after the route is stable. Keep all four inputs and tools identical. If the entry triggers in one biome but not another, record the difference without calling the weather biome-exclusive until repeated.
Distinguish weather, nature, and progress
The Collection is described as a weather collection. Forest growth, fire, and flooding are also official features, but public information does not state whether each has a Collection entry. Do not add a nature event to the weather Dex solely because it happened during an experiment. Wait for the in-game Collection to recognize it.
Contracts may ask you to create a result, and their progress can support that the game recognized an action. Contract completion is still not automatically a Collection discovery. Record the Collection screen and contract screen independently.
Biome and tool unlocks belong in Progression. Their names may be useful discovery context, but they are not weather entries. The Weather index handles phenomenon identification, and Nature tracks ground reactions.
Filter your personal Dex
Discovered
The current Collection visibly records the entry. Keep its exact name, date, and triggering trial.
Observed only
You saw a distinct result, but the Collection did not name or record it. Use a neutral description.
Developer named
The official description confirms the phenomenon group, but not necessarily a specific Collection slot.
Community reported
A player shows the correct game and a detailed result, but you have not independently confirmed the entry.
Locked or hidden
The UI shows an unavailable slot or count without a name. Do not guess its identity.
Needs retest
An old discovery lacks current values, biome, or update date. Reproduce it before using the route.
On a small screen, these status cards remain readable without a wide table. Use the same fields when comparing discoveries with another player.
Handle tornado types and rare combinations
A third-party tracker recorded a “TORNADO TYPES UPDATE” event title, which suggests the current build deserves inspection. It does not provide the exact type names or prove how the Collection organizes them. Add a tornado type only when the live UI names it, the Collection records it, or Beyond Average publishes the name.
For a rare combination, require more than an unusual visual. Capture the new Collection entry, then reproduce the starting state and action sequence. Do not assign a drop rate or rarity probability from how many attempts it took; a few trials cannot establish probability, and the game may use hidden context.
If two players report different names for the same visual, compare spelling, update date, biome, and Collection category. The game may have changed or the events may be distinct. Keep both reports unresolved until the current UI clarifies them.
Recover a missing discovery
If a result appears but no entry unlocks, wait for the event to complete and reopen the Collection. Confirm you are in the correct Experience and that the result has an in-game name. Check whether the same entry was already discovered, whether a contract or tool changed the context, and whether your session started before an update.
Repeat from a clean baseline. If the result is visible twice but never recognized, classify it as observed rather than forcing it into the Dex. The Collection may record only selected phenomena or require a condition the public description does not explain.
If an unlocked entry later appears missing, record the account, session date, and update context before resetting anything. Public sources do not explain save behavior, so avoid claiming a wipe or bug from one screen load.
Completion questions
How many weather entries are there?
No complete official total was found in the public sources checked here. Use the current in-game Collection, and distinguish visible slots from hidden or future entries.
What are all the rare weather combinations?
A complete verified list is not publicly available. Record exact names and conditions only after the current Collection recognizes them.
Does every storm count?
The official description confirms storms and a weather collection, but does not state that every visual storm state creates a separate entry. Check the Collection after a recognized event.
Can a Collection route change after an update?
Yes. Keep a check date and repeat old combinations after major changes. The Updates hub records current official timestamps without inventing patch details.
Evidence note
The existence of the weather collection and rare weather combinations comes from the official Roblox Experience description checked September 26, 2026. All exact entries, totals, categories, rarities, conditions, rewards, hidden slots, and persistence rules remain current-build data.