Extraction & Infiltration Systems

Category: Mission Flow Control
Context: In POV 3.0, drones don’t simply teleport into high-security corporate buildings. Deployments (and extractions) must reflect a physical, localized presence within the game world. The ExtractionSystem manages the spatial and temporal requirements for transitioning between the safe “Neighborhood” hub and active “Raid” scenes.

The Holdout Mechanic

Both infiltration (InfilZoneTrigger) and exfiltration (ExtractionZoneTrigger) share a core design ethos: Vulnerability.

Neither action is instantaneous. The player must navigate their drone into a specific sphere collider and maintain their position for a defined duration (e.g., timeToExtraction = 10s).

This transforms the end of a mission from a simple “reach the finish line” objective into a tense holdout sequence. If the drone is detected, attacked, or forced out of the designated extractionSphere by security forces before the timer elapses, the progress is instantly zeroed (extractionTimer = 0f).

State Machine Triggers

stateDiagram-v2
    [*] --> Neighborhood_Hub
    
    state Neighborhood_Hub {
        Idle --> Infil_Zone : Enter Trigger Radius
        Infil_Zone --> Idle : Exit Early (Timer Reset)
        Infil_Zone --> Raid_Loaded : Hold 10s
    }
    
    Neighborhood_Hub --> Active_Raid : Scene Transition
    
    state Active_Raid {
        Exploring --> Extraction_Zone : Enter Trigger Radius
        Extraction_Zone --> Exploring : Exit Early (Timer Reset)
        Extraction_Zone --> Escaped : Hold 10s (Survive)
    }
    
    Escaped --> GameManager : HandleSuccessfulExtraction()

System Constraints

The architecture uses strict boolean guarding to prevent scene-breaking states: