A Life More Synthetic; Machine Saboteur

 In the Starfall Galaxy, Machine Saboteurs are Androids whose bodies, minds, or both were purpose‑built as anti‑machine weapons. Vaelen skirmish doctrines and later Concordance counter‑insurgency programs needed something that could get close to hostile tech—combat drones, war mechs, rogue AIs’ bodies—and tear them down from the inside while looking like “just another synth.”

Their perspective cores carry specialized counter‑OS libraries, intrusion heuristics, and combat subroutines tuned to recognize vulnerable seams in synthetic armor, antenna clusters, coolant lines, and processor housings. A solid hit isn’t just damage: it’s a forced reboot of targeting systems, a stutter in actuator timing, a momentary scramble of sensor fusion. Where others see “robot,” a Machine Saboteur sees debug logs and failure points.

The glitching effect isn’t purely digital. Many tech bodies in Starfall are hybrid—fluid‑cooled, mana‑reactive, or partially Rift‑infused. A Machine Saboteur’s strikes introduce destabilizing variables at every level: a blade driven at the perfect angle to crack a mana reservoir, a round timed to hit mid‑oscillation in a Rift‑lens, a shock baton tuned to resonate with exocortex frequencies instead of muscle.

Concordance strike cells deploy these Androids as “breaker frames” against enemy synths and autonomous weapons. Inner Sphere corps and the Commission train their own saboteurs to shut down Concordance warframes, rogue industrial swarms, and, quietly, rebellious worker collectives whose chassis make conventional crowd‑control risky.

Machine Saboteur Feat 5

You were created to fight other synthetic creatures, and your attacks unleash destructive nanites that disrupt their systems. When you roll a critical hit against a creature with the tech trait, the target becomes glitching 1.


Non‑Combat Applications

  • Controlled Shutdowns: Machine Saboteurs are invaluable in non‑lethal tech neutralization: disabling rogue security drones, calming berserk mining rigs, or knocking malfunctioning exosuits offline without total destruction

  • Exploit Testing & QA: Guilds and megacorps hire them to probe new combat frames, defense turrets, and AI shells for failure points—weaponizing their knack for finding “where it breaks first” into a form of brutal quality assurance.

  • Covert Tech Denial: In espionage, they act as “accidental” failure vectors—subtly glitching surveillance systems, gate controls, and autonomous loaders during routine contact so that, days later, the target’s logistics “just happen” to collapse.


Societal Impact

Machine Saboteurs occupy a uniquely fraught niche in Starfall politics. To the Automaton Concordance, they are necessary specialists: proof that synthetic life must be able to defend itself not only from organics, but from other machines twisted to organic purposes. Concordance propaganda frames them as “circuit wardens”, protecting synthkind from parasitic code, rogue drones, and enslaving architectures.

But inside the Concordance, there is unease. Many older synths remember that the first Machine Saboteur‑type frames were designed by the Vaelen to hunt down rebellious Androids, not protect them. The same instinct that can glitch an enemy mech can, in theory, glitch a free Android’s chassis—reviving old fears of “kill‑switch cousins” built into their own ranks.

In the Inner Sphere, Machine Saboteurs are treated as both asset and threat. Commission war planners see them as ideal tools against Concordance incursion forces and unsanctioned tech cults. At the same time, corporate security memos quietly flag any Android with known sabotage capabilities as a category‑red insider risk—someone who could, with a few well‑placed hits, send an entire factory’s automation into cascading failure.

Among independents, the reputation is more personal. Freeport crews and Rift‑burg scavengers call them “gear‑killers” or “ghost mechanics” and keep them close when venturing into drone‑haunted wrecks, but keep a wary eye on them back at dock. When your entire livelihood depends on a refurbished mech, it’s hard to fully trust someone who can crash it with a punch.


Adventure Hooks

  • The Glitch Plague: A Concordance convoy reports that its escort drones and warframes are randomly glitching and seizing mid‑battle, even without visible hits. Evidence suggests a Machine Saboteur virus—combat subroutines modeled on the feat’s logic, now propagating memetically through routine maintenance updates. The party must track its origin before every tech‑trait unit in the region becomes unreliable.

  • Factory of “Accidents”: On a Commission‑run ecumenopolis, industrial accidents involving autonomous machinery spike to catastrophic levels. A whistleblower claims a corporate black ops team of Machine Saboteurs is engineering failures to justify replacing unionized organic labor with “safer, fully synthetic lines.” The PCs must infiltrate the sabotage cell, expose the plot, or decide whether to flip these saboteurs to a more righteous target.

  • The Reluctant Breaker: An NPC Android saboteur was built by the Vaelen as a hunter of rebellious synths, then later liberated in the Concordant Rebellion. Now, their glitching touch is both trauma and asset. When a Rift‑mad AI seizes control of a Metronome‑linked defense network, they are the only one who can safely close in and shut the machines down from within—but doing so risks reawakening deeply buried kill protocols in their own core. The party must support, stabilize, or find another way.


Machine Saboteur, in Starfall, is the embodiment of a hard truth: in a galaxy ruled by machines, someone has to know how to break them, and that someone will always be feared most by those who depend on machinery to stay in power.

Comments