Skip to content
AbstractMenus AbstractMenus

Item Enhancer

A “fixed-table” enhancement menu: stone becomes coal ore, apple becomes golden apple, wooden sword becomes diamond sword, wooden axe becomes diamond axe. Built around the oneof rule which short-circuits on the first matching condition - the perfect fit for “switch on item type, do different thing”.

What it teaches

Section titled “What it teaches”
  • The oneof rule type and its short-circuit “first match wins” semantics
  • Per-branch actions inside oneof entries (each entry has its own actions {})
  • Drag-and-drop slots and the placedItem rule for input matching
  • Combining drag-and-drop primitives (placeItem, removePlaced, setButton) into a transformation pipeline
  • Templates for reusable rule and action shapes (${inputSlotRule}, ${outputAction})
advanced
Features: draggable-slotsplacedItem-ruleplaceItemremovePlacedsetButtononeof-ruleconditional-transformation
Open: /ame_enhancer 
# Item Enhancer - drag-and-drop with conditional transformation via oneof rule
# Docs: https://abstractmenus.github.io/docs/en/examples/state-and-vars/item-enhancer
# Open: /ame_enhancer
# Requires: -


include required(file("./plugins/AbstractMenus/menus/example/_shared/templates.conf"))


title: "&6Item Enhancer"
size: 1


activators {
  command: "ame_enhancer"
}


# Slots 2 (input) and 6 (result) are draggable. Slot 4 is the trigger button.
draggable: [
  "--x---x--"
]


# Result-slot placeholder shown when the menu opens or the input is invalid.
resultStub {
  slot: 6
  material: WHITE_STAINED_GLASS_PANE
  name: "&7Result"
}


# Reusable bits
inputSlotRule { slot: 2 }
outputAction  { slot: 6, count: "%changed_item_amount%" }


# The transformation table: each entry pairs a "placed input matches X" rule
# with an action that produces output Y. `oneof` short-circuits on the first
# match - so the first matching transformation wins.
enhanceRules {
  oneof: [
    {
      placedItem: ${inputSlotRule} { material: STONE }
      actions { placeItem: ${outputAction} { material: COAL_ORE } }
    }
    {
      placedItem: ${inputSlotRule} { material: APPLE }
      actions { placeItem: ${outputAction} { material: GOLDEN_APPLE } }
    }
    {
      placedItem: ${inputSlotRule} { material: WOODEN_SWORD }
      actions { placeItem: ${outputAction} { material: DIAMOND_SWORD } }
    }
    {
      placedItem: ${inputSlotRule} { material: WOODEN_AXE }
      actions { placeItem: ${outputAction} { material: DIAMOND_AXE } }
    }
  ]
}


items: [
  # Decorative panes around the draggable slots
  {
    slot: [ "xx-x-x-x-" ]
    material: BLACK_STAINED_GLASS_PANE
    name: " "
  }


  # Default result-slot placeholder
  ${resultStub}


  # Recipes info card
  {
    slot: 8
    material: NAME_TAG
    name: "&aRecipes"
    lore: [
      "&fStone &7-> &bCoal Ore"
      "&fApple &7-> &bGolden Apple"
      "&fWooden Sword &7-> &bDiamond Sword"
      "&fWooden Axe &7-> &bDiamond Axe"
    ]
  }


  # The "Enhance!" button
  {
    slot: 4
    material: NETHER_STAR
    name: "&bEnhance!"
    click {
      rules: ${enhanceRules}
      actions {
        removePlaced: 2
        sound: ${successSound}
      }
      denyActions {
        rules {
          placedItem { slot: 6, material: AIR }
        }
        actions {
          setButton: ${resultStub}
          sound: ${deniedSound}
        }
      }
    }
  }
]
↓ menu.conf

Bundle includes _shared/templates.conf and INSTALL.txt.

Why state-and-vars?

Section titled “Why state-and-vars?”

This example is filed under state-and-vars because the drag-and-drop machinery is itself a form of menu state - the items physically held in slots 2 and 6 are session-local “variables” of the menu. It doesn’t use setVar/setVarp, but the conceptual pattern (read the slot’s state, branch on it, mutate it) is the same.

How oneof works

Section titled “How oneof works”

oneof is a logical rule wrapper that takes a list of entries. It walks the list top-to-bottom and stops on the first whose own rule matches. The matching entry’s actions {} block is then run.

oneof: [
  { placedItem: { slot: 2, material: STONE }, actions { placeItem: { ..., material: COAL_ORE } } }
  { placedItem: { slot: 2, material: APPLE }, actions { placeItem: { ..., material: GOLDEN_APPLE } } }
  ...
]

If none of the entries match, the entire oneof evaluates false. The outer click block then runs denyActions instead of the success path.

This is cleaner than nested if/and/or for switch-like logic.

Adding a new recipe

Section titled “Adding a new recipe”

Append to the oneof list in enhanceRules:

{ placedItem: ${inputSlotRule} { material: COAL }
  actions { placeItem: ${outputAction} { material: DIAMOND } } }

The ${inputSlotRule} and ${outputAction} substitutions keep the slot numbers in one place - if you reorganize the menu layout, only the two anchor blocks change, not every recipe entry.

Try it

Section titled “Try it”

After installing the example pack:

  1. Drop the bundle into plugins/AbstractMenus/menus/example/.
  2. /am reload.
  3. Type /ame_enhancer in-game.
  4. Drag a stone block into the left slot.
  5. Click “Enhance!”. A coal ore appears in the right slot.