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.

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).
  • Billing — one-time or a recurring subscription (monthly / yearly). Recurring perks are revoked automatically when the subscription ends.
  • 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 | | {{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 (available today) and LB Core (in progress).

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.