EscapistsReintroduced/docs/response-medics-combat.md

Response-team medicine and combat priority

RKS 2 session 1790341620-1 (25 September 2026), journal part 1, confirms the old casualty floor repeatedly prevented lethal injury. Events 23102–23118 also show UAZ 6 switching to a routine road patrol while its combat flag was active; events 23162–23371 show subsequent travel with that flag still set. These establish an order conflict, not the exact reason for every individual failure to fire. The read-only SSH excerpt is retained in .local/analysis/medical-combat-2026-09-25/rks2-journal-excerpt.log.

Hunter UAZs now fill accessible driver, turret and cargo seats (bounded at 12), with exactly one cargo medic. US uses Green Berets and USSR uses Spetsnaz native presets. Modded factions first use optional ResponseSoldier and ResponseMedic resources in Configs/ERR/Content/Registry.conf, then their enabled character catalog. The registry supplies RHS ION, AFRF and MARSOC profiles because installed RHS character catalogs can be empty despite the characters being available. Catalog fallback prefers SF/recon presets and a medic; the ordinary soldier fallback comes from the selected faction's group. No wrong-faction medic is substituted. Missing crew resources defer deployment for 30 seconds before any vehicle/body is created or allowance consumed. Genuine partial physical spawn failures still consume their allowance to prevent duplicate forces. Native medic presets retain their authored medical bag, saline, bandages, tourniquets and morphine. Admission waits for every original occupant to be seated. The crew's native combat mode is explicitly fire at will.

Each physical soldier receives a finite startup allowance: two epinephrine and at least two morphine for SF/hunter troops; six of each for medics. Twenty-five percent of ordinary hostile soldiers receive one of each. Existing stock counts toward the allowance. Medic additions target the existing backpack when present, with overflow into free personal pouches only after the bag refuses insertion. Medics do not receive the optional mine/anti-air grants that could consume their treatment storage. Insertion failures and completion are logged; completed, pending or looted grants are never periodically replenished. This does not create AI healers for every ordinary squad; native medic roles are guaranteed specifically in hunter UAZs.

A native detected/identified contact no older than 15 seconds suspends that hunter's travel waypoint and pending travel radio order. Driver recovery cancels its own high-priority boarding action while combat is active. Existing native combat behavior remains free to fight/dismount. After contacts stop qualifying, a further 15 quiet seconds permits HQ travel and driver recovery again. Lost, destroyed, disarmed and old remembered targets cannot hold the patrol forever. The existing permanent objective-defender exclusions remain unchanged.

Full crews increase the number of physical AI per hunter vehicle. The existing three initial UAZs and maximum fifteen vehicle allowance remain unchanged.

Historical validation on 25 September 2026 (the lethal-player medical policy has since been superseded; see recovery.md): the medical-combat Workbench run completed 31 assertions, including the actual three-seat native UAZ crew and medic stock, bleeding/bandaging, timed saline, finite epinephrine and lethal blood loss. Source stayed unchanged during the run and private-prefix cleanup was confirmed. The strict runner still returned failure for loaded asset errors (localization references and inherited world/controller properties); there were no script or runtime failures. Repository medical/equipment/hunter checks passed. This is local scripted integration evidence, not manual or multiplayer combat acceptance. Logs, manifests and failed earlier attempts are retained under .local/analysis/medical-combat-2026-09-25/.

RKS 2 vehicle deployment failure, 26 September 2026

The 14:08 UTC server log contained two rounds. In both, all three opening UAZ attempts failed with “selected faction has no usable soldier/medic profile”; the second round also lost the fourth allowance the same way. Enemy faction was RHS ION. The same journal contains delivered sightings and infantry search orders, so HQ was operating; no hunter crew reached deployment. The installed ION character catalog is empty, although RHS supplies stocked ION medic prefabs. The downloaded journal is retained in .local/analysis/rks2-hunters-2026-09-26/.

Response profile overrides resolve this without changing faction identity. The hunter-faction Workbench fixture explicitly selects ION, unlocks the actual prison gate, checks the seated crew/medic stock, supplies a sighting at HQ's already-delivered intake boundary, and requires a radio-delivered hunter order and more than 30 metres of native vehicle movement. It does not certify a live multiplayer attack, visual detection, or combat accuracy percentages.

The ION native regression exposed a second issue: the crew's modded loadouts refused the required personal manpack. Each hunter UAZ now receives exactly one physical R-107M in vehicle cargo before admission. Its original seated crew can use that manpack as their HQ link; looting, capture, vehicle destruction, dismounting or mission teardown removes the vehicle link. No medic backpack is replaced and no lost radio is replenished. Personal radios retain their existing rules. Radio-fitting and HQ routing both recognize the physical vehicle radio.

Final native validation: all three ION crews admitted with their vehicle radio; the medic had at least four saline/bandages, six morphine and six epinephrine. All three UAZs received a contact order through the production radio route; the fixture confirmed native driving beyond 30 metres. Source hashes were unchanged during the run and cleanup was confirmed. All fixture assertions passed; the strict runner's asset scan still reports existing inherited asset errors. Earlier failed/stalled runs are preserved beside the successful run.

The final complete repository check suite and the targeted vehicle-radio/aim policy regressions also passed after the radio changes. No server restart, Workshop publication or Git push was performed.