Tutorials

World

World command guide: weather, time, gamerules, and waypoints

5 min read

World commands are usually short, but they are easy to scatter across notes and old command blocks. NBTForge groups weather, time, gamerules, and waypoints so setup commands remain easy to audit.

Read inENRUDEESPT中文日本語VIFR한국어IDPLTR

Goal

A world-control command set that can be copied as individual lines or a pack.

Annotated screenshots

World modules are grouped together so environment setup stays separate from entity editing.
Waypoint commands expose locator bar color choices without forcing you to hand-edit syntax.

Step-by-step guide

  1. Open the World category and select the command family.
  2. Choose the smallest command that changes only the state you intend to change.
  3. Add related world setup lines to Project in the order they should run.
  4. Keep world setup separate from entity or datapack commands unless a project requires a full setup pack.

Why world commands belong in a project

A map or server setup often needs a weather command, a time command, and several gamerules. Adding each line to Project keeps the final copy block ordered and reviewable.

This also makes it easier to compare setup commands before pasting them into a command block chain or a function file.

Waypoint and locator workflows

Waypoint commands are useful when creators need a visible navigation marker. The visual controls help avoid typo-prone color and target edits.

If a waypoint belongs to a larger setup, save it beside the related teleport or title command.

Publish-ready check

Use this world tutorial as a repeatable workflow, not only as a one-time screen tour. After the command works in the workbench, copy the final Output or Project pack into a clean test world and confirm the copied text behaves the same way.

When a command depends on version syntax, selectors, saved project entries, or datapack resources, write those assumptions into the project title or surrounding notes. That makes the tutorial useful when another creator opens the same workflow later.

  • Test the copied command, not only the visible builder state.
  • Keep the Edition and Version choice attached to the workflow.
  • Use Project for multi-command setups and future edits.
  • Recheck warnings after importing old commands or switching modules.

FAQ

Should weather and time commands be saved?

Save them when they are part of a repeatable map setup. For one-off testing, copying directly from Output is enough.

Can NBTForge combine world commands into one command?

Minecraft still runs them as separate commands. NBTForge Project helps copy them together in a single command pack.

When is this workflow ready to share?

Share it after the copied output has been tested in a clean world or command block, and after any required version, selector, datapack, or Project assumptions are written down.