● 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 Ops console generates your exact config and confirms live when your server connects.

Connect your server

  1. In the Ops console, open Integrations → 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://ops.citadel-hub.com/api/v1/lb-relay/<your key>/poll?",
            "responseUrl": "https://ops.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 the console if they can't complete.

Map perks

Create cosmetics on the store in your account at app.citadel-hub.com/store. Pick an LB Core preset (prefix, tag color, skin, killfeed color). The player's Steam64 is filled from the purchase. Connect the mod first under Integrations → LB Core in the console, or the product will say it cannot be delivered.

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).

LB webhooks into your activity and Discord

LB's own mods (Admin Tools, Killfeed, Advanced Groups, Airdrops, Loot Chests, Raid Alert, Virtual Garage, Enhanced Banking and more) already send webhooks from your game server. Citadel can receive the same events, so bans, kicks, teleports, kills, plot poles, airdrops and loot chests show up in the server's Activity and can be routed to any Discord channel. Your existing Discord webhooks keep working, and there is nothing to install, so it works on a rented host too.

  1. In the console, open Game events for the server and press Create webhook URL in the LBmaster webhooks panel. Copy the entry it shows. The URL is shown once.
  2. Add that entry to the webhooks array of webhooks.json in your profile's LBmaster/Config folder. Keep your existing entries. Remove any events you do not want from its webhookMessages.
  3. Restart the server. The panel changes from waiting for the first event to last event … once LB sends something.
  4. Route what you want on the same screen, by prefix: lb.hook.killfeed, lb.hook.admintools, lb.hook.groups, lb.hook.airdrop, lb.hook.lootchests, or lb.hook for everything. Posting to Discord needs Overwatch; the Activity history does not.

The webhook URL can only add events to this one server. It cannot read anything or send commands, and pressing New URL stops the old one at once.

  • 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 console and connect again to mint a new one.
  • Stuck on the perk route names for a specific LB feature? Open a support request and we will map your catalog with you.