FAQ

A FAQ is essentially a navigation tree: question list at the root, one sub-menu per answer. This example uses a menus { ... } multi-menu file to keep all four screens in one config, with openMenu calls to wire them together. The ${buttonBack} shared button gets a per-page override to point back at the FAQ index.

intermediate

Features: multi-menu-fileopenMenu-navigationback-button-patternmenu-tree

Open: /ame_faq Copy

menu.conf

# FAQ - hub menu of questions, click each to open the answer in a sub-menu
# Docs: https://abstractmenus.github.io/docs/en/examples/info-pages/faq
# Open: /ame_faq
# Requires: -

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

menus {

  # Main FAQ index - list of questions
  ame_faq {
    title: "&6Frequently Asked Questions"
    size: 3

    activators {
      command: "ame_faq"
    }

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

      {
        slot: 4
        material: WRITTEN_BOOK
        name: "&6&lFAQ"
        lore: ["&7Click any question for the answer."]
      }

      {
        slot: 10
        material: PAPER
        name: "&aHow do I claim land?"
        click { openMenu: "ame_faq_a1" }
      }
      {
        slot: 12
        material: PAPER
        name: "&aWhat does VIP rank give me?"
        click { openMenu: "ame_faq_a2" }
      }
      {
        slot: 14
        material: PAPER
        name: "&aHow do I report a player?"
        click { openMenu: "ame_faq_a3" }
      }
      {
        slot: 16
        material: PAPER
        name: "&aWhere are server rules?"
        click { openMenu: "ame_rules" }
      }

      ${buttonClose} { slot: 22 }
    ]
  }

  # Answer 1 - Land claiming
  ame_faq_a1 {
    title: "&6FAQ - Land claiming"
    size: 3
    items: [
      ${borderBlack} { slot: "0-8" }
      ${borderBlack} { slot: "18-26" }
      {
        slot: 13
        material: GRASS_BLOCK
        name: "&aHow do I claim land?"
        lore: [
          "&7Use a golden shovel to mark"
          "&7the corners of your claim."
          ""
          "&7- Right-click first corner"
          "&7- Right-click opposite corner"
          ""
          "&7Each block costs 1 claim block."
          "&7Earn more by playing or buying"
          "&7with /buyclaimblocks."
        ]
      }
      ${buttonBack} { slot: 18, click { openMenu: "ame_faq" } }
    ]
  }

  # Answer 2 - VIP perks
  ame_faq_a2 {
    title: "&6FAQ - VIP perks"
    size: 3
    items: [
      ${borderBlack} { slot: "0-8" }
      ${borderBlack} { slot: "18-26" }
      {
        slot: 13
        material: GOLDEN_HELMET
        name: "&6What does VIP give me?"
        lore: [
          "&7VIP includes:"
          ""
          "&7- &fcolored chat name"
          "&7- &f5 home points (vs 1 default)"
          "&7- &fdaily VIP kit"
          "&7- &f50% shop discount"
          "&7- &fparticle effect on join"
          ""
          "&7Get VIP at &e/ame_donate&7."
        ]
      }
      ${buttonBack} { slot: 18, click { openMenu: "ame_faq" } }
    ]
  }

  # Answer 3 - Reporting players
  ame_faq_a3 {
    title: "&6FAQ - Reporting"
    size: 3
    items: [
      ${borderBlack} { slot: "0-8" }
      ${borderBlack} { slot: "18-26" }
      {
        slot: 13
        material: BARRIER
        name: "&cReporting players"
        lore: [
          "&7Use &e/report <name> <reason>&7"
          "&7or post in our Discord at"
          "&7&fhttps://discord.gg/example"
          ""
          "&7Include screenshots if possible."
          "&7Staff respond within a few hours."
        ]
      }
      ${buttonBack} { slot: 18, click { openMenu: "ame_faq" } }
    ]
  }

}

_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

• Using menus { ... } to declare a hub + multiple answer screens in one file
• Overriding shared template fields per use - ${buttonBack} { slot: 18, click { openMenu: "..." } }
• The “answer page” pattern: large lore item + back button, no other interactivity
• One question pointing to a different existing menu (the rules question opens the Server Rules menu)

Why multi-menu files for FAQs

A 10-question FAQ as 10 separate files is messy - 10 file paths, 10 include lines if shared templates. Bundling them in one menus { ... } block keeps related screens together and makes editing the FAQ a one-file operation.

The naming convention matters: each menu gets a unique server-wide name. Pick ame_faq, ame_faq_a1, ame_faq_a2 etc. so they don’t collide with other example menus or the user’s own configs.

Overriding ${buttonBack}

The shared buttonBack template defines an arrow item with closeMenu: true. For the FAQ, we want it to navigate back to the index instead. Override the click block per use:

${buttonBack} { slot: 18, click { openMenu: "ame_faq" } }

The ${buttonBack} brings in the material, name, lore. The override replaces the click block. Same pattern for any shared template you need to specialize per-callsite.

Adding a question

Two edits per new question:

1. In ame_faq items list, add a paper tile pointing at the new answer menu name.
2. Add a new ame_faq_aN block at the bottom of the menus { ... } wrapper with the answer content.

Try it

1. Drop the bundle into plugins/AbstractMenus/menus/example/.
2. /am reload.
3. Type /ame_faq in-game.
4. Click any question. Read the answer. Click the back arrow to return.