<\/p>\n
<\/p>\n
<\/p>\n
\t\t<\/p>\n
With the release of a batch of Halo: Reach<\/a> screenshots came the usual amount of obsessive fan analysis, which in turn produced a lot of intriguing rumors — a lot of intriguing rumors that are turning out to be wrong. In Bungie’s latest weekly update<\/a>, they engaged in a round of “Halo: Reach Mythbusters,” shooting down some of the bigger rumors floating around the net. And the biggest: that Halo: Reach would use Natal motion controls.<\/p>\n As you can see in the screenshot above, the targeting reticule — typically in the middle of the screen for a first-person shooter — is mysteriously off to the left, leading many to wonder if it’s because you can aim the reticule independently using some form of motion controls. The answer is much less elaborate: “Truth be told, it’s just a good ole fashioned bug. Bug #15163 to be exact,” Bungie writes. “Halo: Reach is NOT a Natal title and is being developed expressly with the traditional Xbox 360 controller in mind.”<\/p>\n This screenshot alone created a couple of other rumors, including that the HUD will in fact be yellow (evidently it won’t), and more intriguingly, that a portion of the screen was pixelated (area is circled in the image above) because Bungie was hiding something super top secret. Here we will quote Bungie’s explanation in full, because it’s the sort of awesomely jerk-ish behavior we really respect:<\/p>\n