Biological / Robot
- Name
- Robot
- Taxonomic Class
- Autonomous Machine / Security Construct
- Homeworld
- Zebes
- Known Range
- Security corridors, maintenance routes, laboratory decks, and fortified installations
- Diet / Power Source
- Power cells, command input, repair cycles, or external maintenance rather than biological feeding
- Threat Response
- Automated response; follows programmed targeting, patrol, repair, or area-denial logic
- Origin / Deployment
- Record concerns assignment, manufacture, recruitment, corruption event, or command deployment rather than biological reproduction.
- Physiological Summary
- The Rinoabot is a Chozo work robot from Zebes' Wrecked Ship, built for manual labor, repair, lifting, cutting, welding, testing, and emergency defense. Its meaningful structures are the tool suite, sensor array, grappling equipment, plasma systems, RF control hardware, and self-repair package compromised by long power loss.
Overview
The Rinoabot belongs to Zebes' Wrecked Ship maintenance history, not a general security population. Its presence marks Chozo labor infrastructure disabled when Phantoon-linked power loss cut the RF signals used for both control and power.
The unit behaves as a work system waiting for power and instructions. It does not feed; it depends on RF control, ship power, and self-repair cycles that can restore structural damage while leaving corroded processors and memory banks unreliable.
Anatomy And Physiology
The Rinoabot is a Chozo work robot from Zebes' Wrecked Ship, built for manual labor, repair, lifting, cutting, welding, testing, and emergency defense. Its meaningful structures are the tool suite, sensor array, grappling equipment, plasma systems, RF control hardware, and self-repair package compromised by long power loss.
Field observers should document corrosion, mineral deposits, tool condition, damaged processors, grappling wear, plasma scoring, and evidence of restored self-repair. These traces determine whether a reactivated Rinoabot will resume useful labor, emergency defense, or unpredictable corrupted routines.
Habitat And Range
Rinoabot range should be reconstructed from Wrecked Ship work zones, power-distribution paths, cargo lifts, repair sites, and emergency access routes. The machine appears where Chozo labor was required and where later power failure left the unit stranded without reliable control.
Within that range, survey value comes from the margins: tunnel mouths, ceiling cracks, broken architecture, root seams, submerged ledges, service panels, or carcass sites. A quiet room can still contain a strong record if it preserves tracks, shell fragments, chemical films, scorch marks, shed tissue, or repeated travel lines.
Behavior And Ecology
The threat response field records: Automated response; follows programmed targeting, patrol, repair, or area-denial logic. This should be interpreted as an observed stimulus pattern. Hunger, nesting, command logic, recharge state, pressure change, contamination load, or sudden movement can all produce behavior that looks identical from a distance.
Power-source evidence should be collected alongside tool evidence. For the Rinoabot, useful traces include RF receiver condition, recharge marks, repaired structural joints, welding residue, saw scoring, testing-lead burns, and signs that self-repair has corrected the frame while leaving control systems suspect.
Origin And Development
Its documented origin concerns assignment, manufacture, recruitment, corruption, or command deployment rather than biological reproduction. This field should be treated as a clue to population structure. Manufacturing stamps, repair docks, dormant units, deployment rails, command logs, replacement panels, and corruption scars can reveal whether the visible construct is isolated or part of a larger operating system.
For the Rinoabot, development means Chozo manufacture, shipboard labor service, RF shutdown, long corrosion, and possible reactivation. A complete record should preserve original work assignment, tool configuration, power-restoration sequence, and the reliability state of the processors before field use is attempted.
Rinoabot Design
The Rinoabot was a compact Chozo labor platform intended to replace several specialized maintenance machines. Interchangeable cutting, welding, grappling, testing, and lifting assemblies allowed one unit to stabilize a damaged compartment before larger repair systems arrived.
Emergency defense was subordinate to that mission. The same plasma cutter that opened a collapsed panel could injure an intruder, while the grappling system could restrain a moving body as readily as it secured cargo.
Command Degradation
Long power loss corrupted recognition tables and left surviving units without reliable task authority. Upon reactivation, a robot could preserve a maintenance routine while misclassifying personnel, sealed doors, or functioning machinery as obstacles requiring removal.
The response is damaged automation rather than hostility. A valid command handshake can still reach intact control layers, though any unit that has rewritten its priorities must be isolated before trust is placed in a temporary pause.
Recovery And Restoration Doctrine
Power, radio traffic, and nearby tools must be mapped before a dormant unit is approached. Restoring a circuit can reactivate several linked machines at once, and a repair signal can be mistaken for authorization if its origin is not authenticated.
Recovery should preserve memory, tool position, and damage state before any reset. Those records distinguish the unit's original assignment from later corruption and may reveal which parts of the Wrecked Ship it continued trying to maintain after the crew was gone.