Epic Games periodically purges its backlog of low-priority bug reports for Fortnite, a practice CEO Tim Sweeney defends as standard industry procedure, despite pushback from industry peers.
The Epic Games Approach to Bug Management
According to CEO Tim Sweeney, Epic Games maintains a strict hierarchy for software issues. When bug reports are filed, they are categorized by importance and impact. Reports deemed low-priority are eventually cleared from the system once the company determines that fixing them yields less value than focusing on other development tasks.
Sweeney addressed the controversy on Twitter, labeling the periodic deletion as “normal software development.” He clarified that this process strictly excludes widespread issues that impact player experience or game quality. Sweeney noted that when significant bugs persist, it is due to the technical complexity involved in tracking, patching, and deploying fixes rather than a lack of prioritization.
A Different Philosophy at Facepunch Studios
The developer-led debate gained traction when Alistair McFarlane, COO of Facepunch Studios, offered an alternative perspective based on his work with Rust. Unlike Epic, Facepunch opts to maintain a comprehensive, multi-year backlog of bug reports.
“Our backlog on Rust is usually several hundred low-priority bugs—many are bugs to us rather than players—but we never deleted them,” McFarlane tweeted. He explained that these reports serve as valuable resources for “cleanup sprints,” allowing QA teams to address lingering issues or providing new staff members with a way to familiarize themselves with the project’s codebase.
While McFarlane acknowledged that maintaining such a massive list can become a “burden on QA,” he emphasized that he would “rather have them logged than forgotten.”
The Industry Divide
The clash in methodologies highlights a fundamental difference in how studios manage technical debt. While Epic Games manages an immense volume of incoming reports daily, necessitating aggressive pruning to maintain focus, smaller or different-scale teams often leverage historical data as a learning tool.
Ultimately, the effectiveness of either strategy remains tied to the end result: the quality of the player experience. Whether a studio chooses to wipe the slate clean or meticulously archive every minor flaw, the primary metric for success remains the successful resolution of issues that matter most to the community.
Leave a Reply