Forums / Community / Halo Insider

[Locked] MCC Development & Flighting Updates

OP Postums

Hey Friends,

It’s Friday which means we’re back with another mini-update to share the latest status on MCC PC development and where we are at for the next Halo Insider flight. If some of you have paid attention to my posts over on Twitter (1st and 2nd) and even last weeks news article, you have been gaining some insight into the process and where we have been tracking towards for flighting.

In case you are joining us for the first time, you can catch up on what has been going on over the past few months with these helpful articles:
Now that we are all caught up on what’s happened, let’s talk about where we are at right now.

Where are we at?
Currently, we have completed our Ring 2 testing and have verified that previous blocking bugs have been resolved. The Test Team received a new build yesterday and is currently working through a full verification of the build. If verification completes today, we will go to Ring 1 this weekend to verify the changes and assess readiness for the Ring 2. If all goes well there, we will continue in the following week moving through our rings. If no showstoppers are found – we will be able to move to Ring 3 soon once all previous Rings have been cleared. Below are a handful of bugs that have been resolved this week which were Ring 3 blockers.
  • Users were able to matchmake after editing various files
  • Soft Lock when pressing Alt + Tab while in full screen
  • Crash when loading into a match
  • Certain scenarios caused the Roster to disappear and not be accessible
  • Inviting a friend to play would cause the invitee to crash when accepting it
All of these are currently being verified by our internal team as being fixed now. We are looking good to go out to Ring 1 tonight and if verification that all critical bugs have been fixed and no new major issues present, this could be the build that goes out to Ring 3 soon barring no issues.

Looking Ahead!
Even though we are working on the FireFlight, we still have progress being made on the following flight to test out PvP. The key goals for the next one will be to validate Halo: Reach PvP networking within gameplay and through the matchmaking flow. This next flight is currently planned to be an Xbox One flight only. Below is the current spec for our first offerings for matchmaking we are working towards.

Social Games
  • Halo: Reach
    • 2v2 Matchmaking
      • Maps: Countdown, Powerhouse, and Zealot
      • Game Categories: Slayer
    • 4v4 Matchmaking
      • Maps: Countdown, Powerhouse, Zealot, and Tempest
      • Game Categories: Slayer, Flag and Bomb, Zone Control, Asset Denial, and Actionsack
    • 8v8 Matchmaking
      • Maps: Tempest, Breakpoint, and Ridgeline
      • Game Categories: Slayer, Flag and Bomb, Zone Control, and Asset Denial
Competitive Games
  • Halo: Reach
    • Reach Team Hardcore
      • Maps: Countdown and Zealot
      • Game Variants: Slayer and Capture the Flag
    • Invasion
      • Maps: Breakpoint
      • Game Variants: Invasion
We are excited for the future and are all hard at work bringing these games to all of you. Thanks for joining us and we look forward to chatting more with you in the following weeks!

Cheers,
Postums
Hello Halo Insiders,

Welcome back to another Friday mini update where we are going to discuss all the latest and greatest in MCC PC development as we march towards the next flight! The team has made a lot of progress this past week.

But before we begin, if you haven’t been following our previous updates, I highly encourage you to take a few minutes and get caught up on some important background info about the Halo Insider Program, public flighting, and the overall project itself. Consider this a pre-requisite and required reading before you get any further in today’s blog:
Now that you have gotten through all that light reading, let’s get into some new goodness.

Where are we at?
Yesterday, we shared our current proposed build for Ring 3 to our Ring 1 & 2 users. Testing went quite well over the evening with improvements being seen over past builds.

This is the same one that was streamed on Wednesday’s 343 Social Stream. If you missed that, please feel free to check out the VOD HERE. The Reach goodness starts around the 28-minute mark.

As it stands right now, all Ring 3 blockers are currently resolved, and we are very close to getting the build out to the Halo Insiders. The current snag we are working through involves how we support the flight roll-out. These issues were identified early in the day, and some have been resolved, but not all. The good news is that we are very close and once all our ducks are in a row, we will be able to get the party started!

Thank you everyone for waiting patiently. I know we can’t wait to get this out into your hands to try out shortly!

Cheers,
Postums
Good Morning Halo Insiders,

In case you haven’t heard about it, you still can register for the Halo Insider program. Sign-ups are always available if you want to participate in future flighting for Halo titles. Currently flighting is focused on Halo: Reach as part of the Halo: The Master Chief Collection, but it will also serve as a testing ground for all titles that make up the Master Chief Collection.

What does the Halo Insider program entail? How does one sign-up (or opt-out)? Get the answers to these questions and many more on the Registration page HERE, or in the Insider forums HERE.

In addition, if you haven’t been following our previous updates, I highly encourage you to take a few minutes and get caught up on some important background info about the Halo Insider Program, public flighting, and the overall project itself. Consider this a pre-requisite and required reading before you get any further in today’s post:
Now that you have gotten through all that light reading, let’s get into some new goodness.

Flight Two – FireFlight
When undergoing major updates such as adding an entirely new game to MCC or bringing MCC to PC, a critical component in this process is to get community involvement early and often. This means you to get hands-on time to play, test, and provide feedback for our in-progress builds via the Xbox Insider app on console and via Steam on PC.
Since the conclusion of Flight One the team has been working on the next, affectionately dubbed FireFlight. Today we are happy to say that this flight number two will begin today!

Participants
Invites have started to roll out for the FireFlight participants that have been chosen. With this flight, the team has increased the size of the user pool to 10,000 invitees. Those who were invited to Flight One may have not received an invite again to this flight as the requirements the team has chosen for participants has changed.
However, even with this bigger group, most of the overall Halo Insider population will still not be included quite yet. For Flight Two we’re continuing to intentionally limit the number of users as we gradually ramp up in size and scope to appropriately test various hardware configurations, operating systems, and other various scenarios we are looking to test at scale. Should you not be invited this time, we sincerely appreciate your interest and eagerness to help. There is more to come.

Scope
In the Halo Insider MCC Flight One we focused entirely on the Halo: Reach campaign mission, Tip of the Spear. For the second PC flight we will be focusing on verifying Firefight and Firefight matchmaking at scale.

Maps
  • Beachhead
  • Corvette
  • Holdout

Firefight Playlists
During this flight we will rotate two different Firefight playlists throughout the duration with only one available at any given time.
  • 4-player Heroic standard Firefight
  • 4-player Normal grab bag Firefight
As with all flights, keep in mind that this represents a snapshot of an in-progress build at a specific moment in time – which is not as current as what’s being actively developed at this very moment. Flights are also clearly limited in scope which means many of MCC’s features and broader offerings are not included. Participants will want to check out the “Known Issues” post on Halo Support for the latest and greatest details to be aware of for this flight.

Feedback
In conjunction with the Halo Insider MCC flights, we are also beta testing the all new Halo Support site. This is a new site that allows you to learn about known issues and how to troubleshoot them. It also provides a forum to discuss feedback you have around the game, and lets you submit support tickets for technical issues that have not been previously reported. To learn more about the Halo Support site, please take a look at this post all about it HERE.

Those who are participating in the MCC flights will be granted access to the Halo Support site using that same account that they registered with for Halo Insider. If you have feedback during the flights, please take some time and post in the Community section over on the Halo Support site. Otherwise, we look forward to getting your thoughts as part of the survey that will come after the flight has concluded.

Dates & Play Sessions
  • August 24, 10:00 AM PT - 1:00 PM PT & 5:00 PM PT - 9:00 PM PT
  • August 25, 10:00 AM PT - 1:00 PM PT & 5:00 PM PT - 9:00 PM PT
  • August 26, 10:00 AM PT - 1:00 PM PT & 5:00 PM PT - 9:00 PM PT
This flight has gone live today, Saturday, 8/24, as we set our cruising altitude for the duration of the weekend. We will come in on our final approach on Tuesday, 8/27 before clearing all rows at 10 AM PT and sending out a survey in the following day or two asking users about their experience for the duration of the flight.

The FireFlight invites to all participants have begun rolling out at 10AM this morning. So, check those inboxes (spam folders included) and get ready! Thank you everyone who has registered to participate and to those who are invited. Your time and efforts along with your feedback are helping to shape MCC on PC! Next week, we will discuss how the flight went and start ramping up discussions around the next planned Xbox One PvP Flight the team will shift focus over to.

Cheers,
Postums
Hello Halo Insiders,

Today’s update on flighting is going to be quite brief.

Where are we at?
Well, a new blog dropped last week right HERE. In that blog we talked a little bit about three things as it related to flighting.
  • FireFlight had come to pass
  • There were some inner discussions of a FireFlight 2.0
  • Looking ahead to the first Xbox flight for Halo: Reach which would be PvP focused
We have some updates on these points today.

FireFlight 2.0
With bleeding edge transparency often comes pivots and changes on the drop of a dime. Prior to analyzing all the data of our Fireflight we thought we might end up needing to conduct a second one. However, after further investigation, we identified the information we needed to properly evaluate our goals from the results we had collected. This means, we have decided to not conduct a follow-up FireFlight and press onwards, to focus on PvP flighting.

Xbox PvP flight
I was in a meeting this week (Thursday 9/5) where we discussed the status of the Xbox build. Currently the team is working through determining which build they would like to branch with, to begin hardening for the next flight. QA runs daily tests and the team is reviewing reports on the most recent builds to assess which features/bug fixes they would like to be in before the first branch.

For those who are like, “why is he talking about trees?” that is a very fair thought, let me explain.

In the code world, you can create what is called a “branch” which at the time of its creation can be a carbon copy of the core code for a project. But after that branch happens, the code is isolated from your main project. This allows you to fine tune, to pick and choose, what pieces you want pulled into it. Branching for a flight is one of the core steps for each flight to lock everything down and work to more easily stabilize the code base. This concludes my Ted talk. Back to news!

Once a branch is successful, the team will do a full evaluation of the proposed candidate and begin gathering the top issues they would like to resolve in preparation for flighting! Currently, the team has only conducted tests internally to Ring 0. I look forward to discussing the Xbox PvP flight build more next week.

Until next time, we’ll see y’all online!

Cheers,
Postums
Hey Friends,

Back again with another update on how flighting is shaping up. I touched base with the QA team to be brought up to speed on all the issues that were submitted by those who participated in the FireFlight. As well, I talked to the team about the next planned flight for Xbox One which will be Halo: Reach Matchmaking. All the juicy details can be found below!

FireFlight Bugs Recap
From the last flight, we had over 400 issues get reported by the community. There were many duplicate reports of the same problem users were encountering so the unique was much smaller in comparison. Below are the top issues that were reported by count.
  • Stability issues on launch, match start, and match end
  • Settings not working as intended
  • Audio issues
  • Intermittent freezes and enemy display issues
All of these issues are being investigated by the test team and have bugs logged against them to have additional information entered to be fixed in the future.
Below is a full list of issues reported by the community that have already been fixed. Thank you for sharing all the information!
  • Exiting out of settings menu guns continue to fire
  • UI had multiple medal displays
  • Game incorrectly gives “host disconnected” message in certain network situations
  • Picture in picture on weapons like scopes do not match up with view
  • Players could get locked in menus after selecting various sub-menus
  • Death screen camera sensitivity is too slow
  • You could run faster running diagonally while holding the turret
  • Misspellings in the “Change Profile” description
  • Using an Xbox controller can cause crashes
  • When hovering over the roster it is in focus, but when moving away from it, it stays highlighted
  • Firefight Matchmaking menu had placeholder titles
  • Brutes seem to drop invisible armor lock pickups
  • Text sometimes appears as “Breadcrumb text Breadcrumb” instead of “Choose Game Type”
  • During match, UI offset on Ultrawide monitor is present.
Again, thank you so much for all the feedback that you have had! We are excited to hear about things you had issues with so we can put as much polish on the features we have as possible.

Xbox PvP Flight
Currently the team is still working to identify the best build to branch from right now. There are a handful of key bugs they are waiting to get fixed as well as pieces of content that may or may not make it into the flighting build. As bugs are fixed and additional work is happening, they may wait a little bit longer to get some key features in so more systems can be stressed and looked at by the community as they come online.

Currently the team has been having regular Ring 0 play test, which means internal testing only for feedback and stability checks so far. Once a branch build is identified, we will be able to move towards flighting and work through any bugs we have backlogged that are blockers. As we move into the following week, we will have more progress updates to share on the status of flighting as we get ready to push towards the PvP flighting.

Until next time, we will see y’all online!

Cheers,
Postums
Hey Friends,

This week the team has continued working on the Xbox PvP build for our next upcoming flight. So far, all core systems required for the flight to happen have been completed. A new build from the branched state was kicked off Thursday and made its way into test today. The team still has a couple isolated bugs that they are working through which are deemed ring blockers, but this week they went from 10 down to 2 blocking bugs so far. But before anything can even move forward from bug fix to flight, the team must isolate the content for the next flight and trim the build down to just the content wanting to be shipped out for it.

Xbox PvP Flight Ring Status – Ring 0
Right now, there is 1 Ring 3 blocker and 1 Ring 1 blocker that have been identified within the build that is in test.
  • Title Softlocks after completing a match
  • Reach Multiplayer installation issues
Once these have been fixed, and the build has been locked down to the planned content, things on that front will be moving forward quickly!

Please Delete Old Xbox Insider Builds
To those who have participated in previous Xbox Insider flights on the Xbox and still have the old ones installed, you will want to delete these entirely from your Xbox. This will help alleviate some issues that may arise if you try to update that old build to the next flighted build. A fresh install of the next flighting build is what you will want to do.

Xbox Flighting Differences
One key difference from Xbox and PC is the delivery method for the game. With flighting that was conducted previously on Xbox for MCC’s prior game updates, the setup was slightly different to how testing is being conducted now. The last series of flights on Xbox were setup to allow for anyone who owned MCC on Xbox to have access to it via the Xbox Insider program. We still will continue to use that program, but in order to target only the select Halo Insiders we want to have access, we have had to remove that setup and the satisfying entitlement flow for testing.

With the Setup being taken down, it required rebuilding the pipelines and requirements from scratch for our new flow of how we test builds. The great news is our partners have worked closely with us to ensure all is set back up properly and will be good to go as soon as we are ready to move into our first Ring 1 test soon. We are targeting next week to enter into Ring 1 testing.

As we move closer to the Xbox PvP flight and the Ring 1 testing, we will give more updates on how things are going. Stay tuned!

Cheers,
Postums
Welcome back Friends,

This week we are on the bleeding edge of entering our next public flight. The team is currently day-to-day on getting the go-ahead to put out the next flight. The current plan of record is as soon as all blocking bugs are resolved and it has made it through the Ring 1 testing, we will look to move to Ring 3. But before we get into where we are at status wise, we want to remind everyone to delete all your old Halo: MCC Insider builds on Xbox!

Please Delete Old Xbox Insider Builds
To those who have participated in previous Xbox Insider flights on the Xbox and still have the old ones installed, you will want to delete these entirely from your Xbox. This will help alleviate some issues that may arise if you try to update that old build to the next flighted build. A fresh install of the next flighting build is what you will want to do.

Let’s hop on over to see where the team is at right now!

Xbox PvP Flight Ring Status – Ring 1
Right now, there is currently 2 Ring 3 blockers that have been identified within the build that is in test. This week the team has been working actively in the flighting branched build, a paired down the build to be the exact content we want to target for the flight. This branched build has allowed rapid iteration on issues and the team has tackled many bugs over the course of the week.

In great news, all Ring 1 blockers have been resolved this week and later this evening the team will be pushing the latest build out to our Ring 1 participants. The teams will be in over the weekend also testing and resolving Ring 3 blockers in hopes of flighting to Ring 3 as early as next week. The below issues are currently active bugs that the team is working through prior to a public flight and are the only identified Ring 3 blockers as of now.
  • Forge menu loses functionality after closing the PGCR.
  • Halo: Reach Multiplayer is not installed properly in some scenarios
Once these have been fixed and Ring 1 testing is successful, we will plan to get this next flight out quickly. No promises or dates, but things are looking good for as early as next week if all goes well over the weekend. Thank you for swinging by and checking out the latest info for flighting! We can’t wait to get this flight out to our Xbox users. Once this next flight wraps up, we will be working rapidly to our last planned flight over on PC for PvP!

Cheers,
Postums
Hey friends,

Welcome back to our regularly scheduled Friday flighting updates. October is a busy month in terms of flighting for sure! Last week we wrapped up our Xbox One Multiplayer flight for Halo: Reach and we are moving full steam ahead on getting the next PC flight out the door as well. Below are updates on both. Before I dive in, if you haven’t recently updated your Halo Insider profile, please go HERE and make sure you have done the following:
  • Verified your email
  • Opted into communication
  • Opted into PC flighting
  • Provided an updated DxDiag
To be considered for a flight, the first two must be true and the third simply helps us select from the latest and greatest configurations for PCs including OS versions. Let’s dive on in!

Xbox One Flight Recap
Early on in October we flighted Halo: Reach’s Multiplayer on the Xbox One. This flight’s main goals were to test the backend and each of the matchmaking offerings that are going to be available when MCC comes to PC and Halo: Reach joins MCC on the Xbox One. We invited significantly more Halo Insiders to play Halo: Reach than any previous flight. A few different user groups were selected with different criteria. One included a percentage of users from previous Halo Insider flights and actively participated. Also, many users were selected who had not received invites previously. A second, more specific, set of users with high engagement in MCC over the past 90 days was also curated in case we needed to expand our flight to reach goals we had set.

We invited approximately 50k users who have registered for the Halo Insider program. Beyond that, we manually added just over 100 individuals for this flight ranging from streamers, content creators, professional gamers, casters, and other individuals who are vocal about Halo. Their numbers are a mere drop in the bucket compared to who was chosen by specific criteria.

With this flight, we sent invites out in waves to test engagement and better understand who would participate at what rates. This roll-out not only allowed us to validate our theories, it helped us reach the goals we set internally. After the first round of invites, we saw low engagement levels and made the call to double the audience and invite even more players. As we opened the floodgates and expanded invites, we did push our flight services to the limit and even saw a brief moment of (expected) instability as a result where new dedicated server instances were having a hard time keeping up. This is to be expected and is only an issue given the intentionally limited scope for a flight environment.

One mistake we did make (and have since rectified) is we selected users who had not verified emails. So even though we chose you, we couldn’t email you to let you know you were invited! Please make sure you verify your email and opt in for communication in the Halo Insider program. Help us help you!
Additionally, there was an extra special stress test where we asked folks to come out Saturday, October 5th to help us put Halo: Reach’s updated networking to the test. Thank you, Spartans, as you did not disappoint!

We hit our goals, and then some, for concurrent users playing that day (nearly 4x over!) and were able to effectively test the new infrastructure brought online to help support MCC for the future of the title. Your time playing helped us effectively see how leveling worked during the flight and verified that our progression system worked as intended at scale.

All in all, this test was very successful, and we are excited to say that quite a few folks showed up and played lots of matches during the stress test. In total 3,720 users played 5 or more matches, and as a thank you, received the MCC Insider nameplate. On top of that, 1,713 additional folks hit the bar of completing 12 matches during the stress test’s time window earning themselves the MCC Insider Pro nameplate. Thank you to everyone who came out and participated so much. Your efforts are very much appreciated and are helping us shape Halo: Reach!

That being said, there were quite a few folks that went above and beyond in terms of participation. Below are the top 10 players from this flight who all played well over 200 matches during the flight. The top 3 though went all-in and put in over 300 matches. The top player, Bound, took top marks and was the only one to break 400 games played, completing a total of 429 matches!
  1. Bound
  2. Mint Blitz
  3. Rammyy
  4. LUKEPOWA
  5. Fazel 2
  6. ASS1STED
  7. Reclaimants
  8. The DiZZeL
  9. Th3 LiE
  10. MrJaycoooo
We can’t state enough how much we appreciate everyone’s efforts in helping us to test this flight so extensively. As a token of our appreciation for playing near constantly through entire duration of the flight, if you see your gamertag in the list above, we have granted you each an extra special nameplate for your efforts. Thank you!

As one final note to all participants, you can go ahead and delete the old MCC Insider build from your console. This build will not be used again and any flight in the future for Xbox will require it to be deleted.

Update DXDIAG and Verify Email
Before I jump into anything around this, please take some time right now and go update your Halo Insider profile if you haven’t recently with a new DxDiag, ensure you have opted into PC flighting, and have a verified email that we can contact you at! We need this info to help target specific goals we are trying to reach in our upcoming PC flight.

I know this is the third time I’m asking, but literally please click HERE and do it now. I swear it’s the last time I will ask in this post. Now back to our regularly scheduled update!

PC Flight Update
The team is moving very rapidly preparing for the next Halo: Reach flight. Yesterday we received our first branched build for the next PC flight, and it has been getting hammered on internally with our 2nd Ring 0 test happening today. The teams will be in over the weekend hammering away identifying any blocking issues to resolve prior to going to Ring 1 & 2. If no issues are found, the team plans to go out to Rings 1 & 2 on Monday. Our goal is to get this flight out as quickly as possible, so hang on to your seats!

This PC flight, in terms of scope, will have the most content to date for players to enjoy. This flight includes two campaign missions, multiple offerings for social and ranked matchmaking, custom games, and Firefight matchmaking. All types of content will be available over the course of the flight – which we anticipate will last a week – but select offerings for Multiplayer and Firefight matchmaking may change.

Campaign Missions
  • Noble Actual
  • Winter Contingency
Firefight Matchmaking Offerings
  • 4-player Heroic standard Firefight
    • Beachhead
    • Corvette
    • Holdout
  • 4-player Normal Arcade Firefight
    • Beachhead
    • Corvette
    • Holdout
Multiplayer Matchmaking Offerings
  • 2v2 Social: Slayer
    • Countdown
    • Powerhouse
    • Zealot
  • 4v4 Social: Slayer, Flag and Bomb, Zone Control, Asset Denial, and Action Sack
    • Countdown
    • Powerhouse
    • Zealot
    • Tempest
  • 8v8 Social: Slayer, Flag and Bomb, Zone Control, and Asset Denial
    • Tempest
    • Breakpoint
    • Ridgeline
  • Halo: Reach Team Hardcore: Slayer and Capture the Flag
    • Countdown
    • Zealot
  • Halo: Reach Invasion
    • Breakpoint
Closing
As we get closer to the flight’s target date, more information will be shared out in terms of days it will span, what offerings will be present on what days, and all the additional details we know you want. Please stay tuned and we will catch y’all online!

Cheers,
Postums
Hello Friends,

I’m going to keep this week’s flighting update short and snappy because we are on the cusp of putting out our final scheduled flight for MCC on PC! But, if you haven’t updated your profile recently for the Halo Insider program, go do it now. This means verifying your email, updating what platforms you are interested in, and if you select PC – update your DXDIAG. It’s in your best interest to always keep this up to date, I promise!

This week the team has been flighting to our Ring 1 & 2 user groups outside of the studio. If you don’t know what Ring 1 or 2 means, please read THIS article I penned a few months back explaining it all. For those who know, we only have a couple blocking issues we are working through right now preventing us from going out to Ring 3.

Best case scenario, they will be fixed in a new build over this weekend and the flight goes out early next week! Worst case, the flight starts later once the issues are fixed. I don’t have an exact timeline as we are quite agile when it comes to flighting and fixing bugs. Regardless, below is some info about the flight, the offerings and the daily plan.

Flight Three Goals
The primary goals of this flight are to test matchmaking on PC for both the Steam and Windows Store versions. This flight will include Crossplay between the two versions and we are excited to see how it goes. We are also looking to gather feedback from players on the updates that have been made.
This flight will also include the work in progress Season 1 so you can play around and begin customizing your character in game. The teams working on the project have made many bug fixes since the previous flight and are looking to hear what areas we can continue to improve on and gather your precious feedback.

PC Flight Content
The content for this flight includes two campaign missions, multiple offerings for social and ranked matchmaking, custom games, and Firefight matchmaking. During each play session you will be able to play using a keyboard and mouse (or with a gamepad should you choose), on your PC. All three types of content will be available over the course of the flight but select offerings for Multiplayer and Firefight matchmaking will change daily. Please see the next section for daily matchmaking options.

Campaign Missions
  • Halo: Reach Campaign Missions: Noble Actual and Winter Contingency.
Firefight Matchmaking Offerings
  • 4-player Heroic standard Firefight: will be played on Beachhead, Corvette, and Holdout.
  • 4-player Normal grab bag Firefight: will be played on Beachhead, Corvette, and Holdout.
Multiplayer Matchmaking Offerings
  • 2v2 Social: Slayer will be played on maps Countdown, Powerhouse, and Zealot.
  • 4v4 Social: Slayer, Flag and Bomb, Zone Control, Asset Denial, and Action Sack will be played on Countdown, Powerhouse, Zealot, and Tempest.
  • 8v8 Social: Slayer, Flag and Bomb, Zone Control, and Asset Denial, will be played on Tempest, Breakpoint, and Ridgeline.
  • Halo: Reach Team Hardcore: Slayer and Capture the Flag will be played on maps Countdown and Zealot.
  • Halo: Reach Invasion: Invasion will be played on the map Breakpoint. Our flight goal is to test our PvP matchmaking and get your feedback, so be sure to load in and play with us!
Flight Schedule
Each day of this flight will have one unique offerings for playlists in social, ranked, and Firefight matchmaking. This is our preliminary schedule for the days of the flight, but the final schedule will be a part of the emails when they go out. Try to play during the scheduled sessions as this will be your best bet to find a match!

Day 1
  • Social: 4v4
  • Competitive: Team Hardcore
  • Firefight: Arcade
Day 2
  • Social: 8v8
  • Competitive: Team Hardcore
  • Firefight: Heroic
Day 3
  • Social: 2v2
  • Competitive: Invasion
  • Firefight: Arcade
Day 4
  • Social: 4v4
  • Competitive: Team Hardcore
  • Firefight: Arcade
Day 5
  • Social: 8v8
  • Competitive: Team Hardcore
  • Firefight: Heroic
Day 6
  • Social: 2v2
  • Competitive: Invasion
  • Firefight: Arcade
Day 7
  • Social: 4v4
  • Competitive: Team Hardcore
  • Firefight: Arcade
Day 8
  • Social: 8v8
  • Competitive: Team Hardcore
  • Firefight: Heroic
The duration of the flight is subject to change but may be 8 days. After 1:00 PM PT on the final day, matchmaking will become unavailable. So, if you have been invited, be sure to hop online and jump into the action for any of the listed offerings. The final schedule will be available in the emails sent to those who are invited. We hope you enjoyed this update and look forward to flighting real soon!

Cheers,
Postums
Happy Friday Friends,

And welcome back to another weekly flighting development update! This week will actually be very light as we are currently flighting! Full details for scheduled play sessions and content for the current Halo Insider MCC Flight Three can be found in this post HERE. Over the past few days we have sent waves of invites out to folks who have been invited to participate. As of just a few hours in fact we sent out an additional 10k invites, so be sure to check your emails (spam folder too) to see if you have access to jump in on the last scheduled flight for Halo: Reach.

After flighting wraps up, we will take a more in depth look at what we found out from our end as well as review some of the feedback and issues the community has collectively called out for us from this flight. So stay tuned! Thank you for stopping in and as always, we'll see you online!

Cheers,
Postums