Editing Talk:343 Guilty Spark

From Halopedia, the Halo wiki

You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

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 10: Line 10:


::::I've been thinking about this for some time, and I agree. However, Johnson's entry in the ''Essential Visual Guide'' states Guilty Spark ''was'' rampant, so I'm not exactly sure what to make of it.--[[User:Jugus|<font color="MidnightBlue"><b>Jugus</b></font>]] <small>([[User talk:Jugus|<font color="Gray">Talk</font>]] | [[Special:Contributions/Jugus|<font color="Gray">Contribs</font>]])</small> 09:10, 4 September 2011 (EDT)
::::I've been thinking about this for some time, and I agree. However, Johnson's entry in the ''Essential Visual Guide'' states Guilty Spark ''was'' rampant, so I'm not exactly sure what to make of it.--[[User:Jugus|<font color="MidnightBlue"><b>Jugus</b></font>]] <small>([[User talk:Jugus|<font color="Gray">Talk</font>]] | [[Special:Contributions/Jugus|<font color="Gray">Contribs</font>]])</small> 09:10, 4 September 2011 (EDT)
:::::Maybe Spark was programmed to respond in a slightly nicer way, instead of (trying to) outright killing them. [[User:FatalSnipe117|<span style="color:green">'''pestilence'''</span>]] [[Special:Contributions/FatalSnipe117|<span style="color:green">'''Phil'''</span>]], ''[[User talk:FatalSnipe117|<span style="color:green">'''pestilence!'''</span>]]'' 10:16, 4 September 2011 (EDT)


A quote that I made from a really long time ago: '''''"343 Guilty Spark is the Monitor of Installation 04 and was created by the Forerunners! After the Forerunners were assaulted by the Flood they created the Halo Array to destroy the Flood.  The Forerunners set up Monitors to oversee the Halo Installations and to control Sentinels incase of a Flood out brake. To insure that the Halo's wouldn't be destroyed very easily is that they only provided the Monitors with enough information to maintain the Halo installations. And if they were to fall into the hands of the Gravemind they would not have the location of the other installations. And to help these Monitors if they fell into the Gravemind they were programed to stop the Flood at all costs. And they also had a protocol that stated that if even a tiny wire on the ring got a tiny bit damaged the Monitor was to send at least 12 Constructors to examine, repair, see what caused the problem, send it back to a more intelligent computer, then that computer must type an at least 1,000 page report on it, then send that to a higher up Computer, then that computer analyzes it and fixes errors adds things and so forth, then it gets sent to a higher computer, then a higher one, then it gets sent to the Monitor of that Installation. The Monitor then examines it, then right  a "simple" program about it(this simple program is so advanced it would take 500 normal computers to barely process it). It then sends it out to the Sentinel Constructor Factories to implement in all future Sentinels so they would know about this. The Monitor also sends all knowledge of this incident to the Knowing. They would also destroy every Flood Spore in an area. And if they didn't account for every microscopic Flood Spore then that whole area was destroyed.  And another thing as I said above is that the Halo rings must be at perfect condition at all times in case of a Flood out brake.  And the Monitor will do anything to make sure that the ring is always ready to fire. One particular example accord on Installation 08 when Avery Junior Johnson attempted to activate a partially constructed Halo. The Monitor of that Installation 343 Guilty Spark witnessed this. And 343 Guilty Spark couldn't let this happen. Because 343 Guilty Spark knew that it could destroy the Ark and then there would be nothing to make large-scale repairments to the Installations. And that would go against protocol and eventually  all the Installations will need large-scale repaiments and there would be nothing to make the replacements! And then if there was a Flood out-brake the whole UNIVERSE could become consumed! So in order to preserve the Ark and the whole Universe 343 Guilty Spark attacked Avery Junior Johnson and successfully stopped this threat that could destroy the whole Universe and put his makers to shame. Unfortunately, soon afterwards, 343 Guilty was "deactivated". The Ring was forced to fire and the Ring was torn apart. The current status of the Ark is unknown, there is a 100% chance that the ring is severely damaged."''''' Vegerot goes RAWR!  [[User:Vegerot|<span style="color:midnightblue; font-weight:bold">Vegerot</span>]] ([[User talk:Vegerot|<span style="color:grey">talk</span>]])  13:11, 4 September 2011 (EDT)
A quote that I made from a really long time ago: '''''"343 Guilty Spark is the Monitor of Installation 04 and was created by the Forerunners! After the Forerunners were assaulted by the Flood they created the Halo Array to destroy the Flood.  The Forerunners set up Monitors to oversee the Halo Installations and to control Sentinels incase of a Flood out brake. To insure that the Halo's wouldn't be destroyed very easily is that they only provided the Monitors with enough information to maintain the Halo installations. And if they were to fall into the hands of the Gravemind they would not have the location of the other installations. And to help these Monitors if they fell into the Gravemind they were programed to stop the Flood at all costs. And they also had a protocol that stated that if even a tiny wire on the ring got a tiny bit damaged the Monitor was to send at least 12 Constructors to examine, repair, see what caused the problem, send it back to a more intelligent computer, then that computer must type an at least 1,000 page report on it, then send that to a higher up Computer, then that computer analyzes it and fixes errors adds things and so forth, then it gets sent to a higher computer, then a higher one, then it gets sent to the Monitor of that Installation. The Monitor then examines it, then right  a "simple" program about it(this simple program is so advanced it would take 500 normal computers to barely process it). It then sends it out to the Sentinel Constructor Factories to implement in all future Sentinels so they would know about this. The Monitor also sends all knowledge of this incident to the Knowing. They would also destroy every Flood Spore in an area. And if they didn't account for every microscopic Flood Spore then that whole area was destroyed.  And another thing as I said above is that the Halo rings must be at perfect condition at all times in case of a Flood out brake.  And the Monitor will do anything to make sure that the ring is always ready to fire. One particular example accord on Installation 08 when Avery Junior Johnson attempted to activate a partially constructed Halo. The Monitor of that Installation 343 Guilty Spark witnessed this. And 343 Guilty Spark couldn't let this happen. Because 343 Guilty Spark knew that it could destroy the Ark and then there would be nothing to make large-scale repairments to the Installations. And that would go against protocol and eventually  all the Installations will need large-scale repaiments and there would be nothing to make the replacements! And then if there was a Flood out-brake the whole UNIVERSE could become consumed! So in order to preserve the Ark and the whole Universe 343 Guilty Spark attacked Avery Junior Johnson and successfully stopped this threat that could destroy the whole Universe and put his makers to shame. Unfortunately, soon afterwards, 343 Guilty was "deactivated". The Ring was forced to fire and the Ring was torn apart. The current status of the Ark is unknown, there is a 100% chance that the ring is severely damaged."''''' Vegerot goes RAWR!  [[User:Vegerot|<span style="color:midnightblue; font-weight:bold">Vegerot</span>]] ([[User talk:Vegerot|<span style="color:grey">talk</span>]])  13:11, 4 September 2011 (EDT)

Please note that all contributions to Halopedia are considered to be released under the Attribution-ShareAlike 3.0 Unported license (see Halopedia:Copyrights for details). If you don't want your writing to be edited mercilessly and redistributed at will, then don't submit it here. You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

Cancel Editing help (opens in new window)

To view or search uploaded images go to the list of images. Uploads and deletions are also logged in the upload log. For help including images on a page see Help:Images. For a sound file, use this code: [[Media:File.ogg]].

Do not copy text from other websites without permission. It will be deleted.