Themes, templates and shared definitions

Theme fields: schema-version, id, optional extends, screen-defaults and component-defaults. Template fields: schema-version, id, optional extends, parameters and component. Exact {{parameter}} tokens preserve scalar type; embedded tokens stringify it. Missing/undeclared parameters fail.

Action-file fields: schema-version, id and actions. {ref: action_id} expands a shared list. Language fields: schema-version, locale and entries; player locale is selected with en_US fallback. Entries use trusted administrator formatting.

Maps merge recursively with local values winning; lists replace completely. References use registry IDs, not arbitrary file paths. Inheritance, template expansion, shared-action reference cycles fail. See actions and conditions.

Inherit a reusable frame

Create screens/travel.yml:

schema-version: 1
id: travel
extends: frame
components:
  heading:
    text: '<gold>TRAVEL'

The child keeps the inherited background and X. Only heading.text is replaced. IDs refer to loaded definitions, so frame may live in a nested screen directory without changing extends.

If an inherited value fails validation, the error identifies both the affected screen and the declaration that supplied that value. For example, eyes.yml [screen=curtain, component=-, inherited-from=eyes] $.cinematic.actions.covered[1].type means the second covered action comes from eyes, even though validation failed while loading curtain. Fix that action in eyes.yml, or replace the covered list in the child. A local override is reported against the child’s own file. At startup, only rejected screens are skipped; a failed reload keeps the previous configuration.

Apply a theme

Create themes/server.yml:

schema-version: 1
id: server
component-defaults:
  color: '#E8DFC8'
  shadow: false
screen-defaults:
  session:
    timeout-ticks: 2400

Set theme: server at the screen root. Component-specific colors override the theme. A theme may set extends: other_theme to inherit another theme; parent maps merge before local values.

Reuse a button with parameters

The supplied navigation_button template declares screen, label, x and y. Add this to a screen’s components:

open_settings:
  template: navigation_button
  parameters:
    screen: settings
    label: Settings
    x: 44
    y: 132

To write your own template, create templates/menu_link.yml:

schema-version: 1
id: menu_link
parameters:
  target: home
  label: Home
component:
  type: button
  position: {x: 44, y: 132}
  size: {width: 240, height: 32}
  padding: 8
  layer: 20
  text: '<white>{{label}}'
  asset: {provider: native, kind: image, id: 'craftcanvas:button'}
  actions:
    click: [{type: open, screen: '{{target}}'}]

Use template: menu_link with parameters: {target: catalog, label: Browse}. Parameters are expanded at reload, while {variable} placeholders are resolved during presentation. List overrides replace the inherited list, including an entire click sequence.

Create actions/return_home.yml:

schema-version: 1
id: return_home
actions:
  - {type: sound, id: minecraft:ui.button.click}
  - {type: open, screen: home}

Reference it from any button:

actions:
  click: [{ref: return_home}]

Cycles between parent definitions, template expansion or shared actions reject reload and leave the previous valid configuration active.

Translate labels

Create or edit languages/en_US.yml:

schema-version: 1
locale: en_US
entries:
  menu-title: '<gold>SERVER MENU'
  saved: '<green>Your settings have been saved.'

Use text: '{lang.menu-title}' in a component or message. Add a language file with the corresponding locale and keys for another language. Missing locales fall back to en_US; missing keys display the key.

Themes, templates and shared definitions

Inherit a reusable frame

Apply a theme

Reuse a button with parameters

Share an action list

Translate labels