Frequently Asked Forum Questions
Search the HBO News Archives Any All Exact		Search the Halo Updates DBs Halo Halo2		Bungie Webcam HBO XBL Gamertags *Ar's Simple HTML Guide Shishka's Guide for Newcomers The Lowdown on Download Accelerators Red Loser's Anti-Spamming Guide Egg FAQ | More Egg Stuff c0ld's Movie Starter Guide Shishka's HaloPC Pre-Release FAQ 3.1 AutoMagic 117 StripzMaker
Search Older Posts on This Forum: Posts on Current Forum | Archived Posts

Re: My Comprehensive-ish Argument With Narcogen
Posted By: Stephen L. (SoundEffect) <soundeffect@hotmail.com>	Date: 5/31/11 6:45 a.m.
: Joe Staten mentions, I believe it was in the commentary on the H1/H2 : cutscenes in the Halo 2 legendary edition, that the character was referred : to internally only as "sniper sergeant", was not expected to be : a major character, and whose popularity-- which necessitated his return-- : was unexpected. His appearance and style of dialogue in Halo 1 are lifted : almost in their entirety from the character of Sgt. Apone in Aliens (to : which Halo owes quite a lot else, besides) I just finished reinstalling Halo PC last night (new computer). I'll look to the face textures of the characters. I thought Johnson was named. : Dates *do not* have to be set in stone for sufficient continuity to establish : and maintain verisimilitude except for those who feel compelled to check : them, which is not most audience members. Specific dates are put in not to : establish them as specific dates, but to make it appear as realistic as : possible. Security cameras in fiction have date and timestamps on them not : because the value of those timestamps are important, or will match up with : other timestamps later, but because *real security cameras have : timestamps* and in order to "feel real" the fictional ones must : have them, too. The values only have to be "good enough". To : confess that Bungie, or the characters in the Haloverse, don't really know : the exact day, date, or time of day that a specific sequence of events : occurred would be embarrassing and would break verisimilitude. The same : goes for just about every picayune detail in the universe, including : vehicle and weapon specifications, etc. What gives the player the : impression that "hey this universe is detailed, a lot of thought went : into it" is the sheer volume and specificity of details, not an utter : lack of continuity errors, because in terms of generating the most : verisimilitude for the most audience members, generating a large volume of : details trumps achieving a high degree of continuity, and does so almost : every time. Sure, there is a lower limit, but Halo is way, way over it-- : way above the Star Trek and Star Wars series, for instance, and probably : ahead of just about every other franchise I can think of that exists in as : many forms of media over a similar period of creation time. Looking at an issue JUST within the games, the Autumn arrives at Alpha Halo in September, 2552 according to Reach but Jenkins' helmet cam indicates the Flood discovery occurs back in May 2552, and then when back on Earth, ODST takes place in October 2552. If Bungie was to keep consistent within themselves, why didn't Reach's timestamps lead to correcting the timeline back to May 2552? They chose to retcon their own work. But that's OK because it's been 10 years and the fashionable way to deal with that is to change things. Why keep it consistent? No one pays attention to that sort of thing. (This was just an example for those who say that the games are internally consistent within themselves and that all inconsistencies have been introduced cross-media.)

My HBO Articles

Message Index