Versions and release status

Not sure which instructions apply to your build? Start here. The mod, Workshop website, and testing tools have their own releases. Their version numbers don't have to match, but the website does need to explicitly support the mod you're running.

Recorded status

The October 14, 2026 publisher receipt records beta website 0.3.0-rc.5, restoring the Warden preview textures while retaining rc.4's exact mod support. The rc.4 metadata was independently checked earlier; rc.5 checks below are publisher-reported. Production remains reported at 0.2.2 in the release receipt; it was not independently fetched again for this wiki update. Before connecting a particular build, check that site's build-info.json and your running server's status.

Component	Recorded version	What that means
Stable Clockwork Bosses	0.2.0	Preserved stable baseline for Minecraft 26.3/Fabric. Includes merged Workshop integration, optional-client fallback, permissions, schema and experimental API revision 1.
Local core checkpoint	0.3.0-beta.6	Packaged and automatically tested. Adds encounter PvP protection, Better Combat/potion handling and cosmetic face rules. Not deployed; real multiplayer checks remain pending.
Production Workshop website	0.2.2	Last verified hosted production release, with saved-draft publication safeguards. A later local build does not update it.
Beta Workshop website	0.3.0-rc.5	Publisher-reported deployed beta with restored Warden preview textures. Exact support remains beta.6, beta.5, beta.4, beta.3 and 0.2.0; the beta.6 Java HTTPS check reports writes allowed.
Workshop source and deployed beta	Beta.6 schema/controls	The release receipt verifies matching hosted assets/schema and disposable real-HTTPS relay/SDK tests. This does not prove a fresh licensed Minecraft login or multiplayer combat.
Test Mod / Boss Observatory	0.4.1-dev	Basic selected-template browser combat workflow verified in a local disposable profile, with exact beta.5 core dependency. Native F8 GUI/runtime and broader acceptance remain unverified; no live install or publication.

A website that supports beta.4 doesn't automatically support beta.6. The mod checks for its exact version and the capabilities it needs before allowing changes. See Workshop for how that check works.

Beta texture restoration: 0.3.0-rc.5

The beta-only release build is 0ce07f501d56db72d563563117731c0152ccb7071daa9c6d7d9d2a99c6f581b6. The publisher reports all 29 hosted asset hashes verified, all four Warden PNGs returning HTTP 200 with CRC/decompression checks passed, and a fresh browser showing the textured vanilla preview.

Public rc.4 code/assets are unchanged; the release adds the four original PNGs through private inputs and an ignored capture. They were not tracked or pushed to GitHub. Future beta uploads need that private texture overlay after public-source preparation; keep the images and texture-containing capture out of wiki/GitHub.

Declared mod support and required capabilities are unchanged. The publisher reports exact-jar HTTP and SDK/Java/workerd checks with 0.2.0 and beta.6, including the actual beta.6 Java HTTPS reader returning writable=true. These are website/API checks, not new gameplay compatibility or player-login evidence. Production remains reported at 0.2.2 with all 27 asset hashes unchanged; no Minecraft jar was installed or server restarted.

Beta website update: 0.3.0-rc.4

The historical rc.4 beta build is a2a517b5843f903a3f2d79c046939f5eded9e866d282277817e3855c00d4735a, with no required capabilities in its public declaration. The release receipt reports all 25 hosted asset hashes matching the capture, a schema matching the exact beta.6 jar export, and that jar's Java HTTPS client returning writable=true.

The receipt also records 41 editor and 40 relay checks, plus disposable real-HTTPS login-link exchange, save/upload/publish, permissions, isolation and recovery checks. These are API/relay/SDK results, not a new licensed Minecraft login, combat playtest or real speaker-output test. No Minecraft jar was installed or server restarted.

The October 13 rc.3 checkpoint remains historical: it excluded beta.6 and lacked those face controls. The website update resolves that declared support gap; it does not deploy the beta.6 mod or finish Observatory.

What stable 0.2.0 includes

Install one universal core jar with Fabric API. No separate web companion is needed. Optional Workshop access uses an outbound TLS WebSocket to a separate Cloudflare relay; no website or inbound web listener is bundled.

Players without the core use native presentation/gameplay fallback. Modded clients need the matching core for the native editor, custom appearance/audio and enhanced presentation. Other installed mods/addons can still require client copies.

The addon API is experimental revision 1 even in a stable core release. Exact core pins and addon-specific testing still apply; there is no arbitrary-mob or cross-version binary compatibility promise.

What beta.6 adds

• Encounter PvP protection with fresh arena checks; attributed player harm is blocked while boss/environmental harm remains separate.
• Potion placement that reads actual inventory and leaves personal equipment in place, including Better Combat two-handed cases. Full inventories fail safely.
• Angry, Neutral, Curious and Sad eyebrow shapes, independent rotation and optional cosmetic rules for attacks, hits and target changes.
• Automatic template-list/autocomplete refresh after successful publication. Running encounters still require /boss reload to apply changed settings.

The checkpoint passed 56 native server tests without Better Combat and 63 with it, including a separate 63-test Better Combat/Lithium run, native face/editor checks and 68 local website checks. Compatibility and testing records exact versions, additional results and limits. These are not real networked multiplayer tests.

Unfinished work

Observatory 0.4.1-dev now has a verified local profile/browser workflow: choose a real template and sword/axe test preset, Save, Start and read saved results. Restart recovery and cancellation cleanup are covered. This doesn't validate the native F8 GUI's runtime/login/rendering, Better Combat combos or a live deployment. Its exact core dependency remains beta.5, not beta.6 or stable. See the Observatory checkpoint for artifact identifiers, measured runs and limits.

Combat reactions, stagger/vulnerability, expanded combat APIs, and support for arbitrary mobs are still planned. A boss changing its expression when you hit it is just a visual effect for now.

Reading old evidence

Earlier release and preview sections retain their counts and results as history. A statement that a feature was “source only” or a host was “current” refers to that section's original checkpoint. Use this summary and the later exact artifact results for current instructions.

The migration preserved artifacts/history and passed compilation/UI checks without a fresh runtime playtest. It did not commit, push, install or deploy the projects. The playtest checklist records the human checks still required.