TESSERA

content 02

Blocks

Every .yml file in blocks/ is loaded. Each top-level key is one block id.

A custom block is a vanilla block plus an id. When a player places an item whose stored Tessera id matches a block id, the id is written into the chunk's PersistentDataContainer at that position, and into the block's own container when the block is a tile entity. Breaking it runs your drop table instead of the vanilla one.

Keys

KeyTypeDefaultNotes
block_materialmaterial nameNOTE_BLOCKmaterial is accepted as a second spelling. Unknown names fall back to NOTE_BLOCK.
display_nameMiniMessagethe idName of the item form.
hardnessnumber1.0Break time, as for vanilla blocks. A negative value makes the block unbreakable outside creative.
required_toolstringANYANY and NONE disable the tool check.
minimum_tierstringNONETier the tool has to reach.
sounds.placesound nameunsetAlso accepted as place_sound.
sounds.breaksound nameunsetAlso accepted as break_sound.
sounds.stepsound nameunsetAlso accepted as step_sound.
sounds.hitsound nameunsetAlso accepted as hit_sound.
light_levelinteger01 to 15. A light block is put into the air above the block and removed with it.
cancel_dropbooleanfalseBreak with no drops at all.
custom_model_datainteger0Parsed and stored. The item form is built from the matching custom item when there is one.
modelmodel idunsetBlock model shown in the world and for the block's item, such as shop:block/marble. Note blocks only.
dropslist or sectionthe block itselfSee below.

Models

A note block with a model is drawn with that model. Every such block gets a note block state of its own (an instrument, a note and powered=true), and the pack's blockstates/note_block.json maps that state to the model. Every other state keeps the vanilla note block.

marble:
  block_material: NOTE_BLOCK
  display_name: "Marble"
  model: shop:block/marble     # assets/shop/models/block/marble.json

The states are stored in plugins/Tessera/.block-states.yml and never change, so blocks already placed keep their look when you add new ones. Do not edit that file. There are 575 states to hand out.

A custom note block ignores the block below it and redstone, which would otherwise change its state and so its look. The block's item uses the item model tessera:block/<id>, so it shows the same model in the inventory.

A vanilla note block that is powered by redstone can land on a state a custom block uses and look like it until the power goes off.

Drop tables

drops takes either a list or a section. Each entry has item, min, max and chance.

# plugins/Tessera/blocks/ruby_block.yml
ruby_block:
  block_material: NOTE_BLOCK
  display_name: "<gradient:#ff416c:#ff4b2b><bold>Ruby Block</bold></gradient>"
  hardness: 5.0
  required_tool: PICKAXE
  minimum_tier: IRON
  sounds:
    place: BLOCK_STONE_PLACE
    break: BLOCK_STONE_BREAK
    step: BLOCK_STONE_STEP
    hit: BLOCK_STONE_HIT
  drops:
    - item: ruby
      min: 9
      max: 9
      chance: 1.0

Defaults per entry: min is 1, max is min, chance is 1.0. A plain string entry is treated as one guaranteed drop of that id. When drops is absent and cancel_drop is false, the block drops itself once.

Drop ids are resolved as a vanilla material first and as a custom item second. Do not name a custom item after a vanilla material if you want the custom one to drop.

Tool gate: when required_tool is neither ANY nor NONE and the tool does not match, the block drops nothing.

required_tool understands PICKAXE, AXE, SHOVEL, HOE, SWORD and SHEARS. Any other value is matched as a substring of the material name. minimum_tier understands NONE, WOOD or WOODEN, GOLD or GOLDEN (both rank 1), STONE, IRON, DIAMOND and NETHERITE.

Break speed

Digging a custom block takes as long as a vanilla block with the same hardness: 1.5 seconds per point with the right tool, 5 without. While a player digs, Tessera scales their block break speed attribute by the difference to the base block, so efficiency, haste and other modifiers still count. With required_tool, the matching tool gets its tier's speed (wood 2, stone 4, iron 6, diamond 8, netherite 9, gold 12) and anything else breaks at the slow rate.

Behaviour in the world

  • Pistons cannot move custom blocks. Extend and retract events that touch one are cancelled.
  • Block and entity explosions remove the stored id and run the drop table.
  • Note blocks used as bases do not play their note when clicked, and neighbour updates do not change them.
  • The place and break sounds from the config are played on the matching events.

Storage

The id lives in the chunk container under a key derived from the block position, so it survives restarts and chunk unloads. Removing a block through /tessera block remove clears that entry.

/tessera block info      # what you are looking at
/tessera block remove    # tessera.admin

Not configurable

blast_resistance, fortune multipliers, requires_tool, tool_tier and the sound_group spelling appear only in config comments. The parser does not read them.