About

PackReport lets players report gameplay bugs to server hosts - from inside the game, without leaving it or having to chase down external reporting processes. At the same time, it provides an easy way for pack authors and server hosts to collect bug reports and helpful debug information from their users with very low friction or effort.

A player types /report, gets a preview screen, describes the issue, and hits send! PackReport packages a screenshot, their location and dimension, the modpack fingerprint (mod list + versions), system info, and recent chat. Players can also optionally attach the tail of their latest.log. Note the fingerprint reflects the player's own client, so on servers where players run their own client-side mods it won't be a clean snapshot of the server pack - still often diagnostically useful.

This is not primarily a crash reporter and isn't particularly useful for in-depth debugging. It's built for the bugs that don't crash the game - broken quest chains, broken terrain generation, missing or incorrect recipes, a mob that won't spawn, a balance problem, griefing/trolling etc. As for actual crash reporting, there are other mods out there already and this would pair well with them!

If you've installed PackReport on your client but the server you're playing on hasn't, reporting bugs directly to the server's staff through whatever pipeline they already use (usually Discord) is still the way to go. PackReport is designed to slot into those pipelines, not bypass them: when there's no server to send the report to, it writes a local archive instead. Hand that archive to the staff and they get everything they need, without you having to dig it together yourself.

What pack authors get

Discord webhook, HTTP endpoint, or local file - pick one or several. Reports land formatted and readable in the associated channel with the screenshot attached
Role ID pinging - optional. Pings a chosen role on each report (e.g. alerts your staff the moment a bug comes in)
The webhook URL never ships to players; it lives in the server config only, and is never sent to clients. No pulling webhook URLs out of your CurseForge-distributed packs
**Server-authoritative cooldown **- rate-limited per player on the server, so it can't be spammed. Operators are exempt from cooldowns. Time is configurable
Local fallback. A player on a server that doesn't have PackReport still gets a clean local .zip of their report instead of an error, useful for submitting to official pipelines or examining themselves
Preview before submission: players see exactly what's being submitted (screenshot, description, what context is attached) and must confirm before sending

Support and Version Requests

PackReport was just created and has room for improvement. If there are problems or feature requests, you can open an issue here on CurseForge and I'll tend to them as soon as I can.

Other versions may be made available on request. I wasn't sure which others to build for, as these are the only versions I really ever play on. There's a lot of API churn between versions so I can't promise I can always deliver, but I'm happy to look and give it a shot.

Commands

/report — open the report screen (any player).
/reportadmin cooldown clear <player> — clear a player's cooldown (operator).
/reportadmin cooldown reset <player> — restart a player's cooldown timer (operator).

Setup (pack authors)

Drop PackReport into the pack — it goes on both the server and the client.
On the server, edit serverconfig/packreport-server.toml: add your Discord webhook (or HTTP URL, or leave it on file output), set the cooldown.
That's it. Players use /report; you receive reports.

Builds

Loader	Minecraft	Status
NeoForge	1.21.1	Released
Forge	1.20.1	Released

NeoForge build: a config screen is available in-game via Mods → PackReport. TOML editing also available in config directory

Forge 1.20.1 build: configured by editing the .toml directly.

Privacy

PackReport only sends a report when a player presses Send, and only sends what's shown on the preview screen. Logs and recent chat are opt-in per report. Nothing is collected in the background. Looking at you, Pixelmon.

Support Me

I'm on Ko-Fi - buy me a coffee so I can keep creating things like this and meet version requests!