Prime example. The original release, from chapter 15 onward, the dates are in the year 2552.
In the re-release, the years are all 25[b]4[/b]2.
Either Bungie/343i have changed the time-line, or the book is messed up. One prime example:
Chapter 25 (original printing):
[quote][b]0915 Hours, August 25, 2552 (Military Calendar) /
Epsilon Eridani System, Reach UNSC Military Complex,
planet Reach, Omega Wing--Section Three secure facility[/b][/quote]
Near the end of the chapter, is this:
[quote]"Halcyon-class ships were pulled from long-term storage--they were designed to be scrapped, in fact. The [i]Autumn[/i] was re-fit in 2550, to serve in the current conflict near Zeta Doradus."[/quote]
They can't be talking past tense ("2550") if the date the chapter is supposed to occur is 2542...
Now for the re-print:
[quote][b]0915 Hours, August 25, 2542 (Military Calendar) /
Epsilon Eridani System, Reach UNSC Military Complex,
planet Reach, Omega Wing--Section Three secure facility[/b]
...
"Halcyon-class ships were pulled from long-term storage--they were designed to be scrapped, in fact. The [i]Autumn[/i] was re-fit in 2550, to serve in the current conflict near Zeta Doradus."[/quote]
At the very end of the book there is a logged, timed and dated conversation between two guys with the screen names "GLancer" and "TRIGTECH". One (or both) appear to be on Reach from this conversation bit:
[quote][b]TRIGTECH:[/b] Think they're Spartans? Ever seen one?
[1359, 19.07.2552]
[b]GLancer:[/b] Not in person, so I can't say, but pretty damn sure they were something special, and that's what's got me freaked.
[1400, 19.07.2552]
[b]TRIGTECH:[/b] Why? If we got Spartans roaming around I'd like to see the Covies pick a fight, right? Reach's already fortified like the gates of heaven, so adding sme high-end face-punchers to the mix only works in our favor. Crisis averted.
[1401, 19.07.2552][/quote]
It would appear to me that the editor of the re-release messed up the year for 23 chapters plus the epilogue. Really, guys? Hype the re-release with having additional information and CORRECTIONS, but miss essentially 24 chapters worth of dates?
[Edited on 08.05.2010 3:47 AM PDT]
-
[quote][b]Posted by:[/b] Wabajack If you had read, I never mentioned the game (which you just lost).[/quote] you sir an an arse i hate the game. anyways [/quote] I'm an arse for pointing out an error? Alrighty then...
-
[quote][b]Posted by:[/b] MAGIC COOKIE123 OMFG!!! THE GAME DOESNT FOLLOW THE BOOK!!![/quote]weve known this since like when the game was announced
-
If you had read, I never mentioned the game (which you just lost).[/quote] you sir an an arse i hate the game. anyways want to get into a goof if you read the books Spoiler =]) than you know that all spartan 3's die in the first two groups save 2 and the new ones are killed off by the sentinels on onyx and yet they are on reach the spartan 2 home world/ODST training facility [Edited on 08.05.2010 4:28 AM PDT]
-
I thought the purpose of the rewrites was to fix the canon not mess it up. Its messed up worse than it was in the first place. Seriously the editor obviously wasnt a follower of halo. Mybe they will recall them to fix it?
-
The books and various cannon are full of errors.
-
[quote][b]Posted by:[/b] Spartan5252 Damn it, this has ruined the book for me. Well if i pick up the re-release then I will write in the correct date myself if i have too. But I shouldnt have too, thats the job of the editor.[/quote] Yeah, epic fail on their part. [quote][b]Posted by:[/b] MAGIC COOKIE123 OMFG!!! THE GAME DOESNT FOLLOW THE BOOK!!![/quote] HURR DURR IT'S MORE LIKE THE SAME BOOKS CONTRADICT EACH OTHER DURR If you had read, I never mentioned the game (which you just lost). [Edited on 08.05.2010 4:16 AM PDT]
-
OMFG!!! THE GAME DOESNT FOLLOW THE BOOK!!!
-
Damn it, this has ruined the book for me. Well if i pick up the re-release then I will write in the correct date myself if i have too. But I shouldnt have too, thats the job of the editor.
-
[quote][b]Posted by:[/b] Helveck Halo Waypoint confirmed that 2552 was actually a type/confusion error and that it was meant to be 2542 all along.[/quote] You sure about that? http://halo.xbox.com/en-us/abouthalo/timeline Halo Waypoint there is saying that Reach fell in 2552.
-
[quote][b]Posted by:[/b] Helveck Halo Waypoint confirmed that 2552 was actually a type/confusion error and that it was meant to be 2542 all along.[/quote] If that's the case, then there are many other errors as well. Namely, two guys on Reach having a chat 10 years after Reach was glassed. I can understand if the "2550" was an error when the actual date was supposed to be 2542, but leaving several pages of a conversation with the 2552 date? [Edited on 08.05.2010 3:52 AM PDT]
-
[quote][b]Posted by:[/b] Helveck Halo Waypoint confirmed that 2552 was actually a type/confusion error and that it was meant to be 2542 all along.[/quote] Well there's either an error with the timeline or an error with the Autumn's rearmament date.
-
Frankly, a lot of what happened in the Fall of Reach has gone out the window since it's first release. I.e the UNSC only encountered Elites at the Battle of Reach. That said, you'd think they'd at least fix the little things like dates.
-
Halo Waypoint confirmed that 2552 was actually a type/confusion error and that it was meant to be 2542 all along.
-
Probably just another stupid error.