Appearance
Feature flags and integrations
Optional systems remain in the source so communities can expand the framework. They are not automatically enabled or configured by the clean database.
Pawn switches
Most switches live in gamemodes/config/header.pwn:
| Switch | Default | Effect |
|---|---|---|
FEATURE_CUSTOM_SKINS | 0 | Optional ACP-uploaded character models |
FEATURE_REMOVE_STOCK_GRAFFITI | 0 | Broad stock graffiti removal |
FEATURE_REQUIRE_DISCORD_VERIFIED | 0 | Require configured Discord account verification in-game |
FEATURE_EMMET | Commented out | Optional gun-dealer system |
FEATURE_FNR | Commented out | Fear/respect progression |
FEATURE_GANGZONES | Commented out | Gang/turf zone system and associated content |
FEATURE_GANGTAGS | Commented out | Extra gang-tag/model features; text tags remain separate |
Two different switch styles
#if FEATURE_CUSTOM_SKINS reads a numeric value. #if defined FEATURE_GANGZONES checks whether the define exists at all. Setting a presence-based define to 0 still enables that branch. Follow the style used by the actual source and recompile.
FIRE_DIVISION_ENABLED is a separate compile-time switch in the main gamemode. FDSA already uses FACTION_TYPE_EMS; do not change medical access to an unrelated faction type when adding divisions.
Custom skins
Enable FEATURE_CUSTOM_SKINS=1 in Pawn and CUSTOM_SKINS_ENABLED=true in the web environment together. Configure agent file transfer and artwork downloads. No custom character models are shipped. Read the full skin workflow before uploading.
Discord
Discord is disabled by default in both web and game. To configure your own integration:
- Create your own application/bot and OAuth settings.
- Populate the blank
AUTH_DISCORD_*, bot, guild and role environment fields. - Set
DISCORD_ENABLED=truein web only after all required values are present. - For game-side logging, opt into the
DISCORD_ENABLEDdefine in your local secrets file and configure the compatible connector/runtime. - Supply only the channel/role defines you actually need; undefined game logging destinations are skipped.
Web OAuth and game logging are separate. In-game mandatory verification stays off until you deliberately enable its own flag. No real guild, role or channel IDs are provided. Keep password login/recovery functional when testing linking.
Voice and other external services
VOICE_ENABLED=false keeps the external voice endpoints unavailable. The LiveKit template requires your own service URL, key and secret; it is not hosted by the framework. Leave VOICE_DEV_KEY unset in production.
reCAPTCHA is optional and needs a matching site/secret key pair. SMTP is required for the documented verification/recovery/2FA flows; it is configured separately from Discord.
After any change, compile optional code branches, restart the relevant service and test as a normal user. A visible setting is not proof that every asset, database record or external service it needs exists.