Breadcrumb Chain

Three menus chained together with openMenu, each level having a back button to the previous one. Demonstrates how to build menu trees several levels deep without anything fancier than the basic openMenu action.

intermediate

Features: multi-menu-fileopenMenu-chainmanual-back-navigation

Open: /ame_chain Copy

menu.conf

# Breadcrumb Chain - 3 nested menus using openMenuCtx for dynamic back navigation
# Docs: https://abstractmenus.github.io/docs/en/examples/hub-and-nav/breadcrumb-chain
# Open: /ame_chain
# Requires: -

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

menus {

  # Level 1
  ame_chain_l1 {
    title: "&6Level 1"
    size: 1
    activators { command: "ame_chain" }
    items: [
      {
        slot: 4
        material: BLUE_WOOL
        name: "&aGo deeper"
        lore: ["&7Open Level 2."]
        click { openMenu: "ame_chain_l2" }
      }
      ${buttonClose} { slot: 8 }
    ]
  }

  # Level 2
  ame_chain_l2 {
    title: "&6Level 2"
    size: 1
    items: [
      {
        slot: 4
        material: GREEN_WOOL
        name: "&aGo deeper"
        lore: ["&7Open Level 3."]
        click { openMenu: "ame_chain_l3" }
      }
      {
        slot: 0
        material: ARROW
        name: "&eBack to Level 1"
        click { openMenu: "ame_chain_l1" }
      }
    ]
  }

  # Level 3
  ame_chain_l3 {
    title: "&6Level 3 (deepest)"
    size: 1
    items: [
      {
        slot: 4
        material: GOLD_BLOCK
        name: "&6You reached the bottom"
        lore: [
          "&7There's no Level 4."
          "&7Use the back arrow to climb out."
        ]
      }
      {
        slot: 0
        material: ARROW
        name: "&eBack to Level 2"
        click { openMenu: "ame_chain_l2" }
      }
    ]
  }

}

_shared/templates.conf

# AbstractMenus example pack - shared templates
# Reusable HOCON snippets referenced from menus via ${blockName} substitution.
# Docs: https://abstractmenus.github.io/docs/en/examples

# Sound presets (Paper 1.21+ registry keys)
clickSound:    "ui.button.click"
openSound:     "block.chest.open"
closeSound:    "block.chest.close"
successSound:  "entity.experience_orb.pickup"
failSound:     "block.note_block.bass"
deniedSound:   "block.anvil.land"

# Deny action snippets (use as: denyActions: ${denyNoMoney})
denyNoMoney {
  sound:   ${deniedSound}
  message: "&cYou don't have enough money."
}
denyNoPerm {
  sound:   ${deniedSound}
  message: "&cYou don't have permission."
}
denyCooldown {
  sound:   ${deniedSound}
  message: "&cYou're on cooldown. Try again later."
}

# Border items (use as: ${borderBlack} { slot: "0-8" })
borderBlack {
  material: BLACK_STAINED_GLASS_PANE
  name: " "
}
borderGray {
  material: GRAY_STAINED_GLASS_PANE
  name: " "
}
borderBlue {
  material: BLUE_STAINED_GLASS_PANE
  name: " "
}

# Navigation buttons (use as: ${buttonClose} { slot: 22 })
buttonClose {
  material: BARRIER
  name: "&cClose"
  click {
    closeMenu: true
  }
}
buttonBack {
  material: ARROW
  name: "&eBack"
  lore: ["&7Return to previous menu"]
  click {
    closeMenu: true
  }
}
buttonNext {
  material: ARROW
  name: "&eNext page"
  click {
    pageNext: 1
  }
}
buttonPrev {
  material: ARROW
  name: "&ePrevious page"
  click {
    pagePrev: 1
  }
}

# Rule shortcut snippets (use as: rules: ${rulesAdmin})
rulesAdmin   { permission: "abstractmenus.admin" }
rulesVip     { permission: "abstractmenus.vip" }
rulesDonator { permission: "abstractmenus.donator" }

# Common decorative header (use as: ${commonHeader} { slot: 4 })
commonHeader {
  material: NETHER_STAR
  name: "&6&lExample Menu"
  lore: ["&7Welcome to the AbstractMenus example pack"]
}

↓ menu.conf ↓ Bundle (.zip)

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

What it teaches

• Building deeper menu trees with manual openMenu chains
• Per-level back buttons hard-coded to the parent

Manual vs context-aware back

Each level’s back button hard-codes the parent menu name:

{ slot: 0, name: "&eBack to Level 2", click { openMenu: "ame_chain_l2" } }

Simple, predictable, works for tree structures where every menu has exactly one parent. Trade-off: if ame_chain_l2 is opened from multiple parents (say, both Level 1 AND a sub-hub), the back button always returns to Level 1, ignoring where the player actually came from.

For DAG-shaped menu graphs where a menu can be reached from multiple places and back should respect the actual arrival path, use openMenuCtx instead. It propagates context through the menu chain. See the activator/menu input docs for openMenuCtx mechanics.

For 95% of menus a simple tree is fine - hard-coded back buttons keep things predictable.

Try it

1. Drop the bundle into plugins/AbstractMenus/menus/example/.
2. /am reload.
3. Type /ame_chain in-game.
4. Click “Go deeper” twice. Click back twice.