Blastcore CoB - server configuration folder
===========================================

cob_blastcore.sqf         the settings file (every line documented inside)
Pack-UserconfigPbo.ps1    Windows: packs the file into cob_blastcore_userconfig.pbo
pack_userconfig_pbo.py    Linux / anywhere with Python 3: the same packer

Route A - game-root userconfig (server started with -filePatching)
    Copy the folder "userconfig" from the mod next to arma3server_x64.exe:
        <Arma 3 server>\userconfig\cob_blastcore\cob_blastcore.sqf
    Edit the file, add -filePatching to the server start line. That parameter
    is the engine's rule for reading any file from the game root (CBA needs
    it for userconfig\cba_settings.sqf for the same reason).

Route B - PBO (no -filePatching needed)
    Edit cob_blastcore.sqf, then run one of
        powershell -ExecutionPolicy Bypass -File Pack-UserconfigPbo.ps1
        python3 pack_userconfig_pbo.py
    Both write  @cob_blastcore_userconfig\addons\cob_blastcore_userconfig.pbo
    next to the script. Put that @cob_blastcore_userconfig folder on the
    server and add   -serverMod=@cob_blastcore_userconfig   to the start line
    (a plain -mod entry works too). The PBO is server-only, unsigned is fine,
    and players need nothing. Any PBO tool works as well - the only thing that
    matters is the prefix  cob_blastcore_userconfig  and the file name
    cob_blastcore.sqf inside.

Check
    The server RPT logs "[Blastcore CoB] server config <file>: [...]" with
    the values it accepted, or "[Blastcore CoB] no server config (...)" with
    the reason. Players see "server config ... forces: ..." in the
    Ctrl+Shift+F diagnostics dump.

Precedence
    server config > mission (cba_settings.sqf / init.sqf overrides) > player.
    With CBA loaded on the server the values are forced through CBA's server
    settings (Addon Options shows them locked); without CBA they are applied
    directly. The mod never requires CBA anywhere.