Where should I post my game's known issues?

Where players go when something breaks: a pinned Discord message, a store-page link, an in-game notice, or a public status page. A dedicated public tracker that shows acknowledged issues and their status lets players self-check without contacting you, deflecting duplicate reports.

Does a known-issues list reduce duplicate bug reports?

Significantly. Every player who sees their bug already listed skips filing a duplicate and skips the frustrated review. The list deflects redundant reports while visibly proving you are aware and working on the problem, doing double duty for almost no ongoing cost.

How often should I update my known-issues list?

Whenever status changes, acknowledged, fix in testing, fixed. A stale list that still shows fixed bugs as open, or omits the issue everyone is hitting, destroys its own credibility. Move resolved items to a 'recently fixed' section so waiting players can confirm their issue is handled.

How to Let Players Know a Bug Is a Known Issue

Quick answer: Maintain a visible known-issues list, pin it where players look, and update it as status changes. A public known-issues page cuts duplicate reports, reassures players you are aware, and turns 'is this a known bug?' into a question that answers itself.

When a bug hits many players at once, you get the same report dozens of times, each from someone who has no way of knowing you already know. A visible known-issues list solves this on both ends: it tells players you are aware and working on it, and it dramatically reduces the flood of duplicate reports you would otherwise have to triage.

Why a Known-Issues List Pays for Itself

Every player who checks a known-issues page and sees their bug already listed is a player who does not file a duplicate, does not leave a frustrated review, and does not assume you are asleep at the wheel. The list does double duty: it deflects redundant reports and it visibly demonstrates that you are paying attention.

It also changes the emotional tone of hitting a bug. "This is a known issue, a fix is coming" turns a moment of frustration into a moment of reassurance. The player feels informed instead of stranded.

Put It Where Players Actually Look

A known-issues list nobody can find helps nobody. Surface it where players go when something breaks: a pinned message in your Discord, a link on your store page, an in-game notice, or a dedicated public status page. The easier it is to find, the more duplicate reports it deflects.

Bugnet's public tracker and roadmap pages double as a known-issues board: you mark an issue acknowledged and it appears publicly with its status, so players can check whether their bug is already on your radar without contacting you at all. You maintain one list and it serves every player.

Keep It Honest and Current

A known-issues list only works if it is trustworthy. List the real issues, including ones that are inconvenient to admit, and update status as things change: acknowledged, fix in testing, fixed in 1.4. A stale list that still shows fixed bugs as open, or omits the bug everyone is hitting, destroys its own credibility.

Move resolved items to a 'recently fixed' section rather than just deleting them, so players who were waiting can confirm their issue is handled. The list becomes a living record of responsiveness, not just a list of problems.

A known-issues page answers the question before the player has to ask it.