How do I set up a known-issues page for my game?

Build it for players, not as an internal dump. List the issues players actually encounter and ask about (crashes and visible bugs, not every minor internal ticket), include status for each (acknowledged, in progress, fixed next update) and any workaround so the page genuinely helps rather than just acknowledging, keep it current by marking issues resolved as you fix them so players trust it reflects reality, and link it prominently where players look for help, your support page, Discord, and store page. A good known-issues page deflects a large share of duplicate tickets for almost no maintenance cost.

What should a known-issues page include?

For each issue: a clear player-facing description of the problem, its current status (acknowledged, being worked on, or fixed in a coming update), and any workaround players can use right now. The description lets a player recognize their issue, the status reassures them you're aware and on it, and the workaround often resolves their need without a ticket at all. Keep the list focused on problems players actually hit rather than exhaustive, and keep statuses accurate, an out-of-date page that lists fixed bugs as open undermines the trust that makes it useful.

Does a known-issues page reduce support tickets?

Significantly, because a large share of tickets are players reporting or asking about problems you already know. A known-issues page lets those players self-serve: they find their issue, see it's acknowledged and being worked on, maybe find a workaround, and don't file a duplicate. The deflection depends on the page being accurate and findable, keep statuses current so players trust it, and link it where players look for help so they encounter it before reaching your inbox. For the small effort of maintaining one page, it's among the highest-return support tools available, especially for a small team.

Tips for Setting Up a Known-Issues Page

Quick answer: List the issues players actually hit, include status and workarounds, keep it current so players trust it, and link it where players look. A good known-issues page deflects duplicate support.

A known-issues page is one of the highest-return support tools for the effort: it deflects duplicate tickets, reassures players you're aware, and costs almost nothing to maintain. Here are practical tips for setting one up.

List the Issues Players Actually Hit

A known-issues page isn't your internal bug database, it's for players. So list the issues players actually encounter and ask about, the crashes, the visible bugs, not every minor internal ticket. A focused page of real, player-facing problems is what players will scan and find their issue on.

Bugnet groups crashes and ranks them by affected players, so you know which issues players are actually hitting and should list. A page built around the problems players really encounter, rather than an exhaustive internal dump, is what makes it useful as a self-service tool.

Include Status and Any Workaround

A bare list of bugs isn't that helpful, what players want to know is whether you're on it and whether there's anything they can do now. So include status (acknowledged, in progress, fixed in next update) and any workaround for each issue, which turns the page from a list into genuine help.

Status plus workarounds are what make a known-issues page deflect support rather than just acknowledge it, a player who finds their issue with a workaround often doesn't need to contact you at all. Including both is the difference between a useful page and a token gesture.

Keep It Current and Link It Where Players Look

A known-issues page only works if players trust it and find it. Keep it current, remove fixed issues or mark them resolved so the page reflects reality, and link it prominently where players look for help, your support page, Discord, store page. An accurate, findable page is what actually deflects tickets.

Bugnet's public tracker can serve as a known-issues page that reflects current status with little extra effort. So set up a known-issues page by listing real player-facing issues, including status and workarounds, keeping it current, and linking it where players look, deflecting a large share of support.

List the issues players actually hit, include status and workarounds, keep it current, and link it where players look. A good known-issues page deflects a large share of duplicate support for little effort.