A report surfaced this week confirming that Epic Games regularly purges its backlog of low-priority bug reports for Fortnite, and CEO Tim Sweeney didn't deny it. His response on X was direct: yes, they delete them, and no, he doesn't think that's a problem.
Sweeney's case for cutting the backlog
Sweeney's position is straightforward. Epic prioritizes bugs by impact, works through them in order, and draws a line somewhere near the bottom. Anything below that line, the stuff that affects very few players and carries minimal consequence for the experience, gets dropped. "We find the cutoff point where fixing those bugs is less valuable to the game than other things, and we drop them," he wrote on April 10.
He was also clear about what doesn't get deleted. Bugs that a significant portion of the playerbase actually encounters, the ones that genuinely hurt Fortnite's quality, are treated as higher-priority items and stay on the list until resolved. The slow fixes in that category, Sweeney says, come down to complexity, not neglect.
His framing of all this as "normal software development" is worth taking seriously. Fortnite is one of the most-played games on the planet, running across PC, console, and mobile simultaneously. The volume of bug reports it generates is almost certainly enormous, and maintaining a perpetually growing backlog of issues nobody will ever fix does carry real overhead costs.
info
Sweeney specified that widely-experienced bugs affecting game quality are never among the low-priority reports that get wiped. Those remain assigned to the team until fixed.
Facepunch's counter: log it anyway
The more interesting response came from Alistair McFarlane, COO and company director of Facepunch Studios, the team behind Rust. His studio takes the opposite approach. Rust's bug backlog reportedly runs into several hundred low-priority entries, some dating back years, and Facepunch has never deleted them.
McFarlane outlined three practical uses for keeping old, low-priority reports around. First, dedicated cleanup sprints let the team tackle them in bulk when capacity allows. Second, QA staff can work through them independently. Third, and this is the part that stands out, they serve as starter tasks for new hires, giving incoming developers something concrete to fix while they get familiar with the codebase.
That last point is genuinely smart. A bug that's been sitting untouched for two years isn't necessarily a waste of space if it eventually becomes the thing that helps a new engineer understand how Rust's systems connect.
McFarlane acknowledged the counterargument. "I can see the logic in deleting them," he wrote, before landing on his actual preference: "I'd rather have them logged than forgotten."
Facepunch keeps years of bug logs
The scale problem neither side fully addresses
Here's the thing: both positions make sense, and the right answer probably depends entirely on team size and game scale. Facepunch is a much smaller studio than Epic, and Rust, while a long-running survival hit with a loyal playerbase, doesn't operate at Fortnite's volume. Managing a few hundred old bug reports is a very different proposition from managing tens of thousands.
What most players miss in this conversation is that bug triage is itself a form of development work. Every entry in a tracker has to be reviewed, categorized, and periodically re-evaluated. At a certain scale, the overhead of maintaining a massive low-priority backlog can actually slow down the resolution of the bugs that matter.
The key here is that neither studio is ignoring player-facing issues. Both Sweeney and McFarlane made that point in different ways. The debate is really about what you do with the long tail of minor, low-impact reports that accumulate over years of live service.
For a closer look at how live-service games handle ongoing development and updates, browse more guides covering the biggest titles in the space. And if you want to stay across the latest gaming news and industry conversations as they develop, there's plenty more worth reading.
