Composition

There are a few special blocks when calling that command in-game:

1. Air blocks are ignored

2. Barrier blocks are ignored

3. Structure Void blocks are considered Air (Player must leave an air block in their place)

4. GooP JSON Furniture

5. Signs (see signs section)

This makes Barriers and Structure Void blocks impossible to import from the game, and if you truly wish the structure to require them, you will have to manually write them into the YML File and call /goop reload.

YML Format

For reference, this is how the file looks in YML:

- RED_SANDSTONE -1 2 -2

- ANDESITE_STAIRS -1 2 -1||HALF false,FACING BACK

Which comes from

- <MATERIAL> <X> <Y> <Z>||<Blockstates>

Importing with the command VS Writing in the YML File

Importing from the word has the HUGE advantage that it is so fast and easy to use, it will:

• Automatically calculate the X Y Z offsets of the blocks

• Automatically include ALL supported blockstates of the blocks

• Write the blocks in correct sintax

Why would anyone want to write into the YML file then? For the following reasons:

• Allow to make BARRIER and STRUCTURE_VOID blocks required parts of the structure

• If a blockstate is not specified, it is just not checked — ex. a slab block would not matter if it is on the bottom or top

  • Since importing with the command always imports ALL blockstates, it will only match the exact thing being imported.

  • You may want to allow more build flexibility by deleting some blockstates — not checking if the slab is on top or bottom.

Simple Example

A sign that, when clicked, repairs all the items of in the player's inventory at the cost of $10 (using vault economy)

RepairallSign:

Composition:

- DARK_OAK_WALL_SIGN 0 0 0||SIGN Repair

Triggers:

- INTERACT

VaultCost: 10

Commands:

- 'goop nbt damage %player% * 0 oS: goop tell @s &eAll Items Repaired!'

As long as the sign has the word "repair" in any line, it will be detected by CustomStructures.