Looking for a setting, its limits, or what it inherits? This page covers stable 0.2.0, with later beta fields labelled separately. Your generated template.json comments and the editor's field descriptions explain the fields available in the build you're actually running.

Active templates live at:

config/clockwork-bosses/boss-templates/<template>/template.json

The file supports JSON with // comments through Gson. Strict JSON also works. Generated note blocks group explanations above each section. Saves preserve unknown values and regenerate comments, so hand-written comment wording is not retained exactly.

The JSON examples in this wiki are valid partial objects. Copy their fields into the named sections of your existing template. Don't replace the whole template with one of these examples.

Use Save for editor changes, then Reload saved to apply saved templates to loaded bosses. For external file edits, use /boss reload. Neither action loads a new jar.

The experimental schema foundation reuses the existing core defaults/help, client/server editor types and bounds, and API BossSetting declarations. It exports JSON Schema Draft 2020-12 with x-clockwork annotations for inheritance, override scopes, ordered collections, percentage display and action settings. No separate list of website limits is introduced. x-clockwork.numeric_input also exports the real decimal parser limits for declared edits; ordinary JSON Schema checks values rather than lexical input bounds.

Schema defaults describe creation/form values; importing a template must not automatically populate missing fields. Null phase overrides use base settings; Attack-child overrides use their parent. Null dormant-darkness fields inherit the first phase's compiled darkness. Unset phase darkness uses its legacy base fallback, not dormant darkness. Registered action settings use their own declared defaults rather than inheriting another action object.

Schema revision 2 adds x-clockwork.omitted rules separately from creation defaults. For example, omitted loot.source means table, while newly created templates explicitly choose entries. server_default gives no portable literal; keep that field absent when saving an imported file. Missing support sections remain disabled. Null subphase_order means sequential, null roar_between_subphases enables interludes when roars exist, and null loot disables template rewards while retaining vanilla drops.

visible_when shares the game editor's action/geometry selectors with tooling. Legacy attack counts, recovery duration and combat overrides appear only where used; registered actions use their declared action_settings. Hidden values remain stored. The core roar's file field accepts a lowercase OGG basename up to 68 characters, or blank/null for the native roar. Actual media/addons/registries/ world checks are explicitly listed in server_only_checks.

Spatial range fields export x-clockwork.automatic separately from creation defaults and legacy omission. Null inherited overrides remain null; missing imported fields stay missing on save. Automatic audio uses arena geometry, not activation geometry; music keeps its arena audience. See Sounds and music.

The schema handles portable types, ranges and structure. Server validation still checks cutoff order, inherited attack budgets, reward quantity relationships, geometry, addon availability, registry IDs and media contents. These remaining checks are listed in x-clockwork.runtime_checks. A first experimental browser editor now uses these definitions; it does not replace server validation. This schema and automatic sound distance are included in stable 0.2.0 and beta.6. Installation and connected schema availability are separate. See Templates and presets.

The general combat chain is Attack child → health phase → base settings. Children can override movement speed, knockback resistance, follow range, melee, Sonic Boom, and targeting. Health, scale, Darkness, glow, boss-bar identity, and phase-transition effects remain health-phase concerns.

Missing health/potion support sections in older files stay disabled. Missing loot stays disabled. Opening and saving an old file doesn't necessarily enable new features.

Fresh default templates have the Beacon effects master switch off, with individual level-I effect entries enabled. The six player-count presets have the master switch on with only Regeneration I enabled. Both enable the 100 HP fight-health floor, first-entry healing, and the default reusable potion.

Ticks use game time. At normal server speed, 20 ticks is one second. Seconds-based audio limits and file byte limits are listed on Sounds and music.

The target time gate can postpone forced rotation beyond max_attacks. Minimum native melee scheduling can also prevent a small configured cooldown from producing equally fast attacks. A value can be within the allowed range without making attacks happen at exactly that interval.

• Template identifiers: lowercase ASCII letters, digits, dots, underscores, or hyphens; no spaces.
• Media references: single lowercase filenames, no directory paths.
• Custom skin: PNG, exactly 128×128, at most 512 KiB.
• Event/voice sound: OGG Vorbis, at most 1 MiB minus 1 KiB and 30 seconds.
• Music: OGG Vorbis, at most 8 MiB minus 1 KiB and 10 minutes.
• Voice discovery: up to 64 valid files in the direct voice-lines/ folder.

Use regular files inside the template's own folder. Linked template/media parents and linked files are rejected.

Stable 0.2.0 and beta.6 resolve a subphase's type through the registered action catalog. An addon introduces the mechanic; the template selects its ID and supplies its declared action_settings values. See API reference and Lightning addon walkthrough.

Settings support numbers, booleans and bounded text/options. For registered actions, action_settings is optional: leave it out or use {} for the declared defaults. If present, it must be an object, not null, an array or a scalar. Within that object, missing or null declared scalar fields use their defaults. Native combat inheritance stays separate; a custom action does not inherit another action's settings.

Unknown setting keys survive saves but are not exposed as arbitrary controls or execution settings. Missing action IDs fail validation. Client catalog metadata is virtual and is not written into templates. Switching Type replaces action_settings with the new mechanic's defaults.

Existing legacy attack and recovery types keep their original root-level attacks_before_next and duration_ticks fields. For namespaced core IDs, those values belong inside action_settings. Generated comments and the editor show each registered field's description, default and limits.

Partial example:

{
  "boss_bar": {
    "pvp_protection": { "enabled": true }
  }
}

This boolean is encounter-wide, not a phase/subphase override. Missing/null sections or missing/null enabled mean disabled; new files explicitly use true. The schema exports creation true separately from omitted false. String values such as "true" are rejected by editors; use a JSON boolean. /boss reload applies edits to loaded bosses. It uses boss_bar.visibility_area, not the activation trigger. See Player support.

The later source adds fields under skin.glowing_eyebrows. They are packaged in local checkpoint 0.3.0-beta.6, not deployed. See Skins and face controls for the editor workflow, example and current validation limits.

• expression: angry (default), neutral, curious or sad.
• left_rotation, right_rotation: whole degrees -45–45, default 0; positive clockwise.
• events.enabled: false by default; missing/false preserves the static face.
• events.melee, sonic_boom, roar, hurt, target_change: each holds expression (inherit, a named shape, or random) and nullable left/right rotation overrides. Inherit always means the base shape; null angles use the base angles, not a previous event.
• events.hit_duration_ticks / target_duration_ticks: 1–12000, default 20.
• events.hit_cooldown_ticks / target_cooldown_ticks: 0–12000, default 20.
• events.random_between_attacks: false by default; when enabled, resting expressions roll once after a completed melee swing/sonic beam.
• events.random_pool: angry/neutral/curious/sad booleans, default true; all false uses base.

Hit overrides attack/roar, then new target, then rest. Expiry reuses the ten-tick watcher and may add up to nine game ticks. These fields affect glow appearance only. All seven bundled presets include disabled event defaults; existing omitted settings keep the legacy look. Native fixture/editor/atlas checks passed in beta.6; real multiplayer and deployment remain pending. Hosted beta does not yet declare this jar compatible. See Compatibility and testing.