Workshop troubleshooting

Having trouble logging in, saving, publishing, or uploading files? Start here. Before refreshing or opening another template, use Download JSON to keep a copy of your edits. The server handles saved files and validation, but unsaved changes and previews are still in your browser. If the relay goes down, your fights keep running.

Login does not open

Run /boss workshop open in Minecraft. You'll need native owner permission, normally operator level 4, and an online-mode server with Workshop access enabled. Permission to edit bosses doesn't automatically give you Workshop access. You also can't generate a player login from the console.

Your login link works once and expires after two minutes. After restarting Minecraft, get a fresh link; the old links and sessions won't work. You can use /boss workshop logout to revoke your links and sessions, even during an outage. Don't share your login link.

The server needs outbound TLS on port 443; no additional inbound web port or separate companion jar is required. Workshop setup explains the canonical settings.

The website reports an unsupported version

Check the mod version, selected channel/origin, and compatibility message in server status. Then check that site's build-info.json. The website has its own version number, so look for explicit support for your installed mod version.

The October 14 publisher receipt records hosted beta 0.3.0-rc.5, retaining rc.4 support for beta.6, beta.5, beta.4, beta.3 and 0.2.0. The earlier rc.3 checkpoint excluded beta.6; that is historical now. If writes are still blocked, check the selected origin, exact installed version and reported reason rather than bypassing the gate. Installing a jar alone cannot update a website. Standalone Import/Download remains available for local recovery.

Unsupported writes/autosave stay paused. Login/logout and permitted authenticated downloads/previews remain available for recovery. Beta/dev missing or invalid metadata does not fall back to a production host. See Versions and release status.

Website support doesn't install or restart a Minecraft jar. The beta.6 artifact remains a locally tested, undeployed checkpoint. The new release's disposable HTTPS checks also don't replace a fresh licensed Minecraft login or real multiplayer test.

Save succeeded, but the boss has not changed

Save draft stores the server draft. Publish draft validates and commits that saved draft and its media. /boss reload applies saved settings/media to already spawned bosses. Wait for each successful result before the next step.

Publishing uses the saved draft, so save your browser changes first. It also doesn't reload a running fight. Beta.6 refreshes autocomplete after publishing; stable 0.2.0 and older betas need a manual reload for the name list too. Be careful with the command: /boss workshop reload reloads the connection settings, not your bosses.

Active template changed or a stale edit is rejected

Another admin, the native editor, a hosting panel or spawn/arena commands may have changed the active document after your draft was loaded.

1. Download JSON to preserve browser edits.
2. Load and review the Active version under Saved templates.
3. Reapply only the intended fields, preserving newer spawn and arena coordinates.
4. Save draft successfully, publish successfully, then reload bosses if needed.

An old download can bring old spawn and arena coordinates back with it. The revision check is there to protect newer changes. Review them, and don't force an old draft over newer work.

A save or publication has an uncertain result

If a save fails or its result is unclear, approval to publish the older draft is cleared. If you change something while the confirmation is open, you'll need to save again too. Reopen the saved draft and Active version before retrying so you know what actually made it to the server.

Transient reconnects do not replay interrupted save, upload or publish requests. A reconnect can retain a session, but restart, disabling access or changing origin revokes it. Request a new login when needed.

Sound upload or preview is missing

Upload support comes from the server opened by your login link and its schema/capabilities, as well as the matching website UI. A new core jar does not update the hosted UI. Confirm which server the link accesses.

Choosing a file for a local preview doesn't upload it. When you're connected to the server, OGG uploads go into the draft's media folder. The active files only change after you successfully publish.

Event sounds and voice lines are limited to 1 MiB minus 1 KiB / 30 seconds. Music is limited to 8 MiB minus 1 KiB / 10 minutes. Use lowercase OGG filenames without a path, and make sure the audio is actually OGG Vorbis. Renaming an MP3 to .ogg won't convert it! Use mono for normal positional playback.

If a reconnect interrupts an upload, review the saved draft before retrying. Sounds and music covers folders/playback; Workshop covers validation and backups.

The vanilla preview has no texture

Beta 0.3.0-rc.5 restores the four Warden PNGs. If an older beta tab still shows the neutral fallback, Download JSON first to keep unsaved edits, then refresh. The publisher checked a fresh page displaying Vanilla Warden texture. and the textured model. If it still fails, check which host/build is open and whether its texture requests succeed.

This browser preview fix doesn't change the core's in-game skin/rendering behavior or prove Minecraft gameplay compatibility. For a future beta upload, public-source preparation alone excludes those textures: the publisher needs the private overlay. Keep the PNGs and private capture out of wiki/GitHub.

The wrong channel opens

Version spelling and Git branch names do not select a host. An explicit testing channel takes priority; otherwise an existing relay_url remains pinned. Build-channel selection applies only when enabled by the settings, and legacy files retain their stable default.

Testing origins use separate identities. Use a separate test server/world/configuration and a fresh login for the deliberately selected host. Do not copy the production identity to another origin or expect unavailable beta metadata to redirect to production. Workshop channels explains the precedence.

What to include in a report

Include your mod version, website version/build, selected channel, roughly when it happened, what you were doing, and the exact error. Tell us whether the saved draft or Active version changed. Logs help, but remove private login links, keys, cookies, and tokens before sharing them. If you tested locally, say so; a local test doesn't confirm the same thing works through a signed-in cloud session.