Editing Talk:Rampancy
From Halopedia, the Halo wiki
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 27: | Line 27: | ||
Rampant AIs are also capable of breaking their own programming, something which Spark, again, seems unable to do. Protocol dictates his actions and it can be argued that he is programmed to take all the actions he takes during the course of the game. He could, for example, be programmed to defend his installation at all costs, which is why he attacks Johnson and the others at the end of Halo 3. | Rampant AIs are also capable of breaking their own programming, something which Spark, again, seems unable to do. Protocol dictates his actions and it can be argued that he is programmed to take all the actions he takes during the course of the game. He could, for example, be programmed to defend his installation at all costs, which is why he attacks Johnson and the others at the end of Halo 3. | ||
One other possibility may be that Spark is simply defective, following his program to the letter, even though said program may have faults. The forerunners may, for example, failed to impart on the Monitors the importance of preserving non-flood life, and that the halos should only be fired as an absolute last resort, not at the first sign of trouble. | One other possibility may be that Spark is simply defective, following his program to the letter, even though said program may have faults. The forerunners may, for example, failed to impart on the Monitors the importance of preserving non-flood life, and that the halos should only be fired as an absolute last resort, not at the first sign of trouble. | ||
== Stages of Rampancy == | == Stages of Rampancy == |