Skip to content

Build, Dev, and Play

Command Purpose Access
/build Create and change the playable world; flight is enabled Plot owner or Build/Dev collaborator
/dev Place and configure physical codeblocks Plot owner or Dev collaborator
/play Participate in the running game A player able to join the plot
/spawn Leave for the lobby Ordinary players

Dev includes Build. Granting only Build does not allow programming. Enter the plot before using its mode tools.

Player placement, breaking, and bucket edits are blocked in Play, including for the owner. A synchronous handler can use Uncancel Event for placement/breaking where supported; buckets remain blocked. Code-driven world changes are separate from player editing.

Targets used by player actions must be eligible participants. A person standing in Build or Dev is not automatically a game participant. For a reliable test, enter Play and trigger the event there.

Play movement, teleports, portals, respawns, and vehicles stay in the plot. Build and Play cannot enter the code area. Build permits a one-chunk margin around the play area; Dev permits one chunk around the combined play/code area.

When nobody is in Play, transient mobs, drops, projectiles, displays, armor stands, and similar entities are removed, even while builders remain. Item frames, paintings, cushions, players, and block entities are preserved. New transient spawning stays blocked until Play resumes.

Entering Dev installs Event, Method, Call Method, Set Variable, If, and Control tools, plus Objects. Plot owners also receive a Plot Settings shortcut. Objects is the value palette; older descriptions may call it Values.

You can rearrange tools. Entering Dev installs the defaults again rather than restoring an old inventory snapshot. Displaced items are preserved through overflow recovery; open Objects → Recover Items if the inventory was full.

/reset restores the current mode’s default inventory. It is not a world reset, plot deletion, or undo command.