● Citadel Docs

LB Core (LBmaster)

If you grant perks through the LB Core DayZ mod (LBmaster — chat prefixes, tag colors, skins, killfeed colors, custom groups), Citadel acts as the backend the mod polls. Setup is self-serve: the dashboard generates your exact config and confirms live when your server connects.

Connect your server

  1. In the dashboard, open Store → Game servers (LBmaster / LB Core) and click Connect a server. Name it and Citadel generates your Api.json entry — with your API key already filled in. The key is shown once.
  2. On your game server, open profiles\LBmaster\Config\Common\Api.json (the mod creates it on first launch) and replace the example entry with the generated one — or use the Copy full file button for a fresh install. It looks like this:
{
    "version": 2,
    "grantDeveloperAccess": 1,
    "entries": [
        {
            "enabled": 1,
            "name": "Main DayZ server",
            "pollUrl": "https://api.citadel-hub.com/api/v1/lb-relay/<your key>/poll?",
            "responseUrl": "https://api.citadel-hub.com/api/v1/lb-relay/<your key>/response?",
            "apiKey": "<your key>",
            "restrictedAccess": 0
        }
    ]
}
  1. Save and restart the server. The connect page listens live and flips to "Mod connected" the moment your server's first poll arrives — no guesswork.

Notes:

  • Keep the trailing ? on both URLs — the mod appends its own parameters there.
  • The key appears in both the URLs and the apiKey field on purpose; Citadel accepts either, so the integration works regardless of how the mod sends it.
  • No ports to open and no IPs to share: the mod calls Citadel, never the reverse.

Reliability

Citadel's relay queue is durable. If a player buys a perk while your server is down (restart, crash, maintenance), the grant waits in the queue and delivers on the server's next poll — purchases never evaporate. Deliveries require the mod's acknowledgement, redeliver if unconfirmed, and surface in your dashboard if they can't complete.

Map perks

Create perks on the Store page and map each to the LB perk it grants (prefix group, tag color, skin, killfeed color), using {{user.steam64}} and {{form.answers.N}} placeholders in the payload.

Group-based perks require the player to already be in a group — validate that before selling them. Avoid setting a permissionToApplyGroup that isn't in your mod config (the player can otherwise be added to the first group, which may be your admin group).

Troubleshooting

  • Still "awaiting first poll"? Check the entry has "enabled": 1, the file was saved before the restart, and the machine allows outbound HTTPS.
  • Lost the key? Keys can't be recovered. Disconnect the server in the dashboard and connect again to mint a new one.
  • Stuck on the perk route names for a specific LB feature? Contact us and we'll map your catalog with you.