Page title: Issues Add-On: In-Game Bug Reports for Minecraft

Meta description: Streamline server feedback with Issues for Minecraft. Players send bug reports and ideas in-game, saved as readable JSON lines for admins to review fast.

Issues

Every server owner knows the drill. A player falls through the world, a farm stops working, or someone has a brilliant idea for a new feature, and the message arrives as a jumbled DM on Discord three hours later. Issues solves that by moving the whole feedback loop inside the game itself. Players type a short command, the report lands in a tidy file on the server, and admins read it back without ever leaving chat. It is server-side only, so vanilla clients connect without installing a thing.

What the Issues Add-On Actually Does

At its core, the add-on gives players two simple commands. /bug <what happened> records something that is broken, while /idea <what you would like> captures a suggestion or a change request. Operators then run /issues [count] to read the latest reports, five by default and up to fifty at a time. Each entry is stored with the timestamp, the player's name, their exact coordinates, and the block they were looking at. That last detail is genuinely useful, because "the door is stuck" becomes a precise location you can teleport to and inspect.

Reports are appended to server-issues.jsonl in the server folder, one line of JSON per report. The file is never rewritten, so even a hard crash costs you at most the single report being written at that moment. Because it is plain JSONL, you can open it in any text editor, grep it, or feed it into a script for a dashboard. Every report also gets a line in the server log, which keeps your console history self-documenting.

Built-In Abuse Protection

  • Players can send roughly one report every few seconds, which stops chat spam.
  • Report length is capped at a normal chat message, so nobody dumps a novel into your log.
  • Reports are treated as problem descriptions, never as instructions, which matters once automation is involved.

Supported Versions and Loaders

The mod is designed for modern Minecraft Java Edition servers and runs happily on the Fabric and NeoForge loaders across recent 1.20 and 1.21 releases. Because everything happens server-side, players on unmodified clients see no difference. If you are unsure which build matches your setup, check the version list on the project page before you download Issues and drop it into your mods folder.

Optional Maintainer Tools and Claude Integration

The headline feature, and the one that surprises people, is the optional maintainer layer. When a server enables it, named players can work through reports with Claude from inside the game. Each session starts already briefed: it knows which reports it is about, where the logs live, how the mod suite builds, and how to stage a fix without breaking a running server. Claude reads the reports, explains in chat what it believes is wrong, and then waits for a human to say go. Commands like /maintain start, /claude <message>, and /maintain sessions handle the whole conversation, and a browser link lets you follow along from outside the game.

Access is guarded by a passphrase rather than a username, since offline-mode servers accept any name. Five wrong attempts in ten minutes locks that name out temporarily. A maintainer effectively holds the same power as the machine's shell user, so hand it out carefully. Configuration lives in config/server-issues.json, and the file reloads automatically when it changes.

If you would rather skip the manual file shuffling, the foxygame.net launcher installs Issues with a single click and keeps it updated as new Minecraft versions ship, so your report pipeline never breaks after a game update.

Crash Reporting That Works While You Sleep

The add-on also watches how your last run ended. When the server comes back from a crash, the event is saved as a bug report from "the server" with the cause and the crash report name, and it appears in /issues like any other entry. It even catches runs that stopped without shutting down, such as an out-of-memory kill. With the maintainer layer enabled, a crash can open its own Claude session, and repeated crashes within an hour funnel into the same investigation instead of spawning a dozen duplicates. The onCrash setting controls whether Claude merely reports, investigates, or attempts a small automatic fix.

Getting Started

Learning how to install the add-on takes about two minutes. Place the jar in your server's mods directory, restart, and confirm the config file appears. Then tell your players about /bug and /idea, and try /issues yourself. If you want the full Issues for Minecraft experience with automated maintenance, add the optional paude settings and a maintainer passphrase, then test with a throwaway account before trusting it with real fixes.

For any community that runs a long-lived world, this mod replaces scattered complaints with a searchable, timestamped record that survives crashes and version bumps. Set it up once, and your players finally have a proper channel for feedback.