F1 config console

bs_config. Press F1 in game (rebindable, it’s the +bsconfig key mapping). Only staff can open it.

Who can do what

• Open and edit: anyone bs_admin sees as admin (bs.admin / bs.superadmin ACE).
• Delete profiles: only bs.owner. server.cfg gives it to group.superadmin:

  add_ace group.superadmin bs.owner allow

  If you want it narrower, give it to one identifier instead.

Everything is checked again on the server. The page only asks.

What’s in it

Around 314 settings from shared/schema.lua, in categories: Zombies, Economy & Loot, Survival & Medical, Drugs & Addiction, Gadgets, Factions/Squads/VIP, Weather & Time, Weapons & Recoil, Safe Zones & PvP, World Events, Anti-cheat, Keybinds & UI.

Every key is a real key in a resource’s config file. The defaults are read from the files at runtime, so if you edit a file the console follows. The only keys that aren’t in files are the Global.* multipliers (XP, hunger, thirst, loot, trader prices, recoil).

Each row has a slider or field, the file default, min/max, a modified badge and reset. Top search filters everything, / focuses it. “Modified only” shows what you changed.

Live vs restart

Most values are live: they get patched into the resource’s config table and code that reads them each time sees the change at once.

Some are marked restart <resource>, because the code caches them at boot. Those rows have a restart button (it runs ensure <resource>). If a “live” value seems to do nothing, that code caches it too. Press restart.

Profiles

• Built in, read only: Default, Easy, Hardcore, PvP. Edit one and Apply asks you for a new name.
• Your own: as many as you want. Save as, rename, duplicate, delete (owner only, not the active one), set active.
• A profile only stores values that differ from the file.

From the server console:

bsconfig_active            -- show the active profile
bsconfig_active Hardcore   -- switch

Stored in bs_config_profiles, bs_config_state and bs_config_audit (migration 026_config_profiles.sql).

Share a profile

Export gives you a code (BSC1: + base64) and the JSON. It also writes resources/[beyond]/bs_config/exports/<name>.json on the server. Import takes the code or JSON. Values get clamped and unknown keys are dropped, so a profile from another version of the framework won’t break anything, it just loses what doesn’t exist.

Audit

Every set, revert, create, rename, delete, activate and restart is logged with who and when. You can revert a single change from the Audit view.