Talk:Fall of Reach

Merge with "Raid of Reach"
-- Forerunner 15:41, July 30, 2010 (UTC)

Dates retconned?
It seems we have a new, quite large retcon in our hands. According to the ONI Memorial in ODST, the dates for the battle are radically different from what we're used to. Now, that could be chalked up to error or the fact the plaque is just an easter egg, but now, we have new evidence supporting the change: the newest live action trailer shows the date "July 23rd 2552", which wouldn't make any sense in the original context (that is, if the battle began on August 30th). Considering how the date for the beginning of the battle was July 25th in the ONI plaque, the 23rd is probably the day before the invasion. That still leaves one day in between, but that may be the when the Covenant "advance force" arrived and the actual, full-on invasion hadn't yet began.

The new version is also supported by the note in the game's packaging, read by Brian Jarrard in the Reach unpacking video. "You are in possession of the most complete and accurate account that anyone has been able to assemble from the SPECWAR/GroupTHREE/Noble actions during the final weeks before the Covenant glassed Reach."

"Final weeks" wouldn't make a whole lot of sense were the game follow the original story, as most of the planet was glassed the day it was invaded. It seems they changed it to allow for a longer campaign (I saw this coming, really; if it were like the original, the campaign would've lasted for only a couple of hours). In light of this obvious retcon, should we change the page accordingly? --Jugus (Talk  | Contribs ) 10:39, August 18, 2010 (UTC)


 * Hm, it seems that way alright. However, that would be a very large retcon indeed; the dates of Halo: Combat Evolved, Halo: First Strike, and indeed most of the dates in The Fall of Reach, including the Battle of Sigma Octanus IV and the entire time line of the Fall of Reach, are all dependent on when the Fall of Reach took place. For instance, the Battle of Sigma Octanus IV took place on July 17th-18th, which would place it a mere five days before the Fall of Reach if this is indeed a retcon; which would make little sense considering the time it would take the Iroquois to make it back to Reach, and the subsequent events such as the recalling of the Spartans and so on. This would also apply to the Battle of Installation 04; where it is explicitly stated that it took three weeks for the Autumn to get to Halo, and that the battle was in late September. And while I won't go into First Strike, I'm sure you know the magnitude of inconsistencies that would arise there, with the Slipspace time anomaly and all. So, my point is, that we should not jump to the conclusion of a date retcon until we are absolutely sure that this is the case; i.e. when Reach comes out. - Black Mesa.jpg Halo-343   ( Talk )   ( Contribs )   ( Edits )  11:09, August 18, 2010 (UTC)


 * Yep, I'm aware of this - However, it's possible that in this new timeline, the invasion was more gradual (somewhat akin to the Battle of Earth), with smaller battle groups arriving over the span of a month. The final fleet that overwhelmed and glassed Reach would arrive on August 30th like it did before. From then on, the events would transpire much like they did in FS. That's my guess anyways. The events in The Fall of Reach may have happened on the dates they did in the book, including the Iroquois arriving at Reach and John being debriefed, and later receiving his armor, only with the battle going on all that time. The PoA would jump away on the last day of the battle (August 30th), when the actual glassing fleet arrived and the last of the UNSC's defenses were destroyed.


 * That still leaves a lot of inconsistencies with the book, including the Spartans' mission to capture the Prophet: why would they be sent away when they would all be needed on Reach more than ever? Although it could be understood as an act of desperation: they already know Reach is going to fall, and they send the Spartans to take the fight to the Covenant instead of sacrificing them in a vain effort to defend Reach. Still, that doesn't explain why the PoA turns back and the Spartans are deployed to defend the generators, but it seems to be the only way to make any sense out of it. But I agree that we should keep it the way it is until we get more information and a solid confirmation on the retcon. --Jugus (Talk  | Contribs ) 11:33, August 18, 2010 (UTC)


 * The first paragraph of your comment reflects what I thought of the retconned dates. *slashes own comment*
 * Perhaps capturing a Prophet hostage would buy the UNSC some time as to delaying the inevitable fall of Reach? Like a bargaining chip, perhaps? It makes sense, seeing that it caused quite an uproar when John killed Regret on Delta Halo. Perhaps Reach holds more secret than what we know so far? So many mysteries.... -  5 əb'7 aŋk (7alk ) 18:40, August 18, 2010 (UTC)


 * I'm not sure it's a retcon. It seems to me that the planet the Iroquious (and thus the probe) went to just happened to be one the Covenant already knew about. Besides, all we know of the battle is that the components of the Epsilon Eridani fleet defending Reach were eliminated within (I think) 4-6 hours on 30 August. They gradually begin to bombard the planet, finishing (with the exception of Menachite mountain) some time before 15/16 September (the former or the latter being the day the Ascendant Justice reached Reach - the latter being the "revised calendar date" some time after rescuing Halsey, where they work out the correct date). From what I recall, they began glassing from the poles, leaving up to eight days of fighting with surviving UNSC groundforces. I don't remember much about the novel, but I'm sure the PoA simply picked up an emergency transmission addressed to all ships - if you were being attacked, would you personally message each ship individually?-- Forerunner 12:04, August 18, 2010 (UTC)


 * Uh, I'm not sure you're fully aware of what we're discussing. We're talking about Reach potentially retconning August 30th to July 23rd, I'm not quite sure what you're talking about. - Black Mesa.jpg Halo-343   ( Talk )   ( Contribs )   ( Edits )  12:10, August 18, 2010 (UTC)


 * It's probably an error. I was saying that if this isn't an error, then the probe attached to the Iroqious obviously wasn't the first to find Reach - perhaps the Skirmishers were sent ahead to look for information regarding other worlds (ie. Earth) before the humans got a chance to wipe the systems. Yeah - it probably meant August instead of July, though it wouldn't mess with the timeline if it was July.-- 12:37, August 18, 2010 (UTC)


 * No they said they were going to do something that would quote "take issues with" here but in all honestly they've truly screwed the canon up, how the hell does the events in fall of reach still happen if the dates are all wrong. They've essentially taken all the books and flung them out the door. Not just in terms of the events of the game but the events of the books themselves. It's hilarious when you read the last part. Durandal-217 16:11, August 18, 2010 (UTC)


 * Remember when ODST and Halo Wars trailers were released. Many people looked at the limited content and came to the conclusion that they were non-canon. It turned out that as they obviously hadn't played the game, they couldn't see that it really was canon (Flood in Halo Wars; Regret not destroying New Mombasa, etc.). For all we know, Winter Contingency actually takes place on 23 July, while the rest is on 30-31 August.-- Forerunner 17:35, August 18, 2010 (UTC)


 * "For all we know, Winter Contingency actually takes place on 23 July, while the rest is on 30-31 August." That makes no sense. Durandal-217 18:22, August 18, 2010 (UTC)


 * I thought Jugus has already pointed out the obvious approach taken by Bungie to resolve this issue; they had stated that the Fall of Reach occurred earlier than what we already know in Halo 3: ODST through the ONI Memorials. Perhaps those who read the novel took the event too seriously... Maybe the Fall of Reach did occur earlier on in early August after the Iriquois returned to Reach to deliver its report of Octanus. Somewhere during the return, several Covenant ships traced and attacked the planet (which is when the game comes in. It also explains why there weren't many "lightshows" in the Campaign trailer over Reach) but the UNSC on Reach manage to repel the early Covenant forces until they encountered the 700 Covenant ships (which is covered in the novel). Am I wrong? -  5 əb'7 aŋk (7alk ) 18:33, August 18, 2010 (UTC)


 * The way I see it, in the new timeline, the actual battle for Reach itself takes place between July 25 and August 29. At first, the Covenant forces come in with smaller groups. On August 30, things happen pretty much like in the novel, except that the Covenant are already on Reach, they just come in with a bigger force, wipe the rest of the UNSC resistance out and glass Reach. The PoA escapes and Red Team goes underground. As for the events that happen in between, like John being debriefed at Camp Hathcock, the briefing for the mission to capture the Prophet in the auditorium and John receiving his Mark V armor, we'll just have to assume the battle for Reach is taking place all that time. Unless, of course, the UNSC managed to destroy the initial Covenant force and it took some time for them to mobilize another one. In that case, there would be a gap in the fighting much like the one that was originally assumed to be between the "first" and "second" battles of Earth.


 * Judging by the dates shown in the memorial, I'm still fairly certain Halo: Reach will end on August 30 and the time anomaly won't be included. The time anomaly doesn't even affect anything else than the people at Installation 04, causing them to go back in time a couple of weeks when they return to Reach. Events before that shouldn't be affected by the crystal. --Jugus (Talk  | <font color="Gray">Contribs ) 18:45, August 18, 2010 (UTC)


 * Exactly how I view it.- <font face="Century Gothic"> <font color="#FF4F00">5 əb<font color="#FF4F00">'7 aŋk (<font color="#FF4F00">7alk ) 18:49, August 18, 2010 (UTC)


 * So if the Covenant are already on Reach by August 30th explain how NOBODY KNOWS ABOUT IT. It just makes no sense, it's the most moronic thing you could ever come up with in a story, it is loony-toons level ridiculousness. If the Covenant invaded reach on July 25th it would been known throughout the military, no one would be that stupid enough to risk millions of lives on "we need to keep this a secret and build up our military resources". They would have already evacuated the entire planet by that point and nobody would have been that surprised by the real assault by the Covenant as they were in FoR. Durandal-217 19:00, August 18, 2010 (UTC)


 * The answer is quite simple: the magic powers of retcon. Bungie decided to make the battle longer, so the idea that the invasion happened on August 30th isn't true anymore. According to the new timeline, everyone obviously knows that the Covenant are on Reach by Aug 30 since the battle has been raging for weeks; they're not surprised, except maybe about the massive size of the arriving Covenant fleet.--<font color="MidnightBlue">Jugus (<font color="Gray">Talk  | <font color="Gray">Contribs ) 19:07, August 18, 2010 (UTC)


 * Look - we know very little about the campaign and the game's plot. What we do know is that Halo: Reach takes place over a longer timeline than just 30 August, and that an advanced invasion force is there days before the Fleet of Particular Justice arrives (personally I think it was a coincidence that Iroqious led them to Reach, if the advanced force was already there). Just wait for the game to come out and we'll understand. We thought that all of Halo Wars would be on Harvest and that there was a second battle of Mombassa in which John participated in. Just wait for more information to come out before turning this into another "bungie fucked up the timeline" discussion.-- Forerunner 19:06, August 18, 2010 (UTC)


 * Also, it's obvious that it was kept secret - you're the one who's being moronic. Otherwise, nothing would happen on 25 July, let alone 23. -- Forerunner 19:06, August 18, 2010 (UTC)


 * Let's keep it civil...- <font face="Century Gothic"> <font color="#FF4F00">5 əb<font color="#FF4F00">'7 aŋk (<font color="#FF4F00">7alk ) 19:10, August 18, 2010 (UTC)


 * It just shows me that they are not serious about Halo canon anymore. You don't establish a story and stand by it for 10 years and then at the last second erase what you've stood by. That's just contradicting yourself and it makes you (bungie) look very stupid. That right there is not how you create a universe or tell a good story. What's even more depressing are the people who are willing to stand by this disgraceful move by bungie and go so far as to insult others because of it. Durandal-217 19:18, August 18, 2010 (UTC)


 * Just pointing out, Bungie didn't write The Fall of Reach. When it comes down to it, Bungie created Halo. While I respect Eric Nylund and still think he's the best Halo writer, it's Bungie's story. I don't like retcons, but complaining about it's not going to help either. And knowing Bungie, they don't just do things like this for no reason. --<font color="MidnightBlue">Jugus (<font color="Gray">Talk  | <font color="Gray">Contribs ) 19:23, August 18, 2010 (UTC)


 * To Forerunner - it was mentioned in one of the campaign previews that the full-on invasion begins just after Winter Contingency, as the UNSC starts reporting Covenant activity all over the planet through radio. So, keeping the invasion secret from July 23 (or 25) till August 30 isn't really possible. It's a retcon; we'll just have to live with it. On a related note, I'm guessing this hasn't been explained at all in the Fall of Reach reissue? That would've been the perfect chance to change the events of the book when they're retconning it anyways; from what I've heard, they hardly changed it at all. Oh well. An opportunity missed. --<font color="MidnightBlue">Jugus (<font color="Gray">Talk  | <font color="Gray">Contribs ) 19:23, August 18, 2010 (UTC)


 * I'm sure they've got a good reason, otherwise they wouldn't bother to change it. My question would be then, for now, should this article hold the "newer" information, or the old Fall of Reach date? ''Tuckerscreator' 19:25, August 18, 2010 (UTC)


 * I just think its a dishonor to not only the incredible work of Eric Nylund who is a fictional genius in his own right, but it is a dishonor to all of us who stood by Halo. We are not entitled to anything, but we support halo because of its great fiction, gameplay and multiplayer. When all we ask for is a product that continues that foundation, and what we get is a game that on the principle founding of halo (telling a good story) is ignored by throwing out all the work that Nylund, Brannon Boren and Eric S. Trautmann help bungie create is just dishonorable. I believe, or try to believe in honoring people doing incredible work, but when bungie clearly ignores that for the sake of creating what they, and only they want, It just burns my soul. Durandal-217 19:35, August 18, 2010 (UTC)


 * They're not ignoring Nylund, just adjusting. If they were ignoring Nylund, then they wouldn't have collaborated him him to create this. Changes happen, remember when Miranda Keyes's actress was changed? Best not to get too attached to it, changes happen, and who better to change it than Bungie? ''Tuckerscreator' 19:52, August 18, 2010 (UTC)


 * While I acknowledge all the points made, I just can't see it being that there was fighting on Reach weeks before August 30th. Yes, Bungie have retconned before; all minor, and none that affect the overall story. But this is huge, it completely alters the story, and I just don't see Bungie doing that, it would be self-destructive to Halo, and indeed hypocritical, seeing as Bungie have always stood by their creation, and altered it to a minimum. And so many problems arise from this; like why, as Durandal pointed out, practically no one knew that humanity's second most important planet was under Covenant attack for several weeks. ONI are good at covering up; hell, they managed to hide that humanity was on the verge of extinction right up until Earth was attacked, but there's no way they could have hidden a continuous battle on Reach from its own occupants and military defendants. Again, none of us can know exactly what the story is regarding this inconsistency until the game comes out, but if Bungie wanted to make the battle last longer, they had no need to change the dates. A large portion of Reach was left unharmed after the orbital bombardment, and we've never explicitly known how big the portion was; they could have made it as large as they wanted to have a big enough selection of locales to play in, and used all the time from August 30th until September 14th, to set Reach. I can accept an advance invasion force of a day at the most, but as I have said, there's no need for them to change it to weeks. - Black Mesa.jpg Halo-343   ( Talk )   ( Contribs )   ( Edits )  20:24, August 18, 2010 (UTC)

Well, now we know at least that Noble Actual takes place on July 24th, as per this. Winter Contingency presumably takes place later that day, unless it takes almost a day for them to reach Visegrad, which I doubt. There's always the possibility that this is only the advance force and the actual battle won't begin in a long while, but I wouldn't get my hopes up. --<font color="MidnightBlue">Jugus (<font color="Gray">Talk  | <font color="Gray">Contribs ) 12:21, August 19, 2010 (UTC)


 * Yeah, I just saw that too. I'm groping for straws here, but the only redeeming possibility I can think of, is that the next mission, or maybe the one after that takes place on August 30th a few weeks later; the advance invasion force has been taken out, and the true invasion begins on the correct date, with the UNSC ready for them. Again, I don't know, but I really hope this isn't the gigantic retcon it seems to be. - Black Mesa.jpg Halo-343   ( Talk )   ( Contribs )   ( Edits )  12:35, August 19, 2010 (UTC)


 * Agreed. It would be the single biggest retcon in the Halo universe, ever; it would basically de-canonize The Fall of Reachs chapters 24 through 37, plus require major changes in First Strike and possibly The Flood. Not a good idea at all, considering how it wouldn't even be really necessary in order to tell a different story about the events of Reach. Let's just hope it'll be the way you said; that there's actually an over a month long gap between the comm relay mission and the actual invasion. Then again, that seems unlikely considering some hints in magazine coverage. Also, it would be difficult, not to mention unreasonable, to keep the presence of Covenant forces on Reach secret from most of the population for over a month. If an advance force really arrived that early, they would've had plenty of time to evacuate the planet. --<font color="MidnightBlue">Jugus' (<font color="Gray">Talk  | <font color="Gray">Contribs ) 12:44, August 19, 2010 (UTC)

Uh...you guys do know this is a planet we're talking about? In space? Notice that the Covenant team is taking out the communications relay. The place of communications. Want to know why Reach couldn't call for help and no one outside found out about the invasion? The Covenant destroyed the communications. The planet would have been evacuated? Are you crazy? Do you understand how big a logistical operation moving 700 million people off an entire planet would be? Never mind the 350 Covenant ships in orbit. How do you even know that the population didn't know the Covenant had arrived? Maybe that gap was spent building up defenses and arming everyone.

You guys are going rabidly crazy over what a "complete disrespect and betrayal" this is to Eric Nylund and go on about what you're "owed" from Bungie...I mean, I'm not saying I disliked Nylund or his books, but how good of a game could they have gotten just from following the books' Reach storyline? It would have been a disappointment. This is supposed to be the great climactic battle of the entire war...Nylund's portrayal of it was a letdown. The space battle rocked, don't get me wrong, but the ground actions were barely worth noting. Making the Reach invasion a month long lets it be Epic. I mean, how long have we been waiting for a gigantic battle between the humans and Covenant over an entire planet? Maybe everyone should be a bit grateful for this Flayer92 21:05, August 19, 2010 (UTC)


 * They did it with Coral — and you've got a month to evacuate as many as you can, it can be done. The point you make however is completely off center, there is absolutely no logical reason to change the dates, you could have still done Reach with all this NOBLE team bullshit and not change anything. You also letting blind fanboynisum get the better of your judgement, the fact is that there was no war on Reach, their entire military fleet in orbit was destroyed in less then thirty-minutes, their ground forces stood no change against the Covenant, that's why there was no battle. There is no way they could last a month against a technologically advanced race of aliens, because all they have to do is get in their ships and bombard the planet from orbit and that the beauty of Nylund's work, He Makes Sense. Durandal-217 01:33, August 20, 2010 (UTC)


 * Not exactly; the battle wasn't that short and simplistic. During the main space battle, most of the UNSC ships were destroyed, with around fifty left, which split up to defend other areas of the planet. It is also known that the Covenant launched a massive ground invasion, a battle which still raged even after the planet was glassed. The remaining UNSC ships were slowly picked off by the Covenant until a handful of surviving were forced to limp away. The ground battle continued until September 14th, which is why this is a big deal; Bungie didn't have to retcon the battle back a whole month to make a longer battle, they had 15 days of when the ground battle canonically took place, they could have used all that time. So, while this seems to suck as of now, as we've said multiple times, let's just wait until the game comes out before making judgment and changing anything. - Black Mesa.jpg Halo-343   ( Talk )   ( Contribs )   ( Edits )  10:09, August 20, 2010 (UTC)

Theory on dates
I have a different thoery/idea that may or may not have been explained. In the first Remember Reach short, the soldiers and their superiors at HQ were only talking about Insurrectionists. We know that prior to Reach, their activity had been quite sporadic and their forces hadn't been seen in large numbers. However, what if the July 23rd, 2552 date refers to the beginning of a campaign on Reach in response to a resurgence in Insurrectionist activity in the inner colonies, whereas the August 30th date refers to the initial invasion of the Covenant's Fleet of Particular Justice? For those who've seen the footage from GamesCon 2010, you can see that the battle taking place in the background of the opening cinematic has been removed and the plot of it revolves around reports of Innie activity around a comm relay.

Adding in the dates from the Memorial at ONI Alpha Site in Halo 3: ODST, it could be surmised that the UNSC High Command didn't know of further activity from their forces on Reach, leading them to believe that the Covenant swept through the colony in just a single day. This is supported by the meeting in HIGHCOM Facility Bravo in Sydney in the first days of September where COL James Ackerson informs the Admiralty that Reach has been lost and no efforts should be undertaken to rescue survivors. In addition, First Strike proves that forces were still active on Reach in late September. Then again, this is just some batshit insane speculation. :)

Have a good one and please tell me if there's anything I missed or screwed up on!

Rawr,


 * That seems a reasonable theory. I guess none of us realized it never explicitly referred to the Covenant being the enemy on Reach for those dates. Right or wrong, it's more reassuring that it could simply be Microsoft screwing up rather than Bungie turning canon upside-down. - Black Mesa.jpg Halo-343   ( Talk )   ( Contribs )   ( Edits )  20:49, August 18, 2010 (UTC)


 * As a guess, it's as good as any. I guess it's pointless to debate this until the game is out since the discussion will go nowhere with the info we currently have - all we can do is speculate (not to say there's anything wrong with it). I'll just hold on to the hope they'll keep the retcons to a minimum and what I described above doesn't turn out to be true. --<font color="MidnightBlue">Jugus (<font color="Gray">Talk  | <font color="Gray">Contribs ) 20:57, August 18, 2010 (UTC)


 * It's a good theory, but the problem just snaps back to the retcon. If they've really changed the dates, it opens a big wound for anyone to dig in and rip out vital things. If Reach didn't fall on August 30th then who's to say that whole section in Fall of Reach ever happened, because despite that Halsey is speaking with Auntie Dot, people get the impression she is talking to/about Cortana in some form. It just becomes so much more easier for somebody with enough persuasion to completely void the novel. And it extends into First Strike as well, because its already implied that Halsey knows NOBLE Team is a bunch of S-IIIs, it just begins a domino effect that potentially can destroy everything everyone has worked on for the past decade. So even though you point out Ackerson's discussion in First Strike anyone could, again potentially bring the point out that it never happened.


 * And the other question becomes as Jugus mentioned earlier, if they really have changed the dates why didn't they establish that in the re-release of FoR it would have been the perfect opportunity to correct halo canon, but they didn't which again continues to show either a level of incompetence or just showing that they don't care. Durandal-217 21:50, August 18, 2010 (UTC)


 * With 343 Industries, they really try to care, but they're utterly incompetent at what they do. The FoR re-release is evidence of that - it was a total screw-up on all levels. You'd think they would have learned from the Encyclopedia that fans are very sensitive to mistake, and they make a lot of them, but no, they came out worse. If they really want to pick themselves up, for starters they should fire their editor Eric Raab for the half-assed job he's doing, and secondly not to bloody screw up the other re-issues. - Black Mesa.jpg Halo-343   ( Talk )   ( Contribs )   ( Edits )  10:15, August 20, 2010 (UTC)


 * Halo-343, show some respect please.


 * I would show respect were it warranted, but the subject of the FoR reissue does not warrant respect. I respect 343 for their generosity in providing the community with new Halo content, but I do not respect their lack of quality control and their inability to learn from past mistakes. I've voiced myself above, so there's no need for me to take it further, and besides, this is off-topic anyway. - Black Mesa.jpg Halo-343   ( Talk )   ( Contribs )   ( Edits )  22:45, August 22, 2010 (UTC)

Another theory
It is possible that that first Covenant attack force was just to knock out the communications array so that when the Covenant fleet arrived, the UNSC would not detect them (which failed for the most part).

Supported by the fact that the UNSC didn't know the Covenant was there on Reach. But if Winter Contingency took place when the Covenant fleet entered the system, the UNSC would have known that it was the Covenant attacking the communications array. --


 * This is already common knowledge and has been stated by Bungie as the main plot for the first mission, Winter Contingency.

New info from FoR reprint
Some new information on the apparent date discrepancy...

Part of the bonus content released with the Fall of Reach reprint details an ONI investigation of a secure UNSC transmission that was leaked/intercepted by the Covenant, apparently giving away the location of Reach. This could mean that Bungie is indeed retconning, and that the Covenant already knew where Reach was by the time the Iroquois probe revealed its location. Or, I could be horribly misinterpreting this, and it could mean something entirely different. Just a little tidbit for those who don't have the book to think about.

 // ŝтŕγκęŕ [ COM | LOG/M | LOG/S ] 23:33, August 21, 2010 (UTC)

On the Fall of Reach page, it says that its now true that there is 750 Covenant ships above Reach, but 314 ships exit slipspace. Shoud we change it so that 750 ships exit slipspace, or do we just ignore the fact that 436 ships appear out of thin air? Darb 013 17:15, August 22, 2010 (UTC)

I put this inthe "new info for FoR reprint" because of this. "During the Battle of Earth, Terrence Hood estimated the size of the Covenant fleet at Reach as 750 ships/[19] In the original version of Halo: The Fall of Reach, this number is instead "314," though this figure was replaced with "750" in the update." Darb 013 17:19, August 22, 2010 (UTC)

Someone obviously read this and made the changes. Never mind. Darb 013 02:12, August 23, 2010 (UTC)

Another theory *sigh*
Well, I got to thinking about the situation and I sincerely hope Bungie isn't making a mistake and retconning the dates found in the Fall of Reach. However, I have two new explanations: I hope this bogus theory helps out in some way. Cheers, -- CoD addict · (talk) 15:02, August 22, 2010 (UTC)
 * Bungie hasn't yet realized that the dates are wrong
 * ONI covered up the initial, small invasion so Reach would have optimal defenses for the next battle.

How many Covenant ships are there?
So let me get this straight, there were about 300 covenant ships above Reach, but in Halo 2, Lord Hood made a comment that went something like this "the number of Covenant ships above Reach was 50 times this size". BUT (supposedly) Lord Hood was exaggerating when he said this; so this still canonically means that there is only 300 Covenant ships above Reach. BUT the new FoR "revised" verson now says that there was 750 ships above Reach; and took Lord Hood's statement literally. So one (or two) source(s) say 300, and one says 750. Which number will be displayed on the Fall of Reach page, beacuse on the Trivia section it says that the new FoR number is incorrect (does that go aganist the Canon Policy?) but the rest of the page says 750 Thank you. Darb 013 04:50, August 24, 2010 (UTC)

Trivia also says that 750 is only used once in the book. I would go with the previous established 314. 750 turns the fall of reach into a slaughter, rather then the defiant and brutal last stand the planet made in The un-revised version. Even if it does end up being over 700, it's a really poor change by the PTB, that changes the entire context of the battle. ProphetofTruth 13:03, August 24, 2010 (UTC)


 * Actually, no. In the original, the Epsilon Eridani fleet protecting Reach takes on a Covenant fleet far superior in number. They manage to destroy more Covenant ships than the size of the UNSC fleet. That's pretty good. In the revision, they're simply going against an even bigger fleet. They still destroy more ships than they should have (covenant losses are generally a third of the UNSC's fleet size).-- Forerunner 13:34, August 24, 2010 (UTC)


 * Honestly, I see no logical reason why 343i would change the figure from a more sensible 314 to 750 just because of Hood's line. For the first thing, dialogue spoken by characters in fiction can't always be taken literally or assumed to be entirely reliable. Second, there could be a number of reasons for Hood to say "fifty times this size". For one, he might've just been exaggerating as suggested above. Or, he was misinformed of the real size of the fleet which is a likely option. --<font color="MidnightBlue">Jugus (<font color="Gray">Talk  | <font color="Gray">Contribs ) 13:36, August 24, 2010 (UTC)


 * They obviously took Hood literally and assumed that there was an error. Hell, the article even said in the trivia section that it might be an error. 343i probably went to Halopedia to find information and skim-read through this very article.-- Forerunner 13:41, August 24, 2010 (UTC)


 * Well, if the boot doesn't fit, don't wear it. Since that huge number of ships would warp the Battle of Reach into a slaughterhouse, we shouldn't consider it cannon because, it wasn't an easy victory for the Covenant. It was just a mistake on the part of 343i who thought they were helping out some of the inconsistencies in the book. Que   Sera,  Sera  13:48, August 24, 2010 (UTC)


 * It was an intentional alteration. Besides, the Orbital Defence Platforms played a very big part.-- Forerunner 13:54, August 24, 2010 (UTC)


 * It was intentional, but it seems they completely ignored the context. 750 Covenant ships could obliterate all human defenses with a single salvo of plasma torpedoes. As a theory to make the new figure more acceptable, could it be possible that 436 of the ships were actually smaller craft, like fighters or troop transports, leaving 314 capital ships? I don't have the reissue so I can't check the exact wording. --<font color="MidnightBlue">Jugus (<font color="Gray">Talk  | <font color="Gray">Contribs ) 14:00, August 24, 2010 (UTC)
 * On the other hand, a single salvo of plasma torpedos from 750 ships could also destroy several hundred of their own ships, between that the ships would have to be much closer to each other and Captain Keyes ;-) Andrew-108 02:21, September 19, 2010 (UTC)


 * The ODP's did play a very big part, but Reach only had 20 of them, which would be no match for 750 Covenant starships.Darb 013 14:13, August 24, 2010 (UTC)


 * Is it taking into account that there are other colonies in the system? Perhaps the excess ships were busy on Verge or Tribute.-- Forerunner 14:22, August 24, 2010 (UTC)


 * Actually, Verge is not in Epsilon Eridani, as evidenced by the fact it was stated to have been invaded months before the invasion of Tribute (don't ask me how Team Black got to another system during a single battle, though). Still, there's a remarkable number of colonies in the Epsilon Eridani system, so dividing the fleet to each would leave Reach with a smaller number of ships. --<font color="MidnightBlue">Jugus (<font color="Gray">Talk  | <font color="Gray">Contribs ) 14:30, August 24, 2010 (UTC)


 * At least four colonies - Reach; Beta Gabriel; Circumstance; Tantalus and possibly Epsilon Eridani IV (could just be a more scientific name for one of the previous colonies, like calling Earth "Sol III").-- Forerunner 14:34, August 24, 2010 (UTC)


 * Reach is probably the only planet with ODPs in the system since it is a UNSC Powerhouse, so the majority of the Covenant fleet would be attacking Reach since it is the only planet that is putting up a fight. It would be a waste of "ship-power" to send a lot of ships on a planet you could glass later on (when you arnt getting shot at by the ODPs). Darb 013 15:01, August 24, 2010 (UTC)


 * That's not the way the Covenant act. Hell, they decided to go past the Home Fleet at Earth and float above New Mombasa. Tactically, that's stupid. The Covenant aren't good tacticians at all - that's how the UNSC could win ground battles.-- Forerunner 15:05, August 24, 2010 (UTC)


 * Good point, they are quite dumb sometimes. Darb 013 15:18, August 24, 2010 (UTC)
 * Right, Forerunner. In some of the books, some of the Covenant mention that Humans are indeed excellent tacticians and some Elites even go so far as to admire them for it. -- CoD addict · (talk) 01:35, August 28, 2010 (UTC)

Recommend changing main picture
I believe it would be more appropriate to change the main picture at the top-right of the page to one of the more sorrowful pictures of, say, Noble Six grimly looking up at the crashed Corvette with nought but his pistol.
 * I agree. If we're going to call this page "Fall of Reach", let us convey that impression. -- SFH 01:56, September 15, 2010 (UTC)

Me too, but preferably one without Noble Six in it. But I do agree that the current image does not reflect the scale of the battle all that well and the previous image, though rather dated, conveyed it a little better. Tuckerscreator (<font color="#008000">stalk ) 02:04, September 15, 2010 (UTC)

Limited Edition content-Possible solution to date disunity
Yesterday I picked up the limited Edition of Halo Reach and I just finished reading the Hasley's Journal and it seems to suport the events of the fall of Reach while mentioning a small invasion during the July 26 2552 entry. Later it says "If one small team of Covanat have infiltrated Reach, More shall surly follow. I must prepare for the worst case senerio with operation white glove." then the journal continues following the timeline established in the Novel The fall of Reach (the Journal also validates the events of Halo Wars and tries to put light to the differing acounts of Spartans as well)Dragrath1 19:45, September 15, 2010 (UTC)

Retcons
So, now that we know for a fact that Reach contains massive amounts of retcons, especially surrounding the events of Aug 30, how are we going to handle all this? Halsey's journal does reconcile some of it, but not major inconsistencies, like Halsey being in Sword Base while she's supposed to be somewhere else, the Pillar of Autumn being on the surface while it should've escaped already, etc. At least the old timeline is something we have to abandon at this point, if we are to accept Halo: Reach as superior canon. Either way, it's going to require a lot of work. For example, are we going to assume that the space battle in The Fall of Reach occurred after the Autumn lifts off in Reach? Even that raises inconsistencies with the canon, but just throwing all of the "old" canon away doesn't feel right either. Save what can be saved. The question is, how are we going to do it without slipping to the fanon side too much? --<font color="MidnightBlue">Jugus (<font color="Gray">Talk  | <font color="Gray">Contribs ) 19:56, September 15, 2010 (UTC)
 * "are we going to assume that the space battle in The Fall of Reach occurred after the Autumn lifts off in Reach?"
 * Looking at the timeline of the article, I would say so. If I remember correctly, the Autumn required to be refitted for the "Capture a Prophet and etc" mission.
 * In regards as to resolving retcons, can't really say anything other than "save what can be saved". Let's do it slowly to make sure we don't wander off into fanon-land.- <font face="Century Gothic"> <font color="#FF4F00">5 əb<font color="#FF4F00">'7 aŋk (<font color="#FF4F00">7alk ) 20:12, September 15, 2010 (UTC)


 * Again, you guys are over-exaggerating. From how I see it, the Autumn is in the shipyard because she's undergoing maintenance for her special mission. The ship is launched after Cortana is brought onboard and it heads into space. Receiving a hail from Gamma station, they turn back and are forced to deploy their S-II complement to Gamma station and Reach, in the hopes of both allowing the remaining orbital platforms and UNSC ships (there seem to be a few left, but not much) to continue their hopeless defence. The only major retcon I can find is the August 30 one. It's just "Section VI" of Halo: The Fall of Reach that needs to be looked into, not the rest of Halo canon. "First Strike" in fact, seems relatively untouched apart from chronometer changes (Unless the "Gamma" and Reach ops took place while the Autumn was groundside). Also, I don't see anything about Halsey's location that is contradicted, other than the aforementioned chronometer changes.--  Fore  run  ner '' 20:14, September 15, 2010 (UTC)
 * So, we could say that the Fall of Reach space battle, the Gamma operation, and Red Team's fight on the surface only take place after Six is killed?--The All-knowing Sith&#39;ari 20:16, September 15, 2010 (UTC)
 * Well, we couldn't say for sure. We could assume that Six got separated from all UNSC contact and was left alone on Aszod ship breaking facility, whereas others are on other continents on Reach.- <font face="Century Gothic"> <font color="#FF4F00">5 əb<font color="#FF4F00">'7 aŋk (<font color="#FF4F00">7alk ) 20:21, September 15, 2010 (UTC)
 * Also, isn't Cortana on-board the Autumn performing shakedowns and prep in The Fall of Reach. According to Reach, she's in Halsey's care up until being delivered to Keyes himself. XRoadToDawnX 20:29, September 15, 2010 (UTC)
 * As revealed by the Halsey journal, the "Cortana" carried by Noble Six is actually a divided fragment of her. The actual Cortana is still presumably at the Autumn while the copy was analyzing the Forerunner data underneath Sword Base. --<font color="MidnightBlue">Jugus (<font color="Gray">Talk  | <font color="Gray">Contribs ) 20:31, September 15, 2010 (UTC)
 * The problem is, the level The Pillar of Autumn begins on August 30, at 16:52 hours. In The Fall of Reach, the Autumn is already in space at 04:00 hours on the same day, and she escapes some time after 06:37. About Halsey's whereabouts, in the book, she's in CASTLE base on August 25th, then in Camp Hatchcock on August 27th, and in Military Reservation 01478-B on August 29th. In Halo: Reach, she's under Sword Base on Aug 29th, seems to have been there for some time, and doesn't go anywhere until Jun flies her into CASTLE Base. --<font color="MidnightBlue">Jugus (<font color="Gray">Talk  | <font color="Gray">Contribs ) 20:23, September 15, 2010 (UTC)

In the journal it mentions her plans to go through with white glove, and we know that she goes through with this at sword base (she blows the whole relic up) so we can presume she arrives soon after hearing word of Covenant contact (she'd know before the general populace, she did work for ONI and was an expert hacker) and set out for Sword Base on this day. Perhaps the underground complex has rail cars going through all of Reach's abandoned mines, allowing her to move form one to the other while Reach is under siege? SpartanSeries2 22:00, September 15, 2010 (UTC)
 * Sword Base is over 4000 kilometers from CASTLE base, as revealed in the Reach map that comes with the limited edition. In addition, they're separated by an ocean and several mountain ranges. I doubt they'd have mines or underground railways that long. --<font color="MidnightBlue">Jugus (<font color="Gray">Talk  | <font color="Gray">Contribs ) 22:09, September 15, 2010 (UTC)

I suppose that's true, but wasn't Reach a massive mining colony before it became a military one? Also as per the PoA thing that's just a retcon plain and simple. You know, I like all this new stuff info and what not. Sure a change/retcon here and there, but the majority of cannon remains unaffected. I think they chose to limit the game to 1 province for that purpose. Let's them say the battle was "isolated" or "secret" to keep people from panicking (up until the fleet arrives of course) if need be. SpartanSeries2 22:14, September 15, 2010 (UTC)

Proposing new page for "raid" of Reach
No, I'm not saying it should be split from this article, but it should be made into a "sub-battle" since right now, with new content coming from Halo: Reach, the article's starting to get pretty huge, while the "Skirmishes" section takes up a large section of it. And that part wasn't even really a part of the Fall of Reach itself; the planet had already fallen at that point, and it was simply a rescue mission involving a few participants, instead of a planetary scale conflict. --<font color="MidnightBlue">Jugus (<font color="Gray">Talk  | <font color="Gray">Contribs ) 07:21, September 16, 2010 (UTC)


 * Why don't we just add the information from Reach and then decide as to should the article be divided? Also, truth-be told, the article as whole it not concise and not properly summarised. We can still see irrelevant information from the novel inside the event (i.e. "John-117 convinced the team to go to the surface while Cortana continued to pilot the ship. Cortana determined a hole in the Covenant patrol pattern and used it to determine an extraction point."). That's why those sections are long and uninformative. If anything, it should look like a proper battle article like the ones in Wikipedia. What we should do is to remove the trivial information from the novel and improve the content based on our newly-acquired information. - <font face="Century Gothic"> <font color="#FF4F00">5 əb<font color="#FF4F00">'7 aŋk (<font color="#FF4F00">7alk ) 07:41, September 16, 2010 (UTC)


 * I'm not saying that it should necessarily be divided or made distinct from the Fall of Reach like it used to be, but made into its own article, sort of like how Operation: UPPERCUT and the Battle of Viery have their own pages. As the rescue mission isn't really a major part of the conflict, it could be described with a short section on this page, and have a more elaborate description in an article of its own. But it's true that the information on this page is way over-detailed and needs summarizing. --<font color="MidnightBlue">Jugus (<font color="Gray">Talk  | <font color="Gray">Contribs ) 07:46, September 16, 2010 (UTC)


 * Oh, of course we should do that. :P If there's a large military engagement, we should definitely create an sub-article.- <font face="Century Gothic"> <font color="#FF4F00">5 əb<font color="#FF4F00">'7 aŋk (<font color="#FF4F00">7alk ) 07:57, September 16, 2010 (UTC)

Theory on PoA and timeframe
So, I previously suggested that the space battle depicted in the novel with the Pillar of Autumn participating probably occurs after it lifts off from the drydock, as per the new canon presented in Reach. However, I've come up with another possibility that wouldn't require as much ignoring previous canon. In The Fall of Reach, the last we hear of the PoA in Epsilon Eridani is Cortana jumping the ship into slipspace at just after 0647 hours (pg336). As we know, the PoA is lying at the Aszod drydock well after 2000 hours on the same day. Now, one might assume it's been there for some time, but what if the PoA didn't jump into slipspace at 06.47 but actually returned to Reach for repairs? I know that this sounds extremely implausible given the situation, but I think it's the best theory we have to reconcile the book and the game.

I've thought of a possible scenario that could allow for this to happen. Consider this: The Autumn attempts jumping into slipspace, but the S-F drive is damaged and the ship's forced to exit immediately/can't jump at all. They have no choice but to return to Reach to have the damage repaired. The Autumn quickly descends to the Aszod shipyards (through means unknown; possibly using similar rockets as they did in the liftoff to break the fall). After the damage is repaired, they only need to wait for Noble Six and Emile to deliver the Cortana "copy". Again, I see no real point for the Autumn to land in the atmosphere at all, but one might guess that the orbital shipyards had already been destroyed so Aszod was the only remaining place where they could get the ship back to working condition. --<font color="MidnightBlue">Jugus (<font color="Gray">Talk  | <font color="Gray">Contribs ) 12:42, September 16, 2010 (UTC)


 * Well, according to Reach 's PoA level, the Pillar of Autumn is still in the drydock as of 1652 hours, Aug 30th, 2552. If anything, we should really record those dates from the cutscenes and add them to Forerunner's Reach timeline. They appear to offer tremendous amount of clues/hints. That way, we can avoid all the potential bickering and useless-and-potentially-out-of-focus discussions.- <font face="Century Gothic"> <font color="#FF4F00">5 əb<font color="#FF4F00">'7 aŋk (<font color="#FF4F00">7alk ) 12:49, September 16, 2010 (UTC)


 * Sorry, it was meant to say 1652 instead of 2000. Confused it with Lone Wolf. Anyways, I agree that the dates from the cutscenes should be added. Still, the above theory is really the only way to make any sense out of the events. Bottom line; The PoA returns to Reach after it was supposed to jump away. No unnecessary details or speculation needed. --<font color="MidnightBlue">Jugus (<font color="Gray">Talk  | <font color="Gray">Contribs ) 12:58, September 16, 2010 (UTC)


 * This post could be of help.- <font face="Century Gothic"> <font color="#FF4F00">5 əb<font color="#FF4F00">'7 aŋk (<font color="#FF4F00">7alk ) 12:51, September 16, 2010 (UTC)


 * It's a nice summary, but I got the basic timeline already figured out. Thought I'd make an elaborate timeline, with all relevant events included. Or should that be added to Forerunner's timeline? --<font color="MidnightBlue">Jugus (<font color="Gray">Talk  | <font color="Gray">Contribs ) 12:58, September 16, 2010 (UTC)

"Massive Fleet"
Judging by the cut scene after LNoS as well as what is expressed in the FoR with 314 ships "arriving" it is hardly conceivable that the fleet that arrived in this cut scene was "massive." First and foremost were only see a few ships in the cut scene, secondly from the on we encounter less then 5 on the ground/attacking reach.

I suggest perhaps this was a "scouting" section of the Fleet of Particular Justice sent to back up the Super Carrier upon discovery that Reach was a MAJOR human colony arrived on August 13th an subsequently went to ground in the Viery territory. After all, no battle is mentioend to be happening elsewhere up until the 30th, when I propose the MAIN section of the Fleet of Particular Justice arrives and the "Fall of Reach" as expressed in the book truly begins. With this in my mind I think we could take the "massive" out of the section about the 13th.

Thoughts? SpartanSeries2 03:04, September 19, 2010 (UTC)
 * I find that to be quite plausible. I had a similar idea myself.--The All-knowing Sith&#39;ari 15:27, September 19, 2010 (UTC)

Timeline Explained (As I See It)
Hey all, this is my first major post here, but I came up with a (potentially) novel explanation for the timeline discrepencies between the book and the game. I hope I'm not reading too much into this, but I found it rather fun to figure out at any rate. This theory is based off of three things:

1.) That Reach has a 390 day year and 27 hour day as explained on the CAA Handbook-Bungie

2.) That Halo: Reach uses local planetary time for its timestamps as the level "The Package" begins at approx "26:00 hours", clearly local time.

3.) Halo:FoR uses "Military Calendar" for timestamps, presumably Earth time and a 24 hour day cycle.

What I'm getting at is that UNSC military time as depicted in Halo:FoR and Reach planetary time as depicted in Halo:Reach is diveregent by approximately 15.625 days or 15 days 1687 hours. I got this through some very simple math: 390 - 365 = 25 day difference between Earth and Reach. This comes out to, on average, an additional 2.083 days per month on Reach ASSUMING that Reach uses the same names of months as Earth would.

I then used this to determine how diveregent time would be IF we assume that the fleet that jumps in during the "Long Night of Solace" is the big, bad Covie fleet in FoR and that the major fleet engagement occurs on August 30th Military Calendar and August 15 Reach Calendar, essentially between Long Night of Solace and the Battle of New Alexandria.

This works as "Long Night of solace" begins at approx 1200 hours on August 14 (Reach Calendar). Thus, the difference between that time and Military Calendar (Earth time) would be ~7.5 months x an additional 2.0833 days on average per month = 15.625 day time difference which would set the beginning of LNoS at ~ August 30 0187 (Military Calendar).

As far as I can tell, having the Battle of Viery Territory through the end of the game occur between ~August 27th and September 15th creates the fewest inconsistencies, though it presumes that the PoA goes landside for 15 days to get the package. A stretch? Sure, but less of one than assuming that a gigantic battle can take place without anyone knowing (i.e. half of the game). Chime in to let me know what you think of this/ tell me if I am completely wrong.

(The only other inconsistency this creates is with Halsey's placement of July 24th-26th as the dates which Reach are first discovered, but that's less of an inconsistency than what occurs if we keep Reach and Military calendars the same.)

TLDR Version

1.) Using Info from Bungie, determined time difference between Reach and Earth.

2.) Realize game is using "Reach" time

3.) Calculated difference as of LNoS to be 15.625 days.

3.) Events of FoR take place on August 30 Military Calendar, August 15 Reach (game) calendar,

CINCLesothoCINCLesotho


 * ^kickass -- UNSC.jpg CoD addict  ( talk ) 00:05, September 23, 2010 (UTC)
 * Awesome theory. Might not be true, but definitely an awesome and well thought-out theory :)
 * Matt-256 20:37, September 23, 2010 (UTC)

Hmm makes a lot of sense actually. Well done. <font color="Blue"> Helljumper U T C


 * This theory does make a lot of sense. The only problem I have with it is that the way I see it, your math is dependent on Reach and Earth having coordinated new years' days for the year 2552; for instance, 1/1/2552 on Reach must be the same day as 1/1/2552 on Earth, which they probably don't, in order for the 15 day difference to be taken into account. Otherwise, the actual date difference could be much different depending on which specific date Reach and Earth were initially coordinated at. But even in that case, the year on Reach could not have been 2552 since a Reach year is roughly ~1700 hours (about 70-ish Earth/60-ish Reach days) or so longer than an Earth year, which I think messes up the entire timeline according to the game since it does use Reach time, which we've established it does. I think at this point we just need someone official to clear up the date/time system used by the UNSC for its local colonies and how it relates to the game. ---dky 02:20, October 1, 2010 (UTC)

Okay, I did some more math to check your figures. I tried a different method by counting the number of hours instead of taking just days into account, since the fact that 1 Reach Day &ne; 1 Earth Day is an important factor. Let's assume that 1/1/52 Reach = 1/1/52 Earth, for the sake of simplicity.

We know that the Hour (H) is a standard time unit throughout the UNSC.

In this case, we know that 1 Earth Day (ED) = 24 H, and we also know that 1 Reach Day (RD) = 27 H

We also know:

1 Earth Year (EY) = 365.25 * ED = (365.25 ED * 24 H/ED) H = 8766 H

1 Reach Year (RY) = 390 * RD = (390 ED * 27 H/ED) H = 10530 H

The Fall of Reach according to the book started on 8/30/52 using the UNSC Military Calendar, Earth Time (ET). That would be equivalent to 242 Earth Days after New Year's Day, 2552 (we'll use the term "NY" for reference). It just so happens that the year 2552 (Earth) is a Leap Year, by the way.

And so, we get:

8/30/52 ET = NY + 242 ED

242 ED = 5808 H

5808 H = ~215.11 RD

242 - 215.11 = 26.89

That means that there would be a 26.89-day time difference between Earth and Reach as of the date 8/30/2552 ET.

I do note that these were calculated for 8/30 ET, and not 8/15 RT. You can't use 8/15 RT because you would not be able to get the number of hours between New Years and that day on Reach, since we don't know how many days each month has on the Reach calendar. Therefore, we need to work backwards with the established Earth date, for which we would be able to know the number of hours.

Food for thought. I haven't run this through my head too much so please correct me if you wish. ---dky 03:21, October 1, 2010 (UTC)

temporal anomaly?
See here where it says "Unknown time: The Installation 04 survivors arrive at Reach, having experienced a temporal anomaly sending them nearly two weeks into the past." Where is this from? I searched the wiki and found no results about any page talking about temporal anomaly sending people back in time... Been a long time since I've ready the books. Can someone explain? --Mboverload 07:50, September 23, 2010 (UTC)


 * It's from First Strike. The anomaly was caused by the Forerunner Crystal and appears to have only affected the survivors from Installation 04. They were indeed sent back in time from Sept. 22nd to Sept. 7th when they returned to Reach. --<font color="MidnightBlue">Jugus (<font color="Gray">Talk  | <font color="Gray">Contribs ) 07:58, September 23, 2010 (UTC)
 * How exactly does that work? Did they return to Reach or was the time change local to a certain area (e.g. the Ascendant Justice) -- UNSC.jpg CoD addict  ( talk ) 20:23, September 23, 2010 (UTC)


 * The Crystal affected the flow of time around them. Physically, they were travelling to Reach through slipspace from Alpha Halo. Temporally, they were also moving backwards through time as they travelled. It wasn't simply a "rewind" function, if that's what you're asking - and if you're not, sorry I can't be more helpful! --  Specops306   Autocrat     Qur'a 'Morhek   23:03, September 23, 2010 (UTC)
 * So they arrived at Reach before the battle?! /confusedface -- UNSC.jpg CoD addict  ( talk ) 19:19, September 30, 2010 (UTC)
 * No. Most of the heavy fighting was over by September 7th. --WhellerNG 01:09, October 1, 2010 (UTC)
 * Ah. I was getting the dates confused with August 7th. I forgot that it took a good while for the Autumn to get to Alpha Halo. -- UNSC.jpg CoD addict  ( talk ) 04:12, October 1, 2010 (UTC)

Thel killed Noble Six?
I've played Lone Wolf but I didn't see Thel Vadamee apparing to kill Noble Six. It would be hard to tell since he did not have the distinctive Arbiter armor then. Are there sources to confirm this? -Hahap 02:19, October 1, 2010 (UTC)

Just to make sure I didn't miss something, When did Thel come into this? Sicarius-X 02:26, October 1, 2010 (UTC)


 * He didn't. Someone inserted fanon into the article. It was promptly removed. Don't worry about it. --&quot;Government big enough to supply everything you need is big enough to take everything you have.&quot; -Thomas Jefferson 03:04, October 1, 2010 (UTC)

Spartan-IIs on reach, but unaware of the invasion?
What about Juns comment at the end of New Alexandria? "Sir, it true that gauntlet, red and echo teams are assigned to civilian evac ops?" to which Kat says, "Point is, why put spartans on defensive deployments?". Kats comment basically confirms that gauntlet red and echo teams are spartan teams. This takes place on August 23rd. Could this retcon the books retelling of the spartans of red and blue team? It could lead us to assume that the spartan-IIs arrived around aug 15th, when "60% of the UNSC fleet" arrived.

Also in Halseys journal it says the spartans met with her on reach on August 27th. I have a very hard time believing that even though 60% of the UNSC fleet was fighting in the battle at that time, the spartan-IIs were completely unaware. The planet was half on fire...

Well the UNSC was losing but still holding its own with MACs still online. It could be possible that the SIIs although there were not involved in the combat until after the POA took off as they had to prepare for a top secret mission. The 3 Spartan teams meantioned were quiet likely other SIII teams that were order control of Colonel Holland. VARGR 12:00, October 1, 2010 (UTC)

Bungie knew who Red team was, I can't imagine they'd name a team of S-IIIs red team when they already knew there was a red team and all this would do is cause mass confusion.