- gamertag: [none]
- user homepage:
Member of Bungie.net for nearly three years, still continuing!
Enjoy what you have and live on.
My gamertag is Elder Bias
Posted by: OrderedComa
Posted by: raganok99
Posted by: OrderedComa
Posted by: Spartan1065
Posted by: GingerBenj
books suck, reading is lame.
games rock, games are...game?
bungie created halo and its story, eric nylund didnt.
id say about 60% of the reach gamers have heard of the books but not necessarily read them. ultimately they dont care.
99.9% of the xbox live community is unable to read because they are to young.
therefor bungie have the right to make a kick ass game that screws a few of the books ideas.
problem solved :) My God what is happening to the Universe.
I'm going to assume by the lack of edit in the OP no one has come up with any more compelling reasons to believe that there are not glaring errors in Reach's canon since the last time I participated in the discussion in this thread. Reasons of course that weren't thought of and shot down within the first couple months of this debate starting.
Would I be correct in assuming that? I don't feel like flicking through 90+ pages of mostly the same incorrect arguments that say Reach did not break canon.
People have brought up many valid points against or explaining most if not all of Caboose's so called errors.
And Reach did not break canon, and you shouldn't claim it did because none of us has seen the complete picture (aka the Halo Story Bible). Other than what Bungie or 343i tells us about canon we know nothing of what is true or not, and Bungie has said that Reach and TFoR match, now 343i may change things, but I very highly doubt that is going to happen, so like it or not Reach is canon and does not break canon.
Sorry to burst your bubbles, but it did break the canon :) It conflicts the Fall of Reach, First Strike and Ghosts of Onyx.
As I have been reading arguments bought up by those few people like you have been defending Halo: Reach so fiercely, is basic same argument as before in early pages of this topic to now.
And, I understand that some valid points has been proved but it has little effect to none to the errors in the canon of Reach. I am sorry but there is many, probably majority of people at bungie.net seem to disagree with you and those guys. (general assumption)
A conflict does not equal a canon breach, it merely means we haven't seen the connection yet, or the older information has been retconned. Such an example of the latter would be the Elites, Brutes, and Hunters, TFoR and First Strike say they weren't encountered until 2552, yet that is not the case because the older information does not make sense and needed to be changed.
And actually no, Reach really only conflicts with TFoR, Halsey's Journal and the marketing materials released with Reach patch up the issues with First Strike and Ghosts of Onyx.
Sorry, but you're wrong.
Halsey's Journal and marketing material has fixed VERY little the errors of Halo Reach. And marketing material is rated as third, according to canon "rules". Game being first and novels being second in canon "rules". Market material does not override the canon.
There's some content in the game is canon-breaking such as wrong timeline, PoA being on ground which it is impossible due to massive weight and consider about laws of physics applied to it too. And Halycon-class cruisers or Marathon-Class cruisers or larger ships ARE NOT rated for atmosphere. You may argue that PoA went on Halo but it was not case. They were forced to land down since they suffered massive damage from fighting against battle-group of CCS battle-cruisers.
Spartan-IIIs were fine with me for now.
And it does "conflict" the novels of The Fall of Reach, First Strike and little bit of Ghost of Onyx.
Some things in Reach can be simply retconned, but others can't be retconned so simply, it would require to re-write novels.
[Edited on 06.02.2011 1:17 PM PDT]