: The all important question is if it'll maintain all my unlocks. I raced a
: buddy to General from something like Colonel to see who could unlock
: Security first. That was fun times, but it was made easier with the daily
: challenges, double xp, and the dlc playlist (CTF on Highlands, run out the
: clock, max payout). I wouldn't want to start that trip all over again. I
: don't have the time, I don't have the inclination, and Reach wasn't the
: same after 343's TU.

: When Bungie told us it'd be OUR Spartan in campaign, I didn't really care. It
: stayed that way for a solid chunk of time post launch. Just a nifty
: feature while I toyed with new unlocks and colors. And then, at some
: point, without me even realizing it happened, things just gelled, and the
: Spartan I saw in campaign, WAS my Spartan.

: Halo Reach had easily the single finest customization system in any Halo
: title. The appearance options mattered. I built a Spartan that looked
: completely at home alongside the rest of Noble, looked slick in
: multiplayer, and was 100% my own. No one else looked like me. The fact
: Halo 4 and 5 have seemingly missed that is disappointing.

Well, since our Spartans were tied to our Gamertags and the Backwards Compatibility is basically just the Xbox One running a 360 emulator, you should still have your armor unlocks. Any local saves will not carry over, like custom maps and campaign progress(maybe?)

I am looking forward to being able to play Reach Customs again, without having to dust off my old 360 and try to find a controller for it.

Reach is still my favorite Halo game in terms of it's multiplayer. People can bitch and groan about armor lock or whatever, but I really found it to be the most engaging and customizable overall.