The Configuration page controls how Asphyxia behaves: which detections run, how strict each one is, and what is blocked outright.
This page covers saving changes, what each category holds, and how to tune a detection without causing false bans.
Saving changes
- Make your changes. Settings are grouped into categories on the left; changed rows are marked for review.
- Press Save. Nothing takes effect until you save — move between categories freely, changes are held until then.
- Restart the resource (
restart asphyxia). Your game server reads its configuration once, at startup.
Categories
General — server-wide behaviour: Test Mode (detections log but do not
punish), Anti VPN with an IP whitelist, log retention (0 keeps everything),
and a switch to stop matching player IPs against bans (for servers behind a
proxy that gives every player the same IP).
Trust Filter — scores a player’s account before they finish connecting and turns away accounts that look disposable: minimum score, penalties for missing identifiers, required account types, Discord account age, Steam profile, and FiveM playtime. Start permissive and raise it gradually while watching your connection logs.
Client Detections — on/off switches for each client-side detection (each described on Detections), plus OCR keywords, a blacklisted-events list, and blacklisted weapons (names from Weapons).
Server Detections — checks your server performs itself: explosion guards (rate limit, per-type blacklist with IDs from Explosions), entity-spawning rules per type (blacklist or whitelist, spawn limit with window), weapon/task/particle guards, and guarded plus rate-limited server events.
Blacklist or whitelist? A blacklist allows everything except what you list — right for blocking a few known-abused models. A whitelist allows nothing except what you list. Most servers want a blacklist.
Live View — video quality and limits for
Live View. Who may watch is set by the
viewLiveCapture permission on Admins.
Server Options — per-server integration settings, including the webhook URL
used for ban notifications and screenshots.
Tuning a detection
Don’t disable a detection because it fired once. Instead:
- Read the detail on Strikes and Logs to see what was actually observed.
- Whitelist the player if it affects one person — see Whitelisting.
- Loosen the setting if it affects many players.
- Disable it only as a last resort, and report it on Discord.
Test Mode lets you do all of this on a live server without punishing anyone.