Developer 343 Industries has been remarkably thorough and transparent throughout the process of porting the Halo: Master Chief Collection to PC, often releasing in-depth blog posts about the process. This week, community manager Tyler "Postums" Davis has posted an update on how the team handles bugs, from reporting to patching, after a bug-riddled release of Halo 2 Anniversary wreaked havoc on the Master Chief Collection.
While a lot of the discussion around game bugs is usually centered around the technical aspect of fixing them, Postums also goes into detail about how the community team is involved. As the first line of contact with the players, Halo's Community Team usually hear about bugs first, and often has to triage the seriousness of a newly reported issue. While this process also happens through Halo Support, the official tool for tracking and reporting bugs, players are just as likely to report bugs through forums, Discord, or in public social media posts.
Once identified, there's still a big process to go through before a bug can be fixed--one that ensures resources are assigned in the most efficient way. Testers look into details of a bug, finding out how and where it can be reproduced. When bugs are logged, they require details including "an outline of area, severity, description, reproduction steps, impact, expected results, media, and an assignment."Continue Reading at GameSpot