I'm honestly surprised that Microsoft of all Companies hasn't just virtualized their servers and tossed it on Azure to auto scale. If no-one is playing a game, the servers just wont spin up.
Halo 3 was the hypest launch of all time, hands down.I remember getting Halo 3 at midnight on launch day, going home, firing it up and watching the online players number on the main menu go from a few thousand to over a hundred thousand by 3 or 4am. Such a great gaming memory!
That's good to hear! Funnily enough I bought a 360 yesterday in a moment of nostalgia and it hasn't been shipped yet. Then I learned about this and I was like...god damn it! 😂Having lots of good matches on Halo 3. Hop on if y'all have the chance.
Finish the fight!Is it dead???? I can't get into anymore games :(
Edit: FINALLY GOT ONE AFTER 10MIN. LETS GOOOO
Nope, still going!I think it's finally over.
I'm getting the message that the Halo reach server is unavailable.
I had more fun with this one game than any other gaming purchase. Thanks Bungie/343
I was on Reach at the time of posting. Played a few hours of 3, then Reach with no problems. Trying Halo 4 now and that seems to be up as well upon first glance.
I was on Reach at the time of posting. Played a few hours of 3, then Reach with no problems. Trying Halo 4 now and that seems to be up as well upon first glance.
Oh I hadn't noticed that! Wait...that's cool, so Xbox 360 communities can still organize game nights and put together Custom Games, just no more matchmaking, file-sharing, etc.? That's actually not so bad.
As the image says.Oh I hadn't noticed that! Wait...that's cool, so Xbox 360 communities can still organize game nights and put together Custom Games, just no more matchmaking, file-sharing, etc.? That's actually not so bad.
Indeed. Basically the thing that shut down was Bungie's servers, not anything to do with Xbox Live. As the core of Halo 3's multiplayer (and others) uses Xbox Live's party service, the multiplayer itself is still working. The matchmaking (the system that organised match tickets to group players together in a playlist) however was an in-house bungie service which is why that shutdown.Oh I hadn't noticed that! Wait...that's cool, so Xbox 360 communities can still organize game nights and put together Custom Games, just no more matchmaking, file-sharing, etc.? That's actually not so bad.
Tell me about it. I had the fun job of migrating Quake's dedicated server protocol (the original DOS/Win Quake, that is) to virtualised servers. Getting them to launch? Fine, once we had container deployment working (though make no mistake, that was a real pain too, docker containers are hell to setup and we should have just used Windows servers to save on sanity). Getting any player to actually connect to them? I had to make changes to the code, deploy a build, find out if it 3 or more players could connect to it, then try again at least 5 times or more, until I finally had the networking migrated to allowed for virtualized port redirection. A thing the original code not only didn't know about, but actively was designed against entirely.Game servers have to be built with that in mind. Code base from the mid 00s cannot automagically do that.
Yes.Oh I hadn't noticed that! Wait...that's cool, so Xbox 360 communities can still organize game nights and put together Custom Games, just no more matchmaking, file-sharing, etc.? That's actually not so bad.
That's so good to hear. I'm curious was it the same for Halo 2? How long did Xbox Live continue running on the OG Xbox after matchmaking was shutdown?Yes.
The actual gameplay networking in 360 Halo games is entirely on peer-to-peer, and joining parties can (seemingly) be done solely via Xbox Live functionality. So the games should be playable online as long as Xbox Live is supported for Xbox 360.
Matchmaking and fileshare relied on centralized Halo-specific servers, which have been shut down.
Dude! That's wild. Thank you for the insight. It's always interesting to hear the trials and tribulations devs go through getting critical systems running smoothly that players often take for granted.Indeed. Basically the thing that shut down was Bungie's servers, not anything to do with Xbox Live. As the core of Halo 3's multiplayer (and others) uses Xbox Live's party service, the multiplayer itself is still working. The matchmaking (the system that organised match tickets to group players together in a playlist) however was an in-house bungie service which is why that shutdown.
Tell me about it. I had the fun job of migrating Quake's dedicated server protocol (the original DOS/Win Quake, that is) to virtualised servers. Getting them to launch? Fine, once we had container deployment working (though make no mistake, that was a real pain too, docker containers are hell to setup and we should have just used Windows servers to save on sanity). Getting any player to actually connect to them? I had to make changes to the code, deploy a build, find out if it 3 or more players could connect to it, then try again at least 5 times or more, until I finally had the networking migrated to allowed for virtualized port redirection. A thing the original code not only didn't know about, but actively was designed against entirely.
It was the same for Halo 2, seemingly, but the Bungie servers shut down the Halo 2 servers the same time the original Xbox Live service did, so it didn't exactly matter. People could still play multiplayer as long as they were already connected, for a few days.That's so good to hear. I'm curious was it the same for Halo 2? How long did Xbox Live continue running on the OG Xbox after matchmaking was shutdown?