Configure anger points per Sarka instead of cars per point
continuous-integration/drone/push Build is passing
continuous-integration/drone/push Build is passing
This commit is contained in:
@@ -63,6 +63,21 @@ requested totals instead of preventing mission startup. The admin Status page
|
||||
also shows these totals. This is an interim checkpoint system, independent of the
|
||||
existing HQ-directed road interceptions.
|
||||
|
||||
## Šárka special-forces hunters
|
||||
|
||||
Under **Forces → Šárka hunters**, set **Anger points per Šárka** from 1 to 30.
|
||||
The default is 3. Each wave requests the current anger divided by this value,
|
||||
rounded down: a value of 5 gives no car below 5 anger, one at 5–9, and two at
|
||||
10–14. Zero disables new waves; already deployed cars and crews remain.
|
||||
Each car carries four special-forces soldiers, including a medic. Changes apply
|
||||
to the next wave; the existing interval and placement rules remain unchanged.
|
||||
|
||||
The saved key is `mission.sarkaAngerPerCar` in `$profile:Escapists.json`.
|
||||
The command is `/esc mission sarkapoints set N` (also `show` and `help`).
|
||||
Older `sarkaCarsPerAnger` settings migrate to the new default of 3 when enabled;
|
||||
an old zero remains disabled. An explicit new key takes precedence. The old
|
||||
`sarkacars` command is retired to avoid silently reversing its meaning.
|
||||
|
||||
## Mission restarts
|
||||
|
||||
The admin menu **Mission** page includes two independent settings:
|
||||
|
||||
Reference in New Issue
Block a user