Time preset for cinematic scenes

Use this preset when the scene needs repeatable lighting for screenshots, hub areas, puzzle rooms, or command-pack tests. Time commands are easy to overlook because they do not create an entity or item, but they decide whether the rest of the preset gallery is readable.

The Time workbench keeps the action, value, and generated output next to each other, so a creator can choose between `set`, `add`, and `query` instead of copying an old line blindly. For cinematic setup, `set noon` is the stable default. 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.

Do not mix a baseline time setup with encounter-specific night or sunset scenes without naming the Project entries clearly. A later `/time set` line can undo the lighting that a boss, title, or particle moment was designed around.

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.

Put this near weather and gamerule setup, then let special scenes override time only when the story needs it.

For adjacent environment setup, compare the weather map setup preset and gamerule adventure map preset.