Rank-Gated Shop

Many real shops show different prices for different ranks - VIPs get a discount, donors see exclusive items, etc. The implementation uses two items at the same slot: the first carries a permission rule, the second is the fallback.

intermediate

Features: dual-item-displaypermission-rulemoney-rulediscount-tierclick-handler-template

Requires: VaultLuckPerms

Open: /ame_rank_shop Copy

menu.conf

# Rank-Gated Shop - dual-item HAS/NO_PERM display pattern
# Docs: https://abstractmenus.github.io/docs/en/examples/shops/rank-gated-shop
# Open: /ame_rank_shop
# Requires: Vault, LuckPerms (or any permissions provider)

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

title: "&6Rank Shop"
size: 3

activators {
  command: "ame_rank_shop"
}

# Reusable click handler for the VIP-discount line - takes the discounted price.
discountClick {
  rules { money: 50 }
  actions {
    takeMoney: 50
    itemAdd { material: GOLDEN_APPLE }
    sound: ${successSound}
    message: "&aPurchased with VIP discount."
  }
  denyActions: ${denyNoMoney}
}

# Reusable click handler for the regular price.
regularClick {
  rules { money: 100 }
  actions {
    takeMoney: 100
    itemAdd { material: GOLDEN_APPLE }
    sound: ${successSound}
    message: "&aPurchased at regular price."
  }
  denyActions: ${denyNoMoney}
}

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

  # ========== Golden Apple - dual variants by VIP permission ==========

  # VIP variant: discounted, shown only to VIP players.
  {
    slot: 13
    material: GOLDEN_APPLE
    name: "&6Golden Apple &8(&aVIP price&8)"
    lore: [
      "&7Premium fruit."
      ""
      "&ePrice: &a$50 &m$100"
      "&8(VIP 50% discount)"
      ""
      "&aClick to buy"
    ]
    rules { permission: "abstractmenus.vip" }
    click: ${discountClick}
  }

  # Regular variant: full price, shown to everyone else (no rules = always visible,
  # but shadowed by the VIP variant when VIP rule passes).
  {
    slot: 13
    material: GOLDEN_APPLE
    name: "&6Golden Apple"
    lore: [
      "&7Premium fruit."
      ""
      "&ePrice: &a$100"
      ""
      "&aClick to buy"
      "&8VIP rank gives 50% off."
    ]
    click: ${regularClick}
  }

  ${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 dual-item display pattern with a permission rule
• Per-rank pricing without if rule complexity
• Reusable click handlers via ${discountClick} / ${regularClick} substitution
• How rule short-circuiting and slot ordering interact

How dual-item works

Two items declared at the same slot:

# Variant A: shown only to VIPs
{ slot: 13, name: "Golden Apple (VIP price)", rules { permission: "...vip" }, click: ${discountClick} }

# Variant B: fallback for everyone else
{ slot: 13, name: "Golden Apple",                                               click: ${regularClick} }

When the menu renders, the plugin walks the items list. For slot 13 it finds variant A, checks its rules, and either:

• Uses A if the rule passes (VIP sees the discounted version)
• Skips A and looks for the next definition at slot 13. Finds B. B has no rules. B renders.

This is THE production pattern from real-world shops. It scales to many ranks (4-tier donate stores, etc.) by having one variant per rank, in priority order, with the highest-tier rule first.

Why this beats if for rank checks

The if rule could express the same logic, but with two extra problems:

1. The displayed item itself wouldn’t change - just the click action. Visual differentiation requires dual items anyway.
2. if is parsed as an expression on every render. Permission-based dual items are cheaper.

Use if when comparing numeric/string values that can’t be expressed as a built-in rule (level math, custom var values). Use dual-item permission for “this player is in tier X”.

Customizing for more tiers

Add more variants in priority order. Mythic > Donor > VIP > regular:

{ slot: 13, ..., rules { permission: "myplugin.mythic" }, click: ${mythicClick} }
{ slot: 13, ..., rules { permission: "myplugin.donor"  }, click: ${donorClick}  }
{ slot: 13, ..., rules { permission: "myplugin.vip"    }, click: ${vipClick}    }
{ slot: 13, ..., click: ${regularClick} }   # fallback - no rules

Order matters: highest-priority tier first. The first matching variant wins.