GitLab

Crucible allows people to create "custom blocks" using the extra block states from mushroom blocks, note blocks, tripwires or chorus plants.

Items that are configured to be blocks will have their corresponding block placed in the world where the player is looking when right-clicked, and will drop the original item when broken by default (unless configured otherwise).

Custom Block Options

All options are placed under a CustomBlock section on an item.

MUSHROOM_BLOCK and NOTE_BLOCK are considered as "solid" blocks, these blocks need a path to the texture to generate itself, other blocks (TRIPWIRE and CHORUS) are non solid this means you can omit the Texture field and Crucible will use the model assigned to the item

Base Options

• Type - The type of custom block, defaults to mushroom (MUSHROOM_BLOCK, NOTE_BLOCK, TRIPWIRE, CHORUS)
• Id - The ID of the custom block.
• Texture - The path of the texture the block will use, or none if block is non solid

  CustomBlock:
    Type: MUSHROOM_BLOCK
    Id: 18
    Texture: block/stars1

Putting in Resource Pack

Please refer to the Resourcepack Generator wiki page for info.

Example

TestBlock:
  Id: STONE
  Model: 5
  Display: 'Probably a Block'
  Type: BLOCK
  CustomBlock:
    Type: MUSHROOM_BLOCK
    Id: 30
    Texture: block/exampletexture
  CustomBlockSkills:
  - sound{s=block.amethyst_block.place} @self ~onBlockPlace
  - sound{s=block.amethyst_block.break} @self ~onBlockBreak

This tripwire block will use the model generated from the item's Generation field

TestTripwire:
  Id: PAPER
  Model: 5
  Display: 'Tripwire plant'
  Generation:
    Model: block/tripwire_plant
  Type: BLOCK
  CustomBlock:
    Type: TRIPWIRE
    Id: 0

WorldEdit Support

You can place custom blocks using worldedit via the following syntax:

//set mythic:ItemName

If you have a custom namespace replace mythic by your namespace:

//set mynamespace:ItemName