Builder Mode

Builder Mode lets players make a version of a published game within the creator’s allowed catalog. Start with one editable Scene and a small toolbox, then test editing and gameplay separately.

Prerequisites

Use the Full edition. Restricted editions with publishing hidden omit Builder authoring and its runtime. Prepare reusable Objects, a working Scene, and a backup of the creator project.

Choose a Toolbox Path

Game Settings, General has a Builder Mode switch that publishes an automatic Toybox from supported project content. An explicit Game Builder Policy lets you control Scene access, catalogs, tools, variables, imports, and budgets.

The automatic Toybox switch takes precedence over authored policies. When publishing an explicit policy, turn off that switch and run the policy’s Publish Check. Inspect the selected path before exporting; adding a policy resource alone doesn’t prove it is used.

Check Editing and Play

1. Export the Builder game and enter Builder Mode through its offered interface or Enter Builder Mode Action.
2. Select an allowed toolbox item and create a placement. Move, rotate, or resize it with the permitted tools.
3. Try a disallowed operation and verify that it is refused. Check zone, Scene, axis, and budget limits.
4. Choose Play My Version and inspect the edited game.
5. Return to editing, then choose Play Original Game. Confirm that the creator’s baseline is available.

Player changes are creation data. They don’t overwrite your editor’s .mythproj. Saving a creation, downloading it, importing it, and ordinary game progress saves have separate permissions and purposes.

If player saving is allowed, save a creation, close the game, reopen it in the same storage context, and load the creation. Test download/import on another session only if the policy permits them. Preserve game and policy identities when updating a game with existing player creations.

Expected result: players edit only allowed content, can play their version, and can return to the original. A saved creation restores under its compatible publication and policy.

Troubleshooting

If tools or items are missing, inspect the selected policy/Toybox, edition, and publication check. If saved creations aren’t found, compare browser origin, storage, game identity, and policy compatibility. If an edit affects every copy, check whether the permitted operation changes a shared default or a placement.

For chip or voxel editing, inspect their additional catalogs, permissions, and budgets. Test those capabilities in a separate small publication before adding them to a working Builder game.

See Guest Objects, Coil Programs, and saving.