Complete JSON Field Reference

This page consolidates fields from the previous wiki and fields verified against the 1.20.1 source.

Controllers

Path:

config/mm/controllers/<file>.json

Example:

{
  "type": "mm:machine",
  "id": "coke_oven",
  "name": "Coke Oven",
  "parallelProcessingDefault": false,
  "maxParallelRecipes": -1,
  "recipeSelectionMode": "default"
}

Controller recipe selection modes

recipeSelectionMode changes which runnable recipe a formed controller prefers to start. It does not change recipe validity, inputs, outputs, timings, or parallel-processing caps.

round_robin_input_item is intended for sieve/washer/recycler-style machines where several input items share one input port and should be processed fairly.

Ports

Path:

config/mm/ports/<file>.json

Every port JSON is expanded into input and output variants.

Common fields:

{
  "id": "item_port",
  "controllerIds": ["mm:coke_oven"],
  "name": "Item Port",
  "type": "mm:item",
  "config": {}
}

Port config fields

Item NBT matching

Item ingredients support two ways to specify NBT:

{
  "type": "mm:item",
  "item": "minecraft:potion",
  "count": 1,
  "nbt": { "Potion": "minecraft:water" },
  "nbt_match": "weak"
}

or:

{
  "type": "mm:item",
  "item": "minecraft:potion",
  "count": 1,
  "nbt_snbt": "{Potion:\"minecraft:water\"}",
  "nbt_match": "strong"
}

weak/default matching treats the provided NBT as a subset. strong requires a stricter match.

Extra blocks

Path:

config/mm/extras/<file>.json

Example:

{
  "id": "basic_circuit",
  "name": "Basic Circuit",
  "type": "mm:circuit"
}

Supported types:

• mm:circuit
• mm:gearbox
• mm:vent

Structures

Path:

data/<namespace>/mm/structures/<path>.json

Example:

{
  "name": "Coke Oven",
  "controllerIds": "mm:coke_oven",
  "portsAnywhere": false,
  "maxParallelRecipes": -1,
  "layout": [
    ["AAA", "ACA", "AAA"]
  ],
  "key": {
    "A": { "block": "minecraft:bricks" },
    "C": { "block": "mm:coke_oven" }
  }
}

Structure key piece types

A key entry is identified by the field it contains:

"A": { "block": "minecraft:bricks" }

For exact port matching, use the base port id plus the input flag:

"I": { "port": "mm:item_port", "input": true }
"O": { "port": "mm:item_port", "input": false }

Do not use port: "mm:item_port_input" as the normal structure form. Generated block ids include _input and _output, but the structure port requirement is intended to reference the base port id.

Port type matching with tiers

Example:

"I": {
  "portType": "mm:item",
  "input": true,
  "minTier": 2,
  "maxTier": 4
}

This matches any input item port whose storage config tierRank is between 2 and 4. If a port config has no meaningful tier, it behaves like tier 1 for matching.

KubeJS generated-id rules

For startup-generated config-backed content, event.create(...) takes a bare MM base id/path, not a namespaced id:

MMEvents.registerControllers(event => {
  event.create('coke_oven')
    .type('mm:machine')
    .name('Coke Oven')
})

MMEvents.registerExtraBlocks(event => {
  event.create('basic_circuit')
    .type('mm:circuit')
    .name('Basic Circuit')
})

MMEvents.registerPorts(event => {
  event.create('item_port')
    .name('Item Port')
    .controllerId('mm:coke_oven')
    .config('mm:item', c => {
      c.rows(1).columns(3).slotCapacity(64).tierRank(1)
    })
})

Wrong:

event.create('mm:coke_oven')
event.create('mm:basic_circuit')
event.create('mm:item_port')

Structures and process recipes are different: those are datapack/resource ids and should be namespaced:

MMEvents.createStructures(event => {
  event.create('expert:coke_oven')
    .controllerId('mm:coke_oven')
})

MMEvents.createProcesses(event => {
  event.create('expert:coke_oven/charcoal')
    .structureId('expert:coke_oven')
})

Process recipes

Path:

data/<namespace>/mm/processes/<path>.json

Example:

{
  "structureId": "mypack:coke_oven",
  "ticks": 200,
  "parallelProcessing": false,
  "inputs": [
    {
      "type": "mm:input/consume",
      "ingredient": {
        "type": "mm:item",
        "item": "minecraft:oak_log",
        "count": 1
      }
    }
  ],
  "outputs": [
    {
      "type": "mm:output/simple",
      "ingredient": {
        "type": "mm:item",
        "item": "minecraft:charcoal",
        "count": 1
      }
    }
  ],
  "conditions": []
}

Input entries

{
  "type": "mm:input/consume",
  "ingredient": { "type": "mm:item", "item": "minecraft:iron_ingot", "count": 1 },
  "chance": 1.0,
  "per_tick": false
}

Output entries

{
  "type": "mm:output/simple",
  "ingredient": { "type": "mm:energy", "amount": 1000 },
  "chance": 1.0,
  "per_tick": false
}

Output entries use the same optional chance and per_tick fields. For item outputs, the source also accepts shorthand fields such as item, count, and NBT fields directly on the output entry, but the full ingredient object is clearer and recommended.

Conditions

Supported condition types:

{ "type": "mm:dimension", "dimension": "minecraft:the_nether" }

{ "type": "mm:weather", "weather": "clear" }

Weather values are parsed as enum names. Use lowercase or uppercase variants equivalent to the enum names: clear, rain, or thunder.