Decouple base configuration and administration from companions
This commit is contained in:
@@ -28,3 +28,5 @@ Preparation has pending, ready and failed results. Each item is spawned once; re
|
||||
Once ready, checking preparation again returns the existing result. It does not recreate stock, destroyed containers or guards. Guards register once with the mission, allowing the optional HQ to coordinate those existing forces. Stock remains physical after players take it. End-of-round world teardown disposes of mission entities; mission stop cancels activation and strategic services.
|
||||
|
||||
Native validation covers actual insertion, document transfer, depletion, cache loss, objective progression and restart. Visual presentation, manual navigation, multi-client inventory contention and long-term entity cleanup remain separate acceptance requirements. The six-metre cache terrain sample spans about 0.625 metres of elevation; runtime checks also reject an obstructed crate footprint.
|
||||
|
||||
Guard population can use `Guarded 1` to select the injected faction catalog's group prefab. An explicit `Guards` resource remains available for a specialized composition, but its runtime faction must match the catalog's enemy faction. Merely changing faction keys does not retag incompatible character or support assets.
|
||||
|
||||
Reference in New Issue
Block a user