Workshop troubleshooting

Public release 0.2.2 · Minecraft 26.3 / Fabric. Release boundaries.

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.

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.

Shared Music Library is missing or a track cannot be selected

Production Workshop 0.2.4 supports core 0.2.0/0.2.1/0.2.2, but library management needs the connected 0.2.2 server's music capability and an owner login from that server. Opening the website alone doesn't provide its files. Confirm the installed server jar, selected origin and session; restart after a jar change and open a fresh login.

Refresh the library after a revision/reference-impact refusal and review the new impact before confirming. An in-use track cannot be deleted. Library writes happen globally when confirmed; template-local sound uploads remain draft media. Use in open template still needs Save draft → Publish draft, then /boss reload for an already loaded encounter. See the music guide.

The website reports an unsupported version

Check the installed core version and server status, then inspect the production site's build-info.json. The recorded Workshop 0.2.4 release supports core 0.2.0, 0.2.1 and 0.2.2. Shared music management additionally needs the connected 0.2.2 server's advertised capability.

Keep unsupported writes paused. Read the reason instead of bypassing the gate; installing a jar doesn't update the website. Use standalone Import/Download for local recovery where available. Website/API checks are separate from a real-owner session and Minecraft gameplay acceptance.

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. Stable 0.2.2 needs a manual reload for the autocomplete 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.

Download JSON to preserve browser edits.
Load and review the Active version under Saved templates.
Reapply only the intended fields, preserving newer spawn and arena coordinates.
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, template-local OGG uploads go into the draft's media folder. Those active files only change after you successfully publish. Music Library uploads/replacements/deletions are separate global writes when confirmed.

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

Download JSON first if you need to preserve unsaved browser edits, then refresh. Check the production host/build and whether the preview's texture requests succeed. A browser preview failure is separate from the core's in-game skin rendering; record which surface failed in your report.

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.