Consistent behavior when seen by a pacifist enemy

[qoala]

How do other guards behave when you're seen by a pacifist guard?

As far as the pacifist itself, it turns to look directly at your agent and tracks them as they move, similar to armed guards, but without shooting. If it's not cowardly (CFO, scientist), it investigates the destination to where it last saw your agent move.

Current:

• armed guards/drones: all other guards in radio range of the original guard become alerted. If they could see your agent by turning in place, they immediately do so, otherwise they add an investigation point for your agents initial position. Even if your agent moves and is tracked, the radio-ed investigation point does not move.
• cameras: Adds an investigation point at your agent's initial position via radio. No guards turn.
• camera drone (pacifist): Adds an investigation point at your agent's initial position via radio. Other guards do not turn.
• pulse drone (pacifist): like a camera drone, though it only sees its own tile (separate bug: vision after moving diagonally)
• null drone (pacifist): like an armed guard, triggers other guards to turn and overwatch
• unarmed humans: No investigation point communicated. Guard tracks your agent, but there's no other risk to your agent.

Possible pacifist overwatch-alerts option: [pacifist drones and humans, pacifist drones, vanilla=null drones only, none]

[qoala]

My above assessment may be wrong, pulse drones might also cause guards to turn and overwatch.

[qoala]

My initial assessment was very wrong for camera and pulse drones.

• Camera: When you are seen by a camera,
  • guards within range 12 of the camera are notified and will investigate the first tile where the camera saw an agent that turn.
• Camera Drone: When you are seen by a Camera Drone,
  • guards within range 8 of the drone are notified and will investigate the first tile where the camera saw an agent that turn.
  • the nearest non-camera_drone guard is notified and will investigate the first tile where the camera saw an agent that turn. (If any guards were notified by the range 8 signal, this has no additional effect)
  • guards within range 0 of the drone (on the same tile) are alerted and will turn to face the agent themselves. (if somehow the guard cannot see the agent from its tile, the guard will hunt for your agent on its own turn)
• Pulse Drone: When you are seen by a Pulse Drone (step on the same tile)
  • guards within range 8 of the drone are alerted and, if possible, will turn to face the agent themselves.
  • Possibly additional camera-like behavior from use of simcameradrone type without camera_drone trait, but it might not be able to trigger the camera codepath. I haven't been able to trigger it in testing.
• Null Drone or any other normal drone/guard: When you are seen by a guard,
  • guards within range 8 of the drone are alerted and, if possible, will turn to face the agent themselves.

---

Two properties control how "pacifist" drones signal other guards when they see agents. (neither of them is the trait pacifist=true)

• trait camera_drone=true
  • set on Camera Drone, Refit Drone (DLC side-mission), Scanner Drone (AGP), OMNI Drone (AGP)
• type="simcameradrone" (determines the simunit subclass of the unit's logic. Normal human guards are simunit. Normal drones are simdrone)
  • set on Camera Drone, Pulse Drone (DLC), Refit Drone (DLC side-mission), Scanner Drone (AGP), OMNI drone (AGP)

Notes on where these and related properties are/aren't used:

• Pulse Drone is odd in using simcameradrone without having the camera_drone trait. Effects of this noted below.
• Null Drone is pacifist, but has neither of the above properties. This may have been intended, since the properties are labelled "camera drone", not "pacifist drone". However camera drones are so common, that players assume their behavior is prototypical for pacifist drones and not a special case unique to them.
• Type simcameradrone inherits some behaviors from simcamera, the class for mainframe cameras. This is why results from Camera Drones resemble cameras in many, but not all, respects.

Relevant code sections:

• sim/btree/senses: Senses:processInterestShared
  • Triggered on this guard when another unit tries to communicate an interest to other guards (TRG_NEW_INTEREST) within a fixed range of the original sharing unit.
  • If the shared interest includes a target (not just coordinates) and this unit can turn to see the target, this unit does so.
  • If the shared interest has no reason (or is of an alerting interest reason in Senses:addInterest), this guard becomes alerted.
• sim/btree/actions: Actions.ReactToTarget
  • Triggered within a guard's Brain in RangedCombat/MeleeCombat/NoCombat when they have a target.
  • If camera_drone trait, share an interest to that target with a range of 0. No reason provided.
  • Else, share an interest to that target with a range of 8. No reason provided.
• sim/units/simcameradrone: simcameradrone:addTrackingInterest
  • Called from simcamera:performTracking from simcamera:onTrigger on TRG_OVERWATCH from simengine:processReactions (called with the triggering unit whenever a unit does something that could trigger overwatch or other reactions)
  • Only fires once each turn. After the first time each turn, a simcamera/simcameradrone gains the trait tracker_alert and stops sharing new sightings.
  • Shares an interest with a range of 8. No target. REASON_CAMERA is not alerting.
  • This is almost identical to the signal sent by a real camera (from simcamera:performTracking if not self:addTrackingInterest defined), except that cameras have range 12.
• sim/units/simcamera: simcamera:performTracking
  • After calling simcameradrone:addTrackingInterest, if camera_drone trait,
  • Add an interest to the closest NPC-controlled unit without camera_drone trait. This is the same call as made by a security dispatch mission when you loot the storage container.
  • If the closest guard was within range 8, that guard was already notified by the addTrackingInterest. This just compensates for camera drones too far from other guards. Does not apply to cameras.

Additional Notes:

• Triggering the above codepaths
  • Normal guard sharing comes from an Action in the guard's Brain btree. Camera sharing comes from an onTrigger directly registered by the unit (presumably because cameras don't have brains).
  • Still need to identify a common root caller that reaches both codepaths, if any exist. It's possible some player actions could only trigger one codepath.
  • Pulse drones should theoretically have both guard sharing (because they lack camera_drone trait) and cameradrone sharing (because they have simcameradrone type), but I haven't seen the "notifies nearest guard regardless of range" in testing. It's possible the weird limited vision of pulse drones doesn't trigger the TRG_OVERWATCH codepath.
• Other checks for camera_drone trait:
  • sim/aiplayer: aiplayer:spawnInterest
  • Used by security dispatch mission when locker is looted. Used by simcameradrone+camera_drone when seeing an agent for the first time each turn.
  • Finds the closest unit that is both owned by the NPC player and does not have camera_drone trait
  • Because they lack this trait, this can select pulse drones. Because of noInterestDistraction trait ("focused AI"), the pulse drone ignores the interest point and no further guards are alerted.
  • sim/btree/senses Senses:processAppearedTrigger
  • Triggered when something first comes into view for the guard/drone.
  • If the seen unit is a hostile turret, seer units with camera_drone use addInterest, while everything else uses addTarget. Unclear what implications this has for unarmed units.
  • sim/btree/situations/combat: CombatSituation:addUnit
  • The thoughtVis (triangle icon above the guard's head) is normally "combat" (red reticle icon, "engaging intruders") in this situation. Special cases for vip trait: "fleeing" (red running icon, "fleeing intruders") and camera_drone trait: "hunting" (red exclam icon, "Hunting for intruders", same as in the "hunting" situation)