Are the reach servers down? When I go on Haloreachstats.com it says I never played reach when I am a reclaimer, when I try to view it on halo waypoint the page isnt available, when I get on reach I am a recruit but when I press start I am a reclaimer.
> 2533274873630868;1:
> Are the reach servers down? When I go on Haloreachstats.com it says I never played reach when I am a reclaimer, when I try to view it on halo waypoint the page isnt available, when I get on reach I am a recruit but when I press start I am a reclaimer.
They did a hard reset, which fixed everything except the File Share, which is still giving Transfer Failed messages. I think the servers needs another hard reboot.
What did the reset fix?
> 2533274846761497;3:
> What did the reset fix?
I’m not bothering to check to see if you can upload new files to the File Share, as you weren’t able to, which the hard reset should have fixed. The Hard reset did fix from what I know the following:
-The “Welcome to Halo: Reach” screen (Shown only the first time Reach is played on a profile) and the Forward Onto Dawn messages popping up everytime Reach is started up and enters the main menu.
-People being temporarily cR banned for leaving custom games.
-Some copies of Reach randomly crashing, primarily on the Xbox One.
We’ll never get custom nameplates back, huh?
> 2533274846761497;5:
> We’ll never get custom nameplates back, huh?
Nope, never.
> 2533274846761497;5:
> We’ll never get custom nameplates back, huh?
The reasoning behind that is because certain aspects Bungie had control of on b.net were never handed over. For obvious reasons, the Bungie Pro service did not carry over. Halo 3’s File Share Screenshot rendering service, the complex encoding that was ‘Road to Recon’, the encoding for nameplates for Reach, b.net’s custom Reach medals that were viewable online, and the Eternal Armor effect(As they were linked via encoding to the nameplates) for Halo: Reach was not carried over either.
Since the nameplate service with these other aspects never carried over, nameplate capability on Reach will never come back as the nameplates are frozen as is, the nameplate part on b.net is lost to time, and 343i has no intention of trying to make a way to change them.