Server configuration | Asphyxia Docs

Asphyxia’s settings are split in two. Secrets and integrations live in server.cfg because they are specific to one machine. Everything controlling how the anti-cheat behaves lives on the dashboard’s Configuration page.

Required

These three come from your dashboard when you create a server. Asphyxia will not start without all of them.

Convar	Description
`asphyxia_license`	Your license key, verified at startup
`asphyxia_server_id`	Identifies which server’s configuration to download
`asphyxia_shared_secret`	Secures everything sent to the Asphyxia API

server.cfgini

set asphyxia_license       "your-license-key"
set asphyxia_server_id     "your-server-id"
set asphyxia_shared_secret "your-shared-secret"

Optional

Convar	Default	Description
`asphyxia_ban_webhook`	(none)	Discord webhook URL for ban screenshots
`asphyxia_discord_bot_token`	(none)	Bot token for Discord Lookup
`asphyxia_debug`	`false`	Turns on debug mode

Discord bot token

Discord Lookup asks your game server to look up a Discord account, so your game server needs a bot token. Create an application in Discord’s Developer Portal, go to Bot → Reset Token, copy the token once, and add it:

server.cfgini

set asphyxia_discord_bot_token "your-bot-token"

No privileged intents or server memberships are needed. The token stays on your machine and is never sent to the dashboard — treat it like a password.

Ban webhook

When Asphyxia bans someone it captures their screen, posts the image to your Discord webhook, and attaches the link to the ban record on the Bans page:

server.cfgini

set asphyxia_ban_webhook "https://discord.com/api/webhooks/..."

Without it, bans still work but have no screenshot attached.

Debug mode

server.cfgini

set asphyxia_debug "true"

Debug mode lets you trigger detections on a live server without punishing anyone: bans stay in memory, nobody is disconnected, no webhooks fire, and admins with bypassDetections are not exempt so you can test on yourself.