Quick answer: Publish a clear, player-facing changelog for every update, written in plain language about what changed, including fixes and known remaining issues. A reliable changelog proves over time that you ship steadily, listen to reports, and tell the truth, which is exactly what earns lasting player trust.
A changelog seems mundane, but kept well it becomes one of your most effective trust-building assets. Every entry is evidence that you are actively working on the game, that player reports lead to fixes, and that you communicate honestly. A reliable, readable changelog players can browse compounds into a reputation for responsiveness and transparency, while a neglected one, or none at all, quietly signals the opposite.
A Changelog Is a Trust Record
Each changelog entry is a small proof point. 'Fixed the save bug players reported' shows that reporting works. A steady stream of entries shows the game is alive and cared for. Over months, the changelog becomes a visible history of your responsiveness, the single clearest evidence a prospective or current player has that you ship fixes and listen to feedback. That accumulated record is worth far more than any single announcement.
The absence of a changelog, or a long gap in one, sends the opposite signal: a game that might be abandoned, a developer who might not be listening. Keeping the changelog current is keeping that trust signal alive.
Write It for Players, Not for Yourself
A changelog only builds trust if players can understand it. Write entries in plain language about what changed from the player's perspective, 'fixed a crash when entering the second dungeon', not 'patched null deref in DungeonLoader'. Players should recognize the bugs they reported and the improvements they care about. Internal, code-level changelog entries are invisible to the people whose trust you are trying to build.
Lead with what players care about, the fixes for issues they reported, the improvements they asked for, and keep the technical minutiae brief. Crediting reporters where appropriate, 'thanks to everyone who flagged this', turns the changelog into acknowledgement as well as record.
Keep It Honest and Consistent
Two things make a changelog trustworthy: honesty and consistency. Honesty means including the known issues that did not get fixed and not overstating what an update does, a changelog that claims everything is perfect when players can see otherwise destroys its own credibility. Consistency means an entry for every update, on a predictable cadence, so players learn they can rely on it to know what changed.
Make it easy to find and browse. Bugnet's public changelog gives players a clean, persistent release history tied to the issues you fixed, so the link between their reports and your updates is visible at a glance, and the whole record of your responsiveness lives in one place they can check anytime. A changelog kept honest and current is a trust machine that runs on the work you are already doing.
A changelog is a trust record that compounds. Keep it honest, plain, and consistent, and it pays you back for years.