Connect a game server

To grant perks in-game, Citadel needs a way to reach the box. There are three. Nothing connects inbound to your machine and there are no ports to open.

@CitadelAdmin (DayZ)

If your server already runs @CitadelAdmin — the setup in Getting started, whether in direct mode on a rented host or with the Citadel Server Manager on your own machine — it is already connected. Perks target it with no extra step and no relay key. Priority queue grants apply through either path, only when something on the box can write the file; the current Workshop build typically cannot, and the console says if it cannot. Whitelist grants need the Server Manager.

There is no separate connection to make here, and nothing else to buy.

LB Core mod (LBmaster)

In the Ops console, open Integrations → LB Core and click Connect a server. The console generates your exact Api.json entry — key included — and listens live until your server's first poll arrives. No ports to open: the mod calls Citadel. Full details: LB Core (LBmaster).

Your own integration

Any server or worker can be a Command Relay client by speaking the Command Relay API (handshake → poll → apply → ack). See the Relay API reference. Custom relays are created under Relays in the console. Hosted Overwatch does not use a key from that screen.

How perks reach the server

It depends which path you used.

• @CitadelAdmin. Ops queues the grant for the mod or the Server Manager. There is no relay key and nothing for you to poll.
• LB Core. The mod polls Citadel and applies the perk on its next pass.
• A custom Command Relay client. Citadel queues a command; your client polls with its csk_ key, applies it, and acknowledges it. Delivery is at-least-once: a command is redelivered until your client confirms it applied.

The hosted store refuses a perk this box cannot grant at save time, rather than taking payment. A webhook still accepts the payload. Ops applies it only when this box can write the file; otherwise the grant stays queued for a custom client.