Integrate delivered HQ memory, finite physical convoy and RHS WCS dependencies

This commit is contained in:
2026-09-20 02:55:30 +02:00
parent e7b4141f69
commit a2aab17171
230 changed files with 37976 additions and 139 deletions
+13 -1
View File
@@ -31,7 +31,19 @@ The server derives administrator status from the requesting controller's authent
Clock settings apply once at the next round startup; changing them does not jump the current clock. Older valid settings files load the new defaults (14:00, 1×) without being rewritten. See [mission time](mission-time.md).
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.
AI and Intel register their own providers with the Core command service; the full Chat scenario loads both. Existing HQ interval/squad/radius and Intel carrying/reveal aliases remain available, as do `hq show` and `hq log`. They use the same authenticated authorization path.
Additional AI commands:
| Command | Effect |
| --- | --- |
| `/esc hq memory` | Show bounded delivered-report beliefs, confidence, uncertainty and travel estimates |
| `/esc hq stinger show` | Show the saved one-in-N initial equipment chance |
| `/esc hq stinger set N` | Set 0 to disable, 1 for every eligible actor, or 2–10000 for one in N; affects actors that have not rolled yet |
| `/esc hq convoy show` | Show the finite deployment task, retained vehicles, native cargo insertion results and stop reason |
| `/esc hq convoy start` | Opt into one initial six-vehicle deployment near the authored southern supply site; requires a suitable actual road, physical readiness and room for all 19 crew within the 60-body convoy admission cap |
Convoy deployment is under native verification. It is not automatically enabled at round startup. The same per-round receipt is retained after retries, partial startup and losses; this command never replaces a consumed convoy. Cargo is issued once and insertion failures are reported. Combat dismount/reboarding, complete supply routing and HQ response retasking remain separate migration work. The admission cap is not yet a global presence/materialization service. See [AI progress](ai-migration-progress.md) and [external dependencies](external-addons.md).
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.