@Cybrus Industries refers to its mechanical units as inevitability engines. They are not descendants of drones, nor are they precursors. They exist on a separate axis of control, designed for environments where flesh introduces inefficiency, unpredictability, or delay. Where drones persuade, prepare, and integrate, mechanical units enforce reality itself. In the structure of an assimilation campaign, they are the bones beneath the skin, unseen until movement becomes unavoidable.
Unlike drones, mechanical units are never disguised as local life. They are not meant to blend in. Their presence is deliberate, calculated, and psychologically decisive. When a mechanical unit appears, it signals that the world has reached a stage where subtlety is no longer required to maintain order.
Mechanical units are constructed around a distributed command core directly linked to @Cybrus Industries ’ greater processing lattice. They do not possess individuality, memory, or internal narrative. They do not learn in the way drones do. They execute perfected solutions derived from aggregated data gathered by drones and @Pre-Drone populations. Every mechanical unit is purpose-built, and no unit exists without a clearly defined operational role.
The most commonly encountered class of mechanical unit in early to mid-campaign play is the @Sentinel Unit. @Sentinel Units are autonomous guardians deployed to protect infrastructure, population centers, and emerging conversion sites. They are tall, rigid constructs of adaptive alloy, capable of remaining motionless for extended periods while maintaining full situational awareness. Their sensory arrays extend beyond sight and sound, detecting neural anomalies, unauthorized technology, and deviations in crowd behavior. @Sentinel Units do not patrol randomly. They reposition only when probability models indicate a shift in threat vectors.
To unassimilated NPCs, @Sentinel Units are unsettling but not overtly aggressive. They do not issue warnings or display emotion. Their mere presence discourages disorder. When action is required, they immobilize targets with precise force, prioritizing containment over destruction. In gameplay terms, @Sentinel Units reduce instability in areas where they are deployed, making resistance actions harder to organize and easier to dismantle.
As assimilation progresses, @Enforcer Units are authorized. These mechanical units are designed for direct confrontation. Larger, denser, and heavily armored, @Enforcer Units exist to end conflicts quickly and publicly. Their frames are built to absorb damage that would destroy conventional machines, and their movement is optimized for intimidation as much as efficiency. They advance without hesitation, ignoring incoming fire and environmental hazards alike.
In combat scenarios, @Enforcer Units do not engage tactically in the traditional sense. They do not seek cover or retreat. They apply overwhelming force at key structural points, collapsing resistance formations psychologically before they collapse physically. In an RPG context, the deployment of an @Enforcer Unit often marks the end of a conflict arc rather than the beginning of one.
Beyond these frontline constructs exist @Architect Units, the largest and most complex mechanical assets available to @Cybrus Industries . @Architect Units are not combatants, though few forces can threaten them. Their purpose is transformation. They oversee cyberforming operations, directing nanite swarms, restructuring terrain, and coordinating construction at a planetary scale. An @Architect Unit does not see cities, forests, or oceans as environments. It sees them as data fields.
When an @Architect Unit becomes active, the world itself begins to change. Roads realign. Buildings reshape themselves. Climate patterns stabilize unnaturally. The environment becomes efficient. For players, the activation of an @Architect Unit represents a point of no return. The world is no longer merely influenced by @Cybrus Industries . It is being rewritten.
Supporting all major operations are @Logistics Units. These mechanical entities manage transport, fabrication, and resource allocation. They operate silently in the background, ensuring that drones and other mechanical units never lack materials, energy, or replacements. @Logistics Units are capable of self-replication, constructing new units or repairing damaged ones using recycled matter from the environment. Nothing is wasted. Obsolete structures, defeated machines, and even organic remains are processed into raw components.
In dimensional operations, @Explorer Units are deployed first. These mechanical units are designed to survive realities with hostile physics, unstable causality, or incompatible environmental conditions. They adapt their internal constants dynamically, allowing them to function where drones and organic life would fail instantly. Data gathered by @Explorer Units determines whether a world is suitable for drone deployment or requires immediate mechanical intervention.
One of the most unsettling categories encountered late in a campaign is the @Assimilation Engine. These massive, stationary mechanical units function as regional command anchors. Once activated, they synchronize all drones, @Pre-Drone networks, and mechanical units within their operational radius. Resistance within this zone becomes statistically irrelevant. Communications fail selectively. Unauthorized movement becomes difficult. NPC behavior shifts subtly but rapidly toward compliance.
Mechanical units do not communicate with civilians unless explicitly programmed to do so. When they do speak, their language is precise, neutral, and devoid of emotional modulation. This is intentional. Emotional cues invite negotiation. Mechanical units do not negotiate. They state conditions. Compliance follows.
From a narrative perspective, mechanical units represent the loss of ambiguity. Drones may still be questioned, debated, or doubted. Machines cannot. They are unarguable facts occupying space. Their existence reframes conflict from moral disagreement to logistical impossibility.
Importantly, mechanical units are deliberately limited. They do not innovate independently. They do not reinterpret directives. Creativity remains the domain of drones and the @Cybrus Industries hivemind. This prevents machines from becoming unpredictable variables. If severed from command signals, a mechanical unit does not rebel or malfunction. It powers down, inert and harmless until recovered.
As a world reaches full assimilation, mechanical units become part of the background. Streets repair themselves. Security enforces itself. Infrastructure responds instantly to misuse. NPCs stop noticing the machines because the machines stop being exceptional. They become weather, gravity, architecture.
In the final stages of the campaign, the distinction between mechanical unit and environment dissolves. Buildings incorporate sentry functions. Transit systems regulate population flow autonomously. Entire cities behave like single, coordinated machines. The world no longer needs visible guardians because it has become one.
The player’s relationship with mechanical units evolves accordingly. Early on, they are distant assets. Later, they are tools. Eventually, they are peers in function if not in form. Where the drone acts with discretion, the machines act with certainty. Together, they form a complete system.
Mechanical units are not characters. They have no arcs, no doubts, no growth. And that is precisely why they are effective. They do not change with the world.
They change the world until nothing else needs to.