MCC (Master Chief Collection) Server Incident Summary
halowaypoint.com
MCC (Master Chief Collection) Server Incident Summary
1–10 of 35 posts
Re: MCC (Master Chief Collection) Server Incident Summary
#2Really cool to see this level of transparency on an issue from a multiplayer game dev. Really cool write up
Re: MCC (Master Chief Collection) Server Incident Summary
#3I know we normally never hear about this stuff from game compaies at all, but it would be nice to have a little bit more detail.
> Finally, it was identified that there had been some updates behind the scenes to the servers we use to relay STUN traffic as part of the ICE process which had resulted in misconfigurations.
What updates? How were they tested (or not)?
Re: MCC (Master Chief Collection) Server Incident Summary
#4[deleted]
Re: MCC (Master Chief Collection) Server Incident Summary
#5Really cool to see this level of transparency on an issue from a multiplayer game dev. Really cool write up
Both Bungie and 343 have done an admirable job (well, compared to other devs) about explaining their network infrastructure etc. Back in the day they did a big talk about how their matchmaking in Halo2/3 worked that I think to this day is still one of the best methods of learning when you're not in the industry yet. I can't recall what it was called though: might be the "Chris Butcher - Recreating the LAN Party Online: The Networking and Social Infrastructure of Halo 2" GS talk but I can't listen right now to check
Re: MCC (Master Chief Collection) Server Incident Summary
#6Interesting that they call their service UDS. I was under the impression that they used PlayFab.
Re: MCC (Master Chief Collection) Server Incident Summary
#7The most interesting part of this to me is that they have a path, both in code and in process, to fallback to peer-to-peer if stuff breaks. That's pretty impressive.
Re: MCC (Master Chief Collection) Server Incident Summary
#8Interesting that they call their service UDS. I was under the impression that they used PlayFab.
MCC probably has an "interesting" architecture as it's a combination of Halo games that spans a few generations that makes something like playfab a bit too restrictive to work in.
Re: MCC (Master Chief Collection) Server Incident Summary
#9Anyone else having issues viewing this on Firefox? I can see the whole webpage for an instant, then everything disappears, then it is "slowing down my browser".
Re: MCC (Master Chief Collection) Server Incident Summary
#10Really cool to see this level of transparency on an issue from a multiplayer game dev. Really cool write up
Both Bungie and 343 have done an admirable job (well, compared to other devs) about explaining their network infrastructure etc. Back in the day they did a big talk about how their matchmaking in Halo2/3 worked that I think to this day is still one of the best methods of learning when you're not in the industry yet. I can't recall what it was called though: might be the "Chris Butcher - Recreating the LAN Party Onlin…
Only semi-related, but there was a recent excellent, short podcast interview series with one of Halo 2's multiplayer designers: https://smarturl.it/H2Pod