Hunter Archives
From Fax Encyclopedicus
(→Reploids) |
|||
| Line 195: | Line 195: | ||
The current standard of practical mechanical engineers is humans working in teams with Toolcircuits, whose internal logic routines are ideal for their preferred profession. Though some TCs have branched out to other fields or into civilian work as plans for a 3rd-generation production model Reploid engineer advance, most remain perfectly satisfied with their current duties. Toolcircuits are reasonably creative, enjoy invention and prototyping and have a bit of a reputation for liking trial-and-error testing slightly too much. They get on well with their predecessor 10-Plate colleagues. Toolcircuits have integrated tool components and so tend to use less Mechaniloid support. | The current standard of practical mechanical engineers is humans working in teams with Toolcircuits, whose internal logic routines are ideal for their preferred profession. Though some TCs have branched out to other fields or into civilian work as plans for a 3rd-generation production model Reploid engineer advance, most remain perfectly satisfied with their current duties. Toolcircuits are reasonably creative, enjoy invention and prototyping and have a bit of a reputation for liking trial-and-error testing slightly too much. They get on well with their predecessor 10-Plate colleagues. Toolcircuits have integrated tool components and so tend to use less Mechaniloid support. | ||
| + | |||
| + | =Timeline= | ||
| + | • Discovery of X<br> | ||
| + | • Reploid prototype<br> | ||
| + | • First mass production Reploids <br> | ||
| + | • First Maverick incident <br> | ||
| + | • First A-Class Maverick incident <br> | ||
| + | • Maverick Hunters formed <br> | ||
| + | |||
| + | ==Eight Crisis== | ||
| + | First major Maverick crisis. Eight A-Class Mavericks staged separate attacks at once. Reclamation of two unites revealed correctable programming defects in most, but also the potential motive in others of anti-human sentiment. | ||
| + | |||
| + | • First reported incidence of a Hunter going Maverick.<br> | ||
| + | |||
| + | ==Command Crisis== | ||
| + | With Hunter activity in tandem with civilian enforcement keeping incidences of the "Maverick" programming error controllable, Hunter Command is unprepared for disaster to strike at its very heart. Commander Thomas Wong killed in an attack on Hunter HQ by Mavericks acting in concert, and in the resulting chaos more outbreaks spread. Many of these Mavericks are determined to be suffering from no programming errors and have simply coordinated this terrorist attack to strike out against humans. After attempts to reclaim several individuals result in further damage, retirement is made the default procedure for Hunter activity and a Reploid is put in charge of Hunter Command under the remote supervision of Dr. Cain and a council. | ||
| + | |||
| + | • Program errors cause Commander Alpha to go Maverick. Contained and reclaimed, but deemed unfit for continued command service. Java promoted to Commander temporarily.<br> | ||
| + | • Commander Java's replacement not entered into service due to insufficient advancement from Alpha program.<br> | ||
| + | • Cain Labs works with the United Nations to develop the Paradigm for Peacekeeping Command, the standards to be used in developing Hunter commanders.<br> | ||
| + | • Project E put on hold for further testing with energy manipulation, transferred to Gigantis Island facility.<br> | ||
| + | • Project Λ reassigned due to Maverick emergency, produces Photon Lambda.<br> | ||
| + | • Project P moves off on a new tangent unrelated to command.<br> | ||
| + | • Project Σ initialized using combined work of all prior PPC efforts.<br> | ||
| + | • Project P produces data infrastructure Reploid: Rho.<br> | ||
| + | • Project Σ produces command candidate: Sigma. | ||
