UserProfile:Forerunner

Joined

August 12, 2010

About the Prophet of Disdain I found him through pity's page and was curious why is he non canon when pity is consider so? Shouldn't both be consider the same regardless? Was going to ask this in the talk page but saw you deleted it few years back so figured I just ask here.

Could you add your MJONLIR/HRUNTING/cyclops graph to the MJONLIR page?

It's rather confusing how the whole lineaage works on the page, now.

I understand. Since there's hardly any information out other then their names and a vague picture, it might be best to wait anyway.

Hello there,

I have one simple question regarding halo 4. There has been a leakage of 2 new enemies in halo 4: http://www.xbox-skyer.com/attachment.php?attachmentid=269919 I suspect you already know about that.

I just wondered if it was ok to make a wiki page about these? because there hasn't been any made and I feel that it would have, was the content deemed legitimate. I'm asking this question because I have several question marks at the legitimacy as well.

Thanks for your time,

Thijsbos

I think 343i's explanation falls apart because it relies on a cover-up that would be impossible, not to mention completely counterproductive to implement.

For one, I don't buy the idea that a single groundside relay was responsible for all communications across the planet - all ships (and likely satellites) have basic maser and radio communications of their own; how else could they communicate in deep space? The only possible way they could keep the majority of the fleet in the dark would be to create artificial "equipment failures" on every UNSC ship. Even if the UNSC fleet brass could somehow orchestrate such a thing, and keep each of the ships in consistent geostationary orbits so that they can't see what's going on in the other side, what's keeping the Covenant from showing up on their side of the planet and ruining the whole plan? Something like that would probably happen every few minutes as the Covenant ships orbited the planet, unless all of them were also on fixed geostationary orbits. Which seems unlikely, since the Covenant wouldn't know nor care about the UNSC's contrived cover-up; they'd have no reason not to show up on the other side of the planet.

Even ignoring the fact the cover-up would be a practical impossibility, it's hard to see why would they keep half of the planet in the dark if they only wanted to keep Keyes and the Autumn out of the fight until RED FLAG could begin. The rest of the fleet wasn't going to partake in RED FLAG, so why deliberately hold them back? It's particularly strange because the UNSC had no way of knowing a larger Covenant fleet would show up. Shouldn't they be concentrating all their efforts to fight the Covenant who are already present and wrecking havoc on Reach?

It seems that Bungie's intent with Reach and 343i's explanation are at odds with one another - the Data Drops seriously downplay the extent of the invasion before August 30, whereas the game depicts a full-scale invasion going on by as early as August 14 (as evident by the hologram of force deployments aboard Ardent Prayer, a massive Covenant fleet arriving, and large-scale glassing going on). It's clear that with the Data Drops, they wanted to mesh the stories of The Fall of Reach and the game together, but the result comes across as more than a little contrived. To me, a better idea would've been to add some changes to the re-release of TFoR to accommodate the new canon from Reach.