Loading...
Replicated Entities (RepEnt) - Version 8 vs Version 9
Apr 25, 2026, 11:38 PM
Initial article on Replicated Entities (RepEnt), the player-controlled disposable clones at the centre of Fragmentary Order's gameplay loop.
Apr 25, 2026, 11:39 PM
Initial article on Replicated Entities (RepEnt), the player-controlled disposable clones at the centre of Fragmentary Order's gameplay loop.
11Replicated Entities, abbreviated RepEnt, are the disposable clone soldiers players remotely operate in Fragmentary Order. The player is not the clone. The player is a Core Era citizen logged in from a secure bunker, projecting their presence into a hostile zone through a body that is built to be expended.2233Quick Reference4455FieldDetailOperatorCore Era citizen acting as a controllerOperation SiteSecure bunker, away from the combat zoneDeployed ToContested zones across the Solar SystemCombat TypePlayer versus player between human-controlled clonesLoss ModelDisposable; loss is built into the contract economyFrameworkOperates inside the CORIE Framework66The Player's Frame7788The player's seat in the fiction is a chair in a bunker. From there, a Core Era citizen logs into a RepEnt and walks it into a contested zone they would never survive in person. The clone moves where the controller tells it to move and fires the weapon the controller picks; the controller's body stays safe.991010The studio frames this as freelance contract labour: citizens accept deployments the way other workers accept shifts, with credits and reputation on the line each time they boot a RepEnt. See Setting: The Year 2251 for context.11111212Disposable by Design13131414RepEnts are expendable by intent. A clone that does not extract is gone with whatever gear it was carrying, and the controller continues from the bunker without lasting bodily harm; the credit ledger takes the hit instead.15151616That choice shapes the risk and reward loop. Bringing better gear into a contested zone raises the prize if the RepEnt extracts and raises the bill if it does not. Every clone in the field is also something a rival can take off the controller's hands.17171818PvP Combat Model19192020Combat is between human-controlled clones, not players versus computer-driven aliens. Every RepEnt on the map represents a real controller making real decisions, so encounters are unpredictable. The studio has not committed to a fixed match format, team size, or per-zone player count. For the wider loop see Gameplay Overview; for the size and variety of zones see Maps and Scale.21212222Why It Matters in CORIE23232424RepEnt deployments are how a player participates in the risk economy run by the CORIE Framework. A clone in a contested zone is a unit of risk in motion. Progression therefore tracks more than kills and loot: it tracks how CORIE rates the work, which factions pay for what kind of pressure, and how the credit flow shifts as the corporate balance changes. The RepEnt is the tool; CORIE is the market.25252626Unconfirmed Details27272828Significant aspects of how RepEnts work have not been disclosed:292930-Origin of the clones. Genetic source and production method are unconfirmed.Consciousness and memory transfer. The fiction for how a controller's input reaches the clone has not been explained.Named RepEnt models, classes, or chassis variants.RepEnt-specific equipment systems. Whether gear, implants, or augments are tied to the clone or to the controller's account is unclear.Customisation and gender options for the clone.Penalty model on loss. The exact cost in credits, reputation, or stored gear when a RepEnt fails to extract is unpublished.30+Origin of the clones. Genetic source and production method are unconfirmed.Consciousness and memory transfer. The fiction for how a controller's input reaches the clone has not been explained.Named RepEnt models, classes, or chassis variants.Equipment systems. Whether gear, implants, or augments are tied to the clone or the controller's account is unclear.Customisation and gender options for the clone.Penalty model on loss. The exact cost in credits, reputation, or stored gear when a RepEnt fails to extract is unpublished.