Deploying

Deploying publishes saved flow changes to a Minecraft server instance through a review step.

Before You Deploy

1. Click Validate and fix any highlighted issues.
2. Click Save.
3. Confirm the flow is targeting the correct server instance.
4. Export a backup first if the change is large or risky.

Submit Steps

Editors submit deployments instead of publishing directly.

1. Click Submit in the editor header.
2. Confirm the target server shown in the modal.
3. Enable Apply on Server if the change should go live immediately.
4. Click Submit for Review.

The submission stores who submitted it, when it was submitted, the target server, auto-fetch state, command triggers, event triggers, and compiled program entry count.

Owner Review

Owners see Deploy Review History in the deploy modal.

Pending submissions can be:

• Deploy: approve the submission, write commands and events to the proxy deploy collections, and notify the target proxy server when applicable.
• Reject: deny the submission without changing deployed commands or events.

Reviewed submissions stay in the history. Each record shows who submitted it, when it was submitted, what commands and events were included, who reviewed it, when it was reviewed, the review result, and the deploy ID when deployed.

Owner Direct Deploy

Owners can still deploy the open flow directly.

1. Click Deploy in the editor header.
2. Confirm the target server shown in the modal.
3. Enable Apply on Server if the change should go live immediately.
4. Click Start Deployment.

The server instance name should match the Handler server name in that server's config.

Apply on Server

When Apply on Server is enabled, the matching server reloads commands and events after deployment. This makes supported changes go live without a restart.

Leave it disabled when you only want to upload the change and apply it later.

Deployment Log

The deployment modal shows live output for the current submit or deploy action.

For owners, the modal also shows review history with submission status, submitted-by details, approved-or-denied-by details, target server, trigger counts, command details, event details, and deploy IDs.

Troubleshooting

Problem	What to check
Deployment stops before upload	Run Validate and fix missing required fields.
You see Submit instead of Deploy	Your account is not currently detected as an owner for this flow. Re-login if your role just changed.
A submitted change is not live	Ask an owner to open Deploy Review History and approve the pending submission.
Change does not appear in game	Confirm Deploy to matches the server name and Apply on Server was enabled. Otherwise, fetch it manually using /handler fetch on the server
Command is unavailable	Check command name, enabled state, permission, allowed sender type, and cooldown.
GUI click does nothing	Make sure clickable GUI items point to a Function node.
Button click does nothing	Make sure the message button ID matches a Button Trigger action ID.