Server Runtime And Operations

Server Runtime And Operations

This is a gateway for prompts and readers that ask for "server runtime" or "server operations" without knowing which owner page they need.

Do not put long source proof here. Runtime and operations are intentionally split so gameplay loops, deployment contracts and release evidence do not overwrite each other.

Branch scope matters for server startup. Current docs head docs/developer-wiki-index f74b3822 keeps the broad server-runtime source anchors from a6785f51, 4277a2ad and the earlier 92c5cf05 / 6afcc58e snapshots; hosted-FPS source paths were rechecked on 2026-06-24 and repo docs branch HEAD@4a1bc13edde6 is unchanged from d0161083 / a27086cd for that surface. Current stable/B74.1 origin/master@f8a76de34 differs for AI supply-truck startup, Patrols v2 and FPS publisher cleanup, with FPS single-publisher start/removal anchors now at Chernarus Init_Server.sqf:950,:996-998 and Vanilla :937,:983-985; current B74.2 keeps the same FPS shape with source-Chernarus line drift to :983,:1029-1031; historical a96fdda2 matches the supply-truck/FPS cleanup but not Patrols v2, and no current release/* head was exposed. Use Server gameplay runtime atlas before citing source line anchors as current-master evidence.

Which Page Owns What

Need	Open this	Why
Long-running gameplay loops	Server gameplay runtime atlas	Town capture, town AI, resources, victory, supply mission tracking, server FPS publishers, side radio and dormant server hooks.
Server branch/source split	Server gameplay runtime atlas, Current source status snapshot	Separates docs-checkout line anchors from current origin/master, release and upstream branch truth.
Running or packaging a server	Server ops runbook	Mission generation, deploy inventory, BattlEye paths, extension paths, DiscordBot data paths, RPT/log collection and dedicated/listen smoke boundaries.
Public-server trust boundaries	External integrations, Integration trust boundary audit	DiscordBot, in-repo extension, out-of-repo AntiStack DB extension, BattlEye filter posture and missing production config.
Authority hardening	Server authority migration map, Hardening roadmap	Server-owned validation design, direct-PV/PVF risks and implementation order.
Headless/client delegation	AI runtime/HC loop map, Headless delegation/failover	HC ownership, client FPS delegation, town AI/static-defense update-back and disconnect/failover policy.
Performance testing	Performance opportunity sweep, Testing workflow	Benchmark order, old BE comparison route, full-server FPS matrix and proof level naming.
Current branch truth	Current source status snapshot	Whether a finding is stable-master, docs branch, release branch, generated Vanilla or upstream candidate truth.

Source Orientation

Use these source clusters only as orientation. The owner pages above carry the detailed evidence and next gates.

Cluster	Source area	Owner page
Init and worker startup	Missions/[55-2hc]warfarev2_073v48co.chernarus/Server/Init/Init_Server.sqf	Server gameplay runtime atlas
Branch-sensitive startup deltas	AI supply-truck gate, Patrols v2 side driver, FPS publisher cleanup	Server gameplay runtime atlas, Feature status register, Source fix propagation queue
Town/camp runtime	Server/FSM/server_town.sqf, server_town_ai.sqf, server_town_camp.sqf	Towns/camps/capture, Server gameplay runtime atlas
Economy/resource runtime	Server/FSM/updateresources.sqf, supply mission server modules	Economy/towns/supply, Supply mission architecture
Integration and telemetry	Server/CallExtensions/GlobalGameStats.sqf, DiscordBot, Extension, BattlEyeFilter/publicvariable.txt	External integrations, Server ops runbook
Release proof	Tools/LoadoutManager, smoke scripts, RPT captures	Tools/build workflow, Testing workflow

Agent Rule

If a task asks for Server-Runtime-And-Operations.md, start here, then edit the owner page that matches the task. Keep this gateway short. Add new runtime facts to Server gameplay runtime atlas, new deployment facts to Server ops runbook, and new proof gates to Testing workflow.

Continue Reading

Runtime: Server gameplay runtime atlas | Operations: Server ops runbook | Testing: Testing workflow

Main map: Home | Status: Progress dashboard | Agent index: agent-machine-index.json