[!NOTE] This documentation covers the very first mechanics tested for the game. During the early STIK prototype phase, primitive geometry (cubes/spheres) was used as placeholders to represent different data types before final art assets were integrated.

Simulated Transfer Interface Kit (STIK)

Category: Core Systems Design
Context: The STIK mechanic attempts to gamify the “downloading data” trope commonly found in stealth/action games by anchoring it deeply into physical space and consequence. Within the framework of POV 3.0 (a mission-based drone operations and stealth progression game), the player uses remote-controlled platforms (e.g., spiders, crawlers, flyers) to covertly gather critical data from high-security building areas on behalf of factions like PixelShift (DEMOTECH, FED, etc.).

Full Pipeline

The STIK system spans from drone deployment through data extraction, processing, and eventual sale. Every step carries physical risk and economic consequence.

STIK Pipeline: Infiltration to Payout

Core Interaction Loop

Data theft requires interfacing external hardware (the thumbdrive) with in-game Terminals.

The process is inherently precarious. The drone must physically maneuver the drive into a Terminal port while maintaining a low suspicion level, initiating a data transfer defined by the Terminal’s transmission speed and the Drive’s maximum capacity.

graph TD
    A[Player Interacts with Terminal] --> B{Is Terminal Secured?}
    B -- Yes --> C[Hack/Pin Mini-game]
    B -- No --> D[Open Access]
    C -- Success --> D
    C -- Fail/Timeout --> E[Lockout / Alarm]
    
    D --> F[Enable Data Download Port]
    F --> G[Player Inserts Flashdrive]
    G --> H[Snap Physics & Begin Download]
    
    H --> I{Download State}
    I -- Uninterrupted --> J[Data Max / Safe Eject]
    I -- Pulled Early / Interrupted --> K[Data Corruption Penalty]

Physical Consequences: The Interruption Penalty

If the player breaks the physical connection before the progress is complete—whether by getting shot, needing to flee, or manually pulling the drive early out of panic—the StopDownload() function triggers a corruption event.

When interrupted, 5% to 40% of the currently captured data is instantly flagged as corrupted (corruptedDataAmount).

Because a flash drive’s itemSellValue is strictly derived from the ratio of uncorrupted data to the drive’s total capacity, pulling a drive early doesn’t just halt progress—it actively destroys the payout of the data already stolen.

Structural Integrity

Flashdrives exist physically in the world as interactable Ragdoll/Physics items meaning they can mitigate or absorb damage.

Structural Health: Drives have an HP limit (default 100). Taking physical/ballistic damage degrades this.
Catastrophic Failure: If currentStructuralHealth hits 0, hasStructuralIntegrity becomes false. The drive is “bricked” and cannot interface with Terminals at all.
Material Shaders: Drive damage is visually relayed to the player via a _Damage property block in the shader, scratching and destroying the mesh as it takes a beating.

Storage Tiers & Visuals

To quickly communicate value and limits to the player during high-stress scenarios, STIK heavily relies on silhouette and albedo indicators:

Small (Red): 1 GB (Fastest to fill, lowest payout risk)
Medium (Green): 50 GB
Large (Blue): 100 GB (Highest time-on-target risk, massive payout)
Custom (Gold/Lerp): Specialized objective drives.