escapists/EscapistsReintroduced
1
0
Fork 1
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Decouple base configuration and administration from companions

Browse Source
This commit is contained in:
jakub
2026-09-19 03:15:33 +02:00
parent 35daefa860
commit ce19ec68df
96 changed files with 9200 additions and 171 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/configuration.md
+36
View File
@@ -0,0 +1,36 @@
# Base mission configuration
The independent Core scenario loads `Configs/ERR/VanillaFactions.conf` through `ERR_GameMode.m_FactionDefinition` and `Configs/ERR/EveronSites.conf` through the scenario component. Both are successor resources. Changing a configuration requires restarting the scenario; the live round is not repopulated.
## Factions and assets
The catalog explicitly selects the player faction, enemy faction, prisoner character, guard group and extraction helicopter. Current defaults are unarmed US prisoners, Soviet guards and the vanilla unarmed Mi-8 transport. Both factions must exist in the world's faction manager and consider one another hostile. Required prefab resources must resolve. Guard groups must have the catalog's enemy affiliation; an incompatible group is rejected rather than relabelled.
This provides an injection boundary, not automatic support for arbitrary addons. A different faction also needs matching characters, inventories, world manager configuration and companion support compositions. The current mortar crew remains a vanilla Soviet composition and rejects a different enemy faction.
Supply/guard placement and finite stock are described in [site authoring](site-authoring.md).
## Administration
Open the normal game chat and enter a command. Core provides:
| Command | Access | Effect |
| --- | --- | --- |
| `/esc status` | Server administrator | Current objective or startup failure cause; adds HQ status when Chat is loaded |
| `/esc settings` | Server administrator | Current shared settings and values |
| `/esc mission radio show` | Server administrator | Radio defence duration in seconds |
| `/esc mission radio set N` | Server administrator | Save a whole-number duration from 30 to 1800 seconds |
| `/esc spectate next` | Spectating player | Select the next surviving friendly player |
| `/esc spectate previous` | Spectating player | Select the previous surviving friendly player |
The server derives administrator status from the requesting controller's authenticated player ID. Clients cannot send an administrator flag through the RPC. Requests are limited in length and rate; malformed numbers and out-of-range values leave the previous setting intact. Saved values belong to the server profile, not client profiles. Changing radio duration affects the current defence calculation, so configure it before starting the transmission.
With the companion Chat addon, existing HQ interval/squad/radius and Intel carrying/reveal aliases remain available, as do `hq show` and `hq log`. They extend the same Core command service and authorization path.
The command parser and setting mutations have native service tests. Actual remote RPC ownership, chat usability and pre-spawn presentation still need multiplayer/UI acceptance.
## Failed preparation
If the faction/catalog setup or authored site preparation fails, the mode retains the reason, stops its services and refuses progression or spawning. It does not fall back to a partially prepared mission. A local hint describes the failure and `/esc status` gives administrators the cause. Correct the resource/configuration and restart the scenario. There is no automatic retry that recreates stock or forces after failure.
Waiting for normal site preparation does not consume a player's spawn retry budget. Once ready, actual failed spawn requests are bounded. This does not remove the one-life or identity requirements.