Block Lifecycle

Custom blocks exist as barrier blocks in the world with two distinct phases.

Phases

Phase	When	Callbacks
Placed	Barrier block exists in world	onPlaced, onPlacedClick, onPlacedInteract, onPlacedBreak
Active	After ignition / fuse	onPlace, onTick, onTrigger

Surface click routing is declared in YAML behavior. Override onPlacedClick only for custom logic beyond standard actions.

Config sections

Section	Purpose
display	Title and description
block	Placeable/breakable flags, base material, breaking tuning
textures	Asset paths (top, side, bottom)
behavior	Surface clicks — left/right block and air actions
custom_data	Extension-specific tuning (fuse, power, radius, etc.)

Block behavior

behavior:
  combustible: true
  left_click_block: break
  right_click_block: ignite
  left_click_air: none
  right_click_air: none
  ignition_materials:
    - FLINT_AND_STEEL
    - FIRE_CHARGE
  sounds:
    place: BLOCK_BEACON_ACTIVATE
    ignite: ITEM_FLINTANDSTEEL_USE

Action token	Effect
none	No action
break	Break the placed block
ignite	Start fuse / active phase
open	Open extension GUI
handled	Strategy handles the click

Persistence

Placed blocks are indexed in placed-blocks.json — see Storage.

Related

• Extensions — manifest and deploy
• Strategies — AbstractIgnisBlockStrategy
• Extension Cookbook — explosion config recipes