Weather preset for map setup

Use this preset at the top of a map setup pack when rain, thunder, and changing weather would make screenshots, particle cues, or player routing harder to review. It is a small command, but it belongs near gamerules and time because it controls the world state every later command assumes.

The Weather workbench keeps the weather kind and optional duration visible beside the output. That makes it easier to decide whether the setup should be a permanent clear command, a timed reset before an event, or a reusable line in a function pack. A copied command is only useful when the surrounding assumptions are visible: selector scope, world state, order inside the pack, and the exact output that will be pasted into Minecraft. Treat this preset as a checkpoint where those details can be reviewed before the command leaves NBTForge.

The gallery is structured around that review. The first shot shows the workbench state, the second shot calls out the field or companion module that changes player-facing behavior, and the output shot keeps the command or command pair visible. When the preset has a visible result, the in-game capture confirms the same idea in a restored test world rather than relying on a generic overlay.

Weather state is global, so a broad setup command can erase intentionally dramatic storm scenes if it runs too late. Put clear-weather setup before encounter-specific commands, then let storm presets override it only inside the scene that needs thunder.

Run the first smoke test with a narrow selector and a clean world state. Environment, utility, routing, and feedback commands can look harmless, but they often affect every player or the whole world. Confirm the command changes only the intended state, then save the exact output beside the setup or follow-up lines that explain why it exists.

If the command becomes part of a function file or command-block chain, test the copied artifact, not only the live workbench state. That catches stale selectors, wrong command order, missing setup lines, and effects that only appeared to work because a previous test left state behind.

• Keep selectors narrow until the full pack is reviewed.
• Place world setup before encounter-specific overrides.
• Save feedback commands next to the state change that triggers them.

Pair this with a gamerule and time command so the capture or playtest world starts from one known environment.

For the dramatic opposite, compare the thunderstorm boss arena preset, then add the time cinematic scene preset.