With the release of Halo: Combat Evolved Anniversary, Halo Waypoint will be seeing a major overhaul in terms of its web interface and the Windows Phone version's usability and new features. The web version will see fixes to the layout of the site, how content is pushed up by the community and the forums getting fixed from community feedback. One new major feature is the ability to set "custom challenges" for any mode that you and your friends can gain Halo: Reach credits for achieving.
Here's where it gets awesome. In conjunction with the Windows Phone Mango update, Halo Waypoint's Windows Phone version will also be getting the same treatment as the web version except for one major difference. By some voodoo magic it will be able to streamline information from your console and will be able to display a live top-down feed of where each of your teammates are and if they are in danger or already dead. It will be called the "Advanced Tactical Assault System," ATLAS for short, and will be available for all Halo: Reach maps and the new Anniversary maps as well.
Speaking of the new Halo Anniversary maps, 343 sent over some screenshots of the newly announced High Noon map, which is a remake of arguably one of the best Halo: CE maps ever, Hang 'em High. You can check those out in the gallery below and while you're at it you can check out another video of the new big update coming to the Halo Waypoint website.
Photo Gallery: (9 images)
Click to zoom - browse by swipe, or use arrow keys
Get more destructoid: We're indie-run, blogging for the love of it, and our site will always be free. Optionally, you can support us and get: (1) Faster pages from our cloud server (3) Wide(r)screen (3) No big ads on Dtoid, Japanator, Tomopop, or Flixist (4) Auto contest entries, and (5) Dibs on betas & downloads. Try it out
Unsavory comments? Please report harassment, spam, and hate speech to our moderators, and flag the user (we will ban users dishing bad karma). Can't see comments? Apps like Avast or browser extensions can cause it. You can fix it by adding *.disqus.com to your whitelists.