CLOCKWORK BOSSESStable wiki
STABLE0.2.2 · Public release documentation.
Stable documentation
On this page

Clockwork Bosses 0.2.2

Public release 0.2.2 ยท Minecraft 26.3 / Fabric. Release boundaries.

Let's build a boss. Start with a template, set up its arena, give it health phases and attacks, then try the encounter in your world. You can change skins, sounds, player support and loot in the in-game editor without opening a configuration file.

This wiki is for public release 0.2.2, on Minecraft 26.3 / Fabric. It mirrors the release documentation alongside the GitHub wiki. The hosted Workshop builder stays at the site root. Its login and server connection are separate from reading this wiki.

Start here

  1. Install matching 0.2.2 jars and make your first boss.
  2. Choose a template or preset.
  3. Select the activation and arena.
  4. Edit the fight, then Save โ†’ Reload saved โ†’ test.
  5. Work through the playtest checklist before inviting players.

What's in 0.2.2

The release adds shared encounter music and the bundled boss1.ogg and boss2.ogg tracks. Choose a Library source and filename in Sounds โ†’ Music; neither song is selected automatically. Sounds and music explains the source, limits and backups.

Gameplay retains the 0.2.1 baseline: pupils, the burrow visibility fix, full native emergence timing and saved-box arenas. The core and Workshop connection come in one universal jar. Clients using the editor, custom visuals or audio need the matching jar; clients without it use the native fallback, subject to other installed mods' requirements.

The newer Moves library, scripted attack builder, imported boss models, custom animation authoring and portable boss projects are outside this release. See release boundaries.

Build your encounter

Save, reload and share

Save writes the selected template. Reload saved applies saved templates to loaded bosses. Editing a preset changes future copies; it doesn't update templates already copied from it. A JSON export keeps shared music references, so bring the selected audio files separately when moving servers.

Use Commands and Configuration reference for exact syntax and limits. Workshop covers connected editing; Troubleshooting covers common problems. The release record and testing evidence keep recorded checks separate from fresh gameplay acceptance.