Sub-Hub

When the main hub gets crowded, split overflow features onto a secondary hub. This example follows the most common pattern: same layout as the main hub, but with a back button pointing at the parent.

beginner

Features: openMenuback-button-patternsecondary-hub

Open: /ame_subhub Copy

menu.conf

# Sub-Hub - secondary hub with a back button to the main hub
# Docs: https://abstractmenus.github.io/docs/en/examples/hub-and-nav/sub-hub
# Open: /ame_subhub  OR  click the "Other" tile in the main hub
# Requires: -

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

title: "&6Other Features"
size: 3

activators {
  command: "ame_subhub"
}

items: [
  ${borderBlack} { slot: "0-8" }
  ${borderBlack} { slot: "18-26" }

  # Header
  {
    slot: 4
    material: NETHER_STAR
    name: "&6&lOther Features"
    lore: ["&7Things that didn't fit on the main hub."]
  }

  # Tag chooser
  {
    slot: 11
    material: PAPER
    name: "&aTags"
    lore: ["&7Pick a chat tag.", "", "&8Opens /ame_tags"]
    click { openMenu: "ame_tags" }
  }

  # Roulette
  {
    slot: 13
    material: NETHER_STAR
    name: "&aRoulette"
    lore: ["&7Try your luck.", "", "&8Opens /ame_roulette"]
    click { openMenu: "ame_roulette" }
  }

  # Vote
  {
    slot: 15
    material: BEACON
    name: "&aDaily vote"
    lore: ["&7Vote and earn rewards.", "", "&8Opens /ame_vote"]
    click { openMenu: "ame_vote" }
  }

  # Back to main hub
  {
    slot: 18
    material: ARROW
    name: "&eBack to Main Hub"
    lore: ["&7Return to /ame_hub."]
    click { openMenu: "ame_hub" }
  }

  ${buttonClose} { slot: 22 }
]

_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

• The back-button pattern via openMenu to the parent’s name
• Distinguishing “back” (just go up the tree) from “close” (exit the menu UI)
• Allowing the sub-hub to be opened directly via its own command in addition to chained navigation

Two ways to “go back”

Approach 1 (used here): hard-code the parent name.

{
  slot: 18
  material: ARROW
  name: "&eBack to Main Hub"
  click { openMenu: "ame_hub" }
}

Cheap, simple, works. Limitation: if multiple menus chain into this sub-hub, the back button always lands on ame_hub, even if the player came from somewhere else.

Approach 2 (see Breadcrumb Chain): use openMenuCtx and let the activator context propagate the “previous menu” through the chain. The back button then dynamically returns to wherever the player came from.

For 95% of menus, hard-coding parent is fine. Reserve openMenuCtx for genuinely deep menu trees.

Try it

1. Drop the bundle into plugins/AbstractMenus/menus/example/.
2. /am reload.
3. Type /ame_hub to start at the main hub, or /ame_subhub to land here directly.
4. Click any tile to open its target menu.
5. Click “Back to Main Hub” to return.