● Citadel Docs

Player store

Sell perks to your players and have them applied in-game automatically. Your store lives at /store on your community address.

Before you start

  1. Subscribe to the Game Server / Store add-on (or start a trial).
  2. Connect your Stripe so player payments pay out to you.
  3. Connect your game server so perks can be granted in-game.

Want a head start? Setup templates create a full perk catalog with sensible command conventions in one click.

Create a perk

On the Store page, click New product and set:

  • Name, description, price — the player-facing price you set (it's your revenue). Add an optional image and a badge ("Best Seller", "New") for the storefront card.
  • Billing — one-time or a recurring subscription (monthly / yearly). Recurring perks are revoked automatically when the subscription ends, and players can cancel their own renewals from their account page.
  • Pricing tiers — optionally sell one perk at several durations (7 / 30 / 90 days, each its own price). Tiered perks expire automatically when the bought duration runs out and show as "From $X" on the storefront.
  • In-game grant — the game server (relay) to target, plus the unlock and optional lock commands (see below).
  • Purchase questions — fields the player fills at checkout (e.g. their Steam64), which feed the grant.

In-game grant mapping

Each perk maps to a relay command with a payload. Use placeholders that Citadel resolves at purchase time:

| Placeholder | Resolves to | |---|---| | {{user.steam64}} | the buyer's Steam64 (or the recipient's, for gifts) | | {{form.answers.N}} | the answer to the Nth purchase question | | {{org.slug}} | your community slug |

Example unlock command for a "Priority Queue (30 days)" perk:

{
  "commandType": "AddPriorityQueue",
  "payload": { "steam64": "{{user.steam64}}", "days": 30, "comment": "VIP perk" }
}

and its lock (expiry) command:

{ "commandType": "RemovePriorityQueue", "payload": { "steam64": "{{user.steam64}}" } }

The available command types depend on your integration — see CFTools and LB Core (LBmaster). Citadel checks commands against what your server actually declared, so a typo is caught when you save the perk — not after someone has paid.

Gifting

Players can buy any perk as a gift: they enter the recipient's Steam64 at checkout and the grant targets the recipient instead of the buyer.

Beyond the catalog

Gift cards, store credit, loyalty tiers, and Discord role rewards are covered in Gift cards, loyalty & Discord rewards. Revenue, buyers, and best-sellers live on Insights.

What happens on purchase

A player buys → Citadel charges them (funds to your Stripe, a 5% platform fee) → resolves the placeholders → sends the unlock command to your server → the perk applies. On a recurring perk's expiry — or a refund — the lock command revokes it.

If your server is offline at purchase time, the grant waits in a durable queue and delivers when it reconnects. If delivery is configured but can't complete, the order is marked honestly in your dashboard (never silently "delivered") and Citadel retries on a cycle; staff can also re-push or revoke any order from the Players page.