> 2546678360738636;219:
> > 2533274868378013;218:
> > > 2546678360738636;217:
> > > > 2533274813317074;3:
> > > > Just wanted to drop in that 343 are aware of the issues 
> > > >
> > > > No etaās on fixing, but info has been passed over to the relevant teams by Bravo (source: twitter)
> > >
> > >
> > > Happy to see an official statement. Im just now going through all the comments to see what the latest is
> >
> >
> > Haha! There have only been those 2 things.
> >
> > Yes thatās right, a forum moderator and some twitter feed that deals mainly in promotions is all we have heard. At the end of day 6, possibly in day 7ā¦
>
>
> To be fair, it is Halo Reach: a game that was release 6 years ago with a different company. 343 doesnāt have an infinite amount of man power to dedicate. Iām sure they have people looking into the issue
The game has an active playerbase, itās not Halo 4, and 3 is still going strong.
They could confirm that there is a guy actually working on it, even if heās busy reading documentation. Maybe get him to post quickly on the forums or something.
I get that not everyone works with software, so perhaps it isnāt obvious, but when something goes down and people notice, something ought to be done EVEN IF that something is:
> shrug itās 6 years old guys, we canāt be bothered, sod off to a different game
Itās still something.
Right now no one can plan around it, no one knows how long it might actually be, no one knows if checking it often or checking it once a day is worth it, so forth.
Also on the note of software, there should be automated backups, so when crap like this does happen you always have the worst case solution of:
> throw away the existing server (because thereās probably only the one) and write last weekās backup onto a new one
Youāve lost a week of stuff, but as itās not critical data, weād all live with it.
Iād be very surprised if (whoever made Halo: Reach) didnāt make it so you could just deploy an image to a server to yield more servers, This has been the norm since 2005 for matchmaking games because of off-peak and peak hours. When you need more matchmaking throughput, you just turn on more computers, point them at an OS image and let them run.
Something must have gone horribly wrong, or they were horribly incompetent but given the rock-solidness of Halo 2, 3 and ODSTās multiplayer and their love of reusing the same engine I really doubt that.
So yeah, you pay for a service (Xbox Live Gold) and a part of that is having an expectation that matchmaking works. Itād only be reasonable to expect them to take it down if like 2 people only played the game any more and there was no point. Reach is somewhere between 10-15k on peak times and 25k on weekends. Hardly dead.
So their job is to make sure we can play the game we paid for using the service that we also paid for; and theyāre not communicating with us about what theyāre doing so we can go back to doing our thing and they can go back to making more Destiny DLC or whatever it is these people do these days.
K?
