The Report Panel

Hub › Other Systems › The Report Panel

The report panel is how a player talks to the team from inside the game. It is the REPORT A BUG tile on the main menu and Contact Support under Settings › Legal & Support. A person reads every report; the ones that are bugs become fixes in the next bug run, and the fix is logged on the codex page that owns the rule.

What you fill in

Kind — Bug, Suggestion or Other. Pick Bug when the game did something it should not have; Suggestion when you want it to do something new.
Title and what happened — your own words. Where you were and what you pressed is the most useful thing you can write.

What rides along

Attached	Why
The game's state when you opened the panel	Floor, party, window, battle in progress — a snapshot taken at open time, so what you describe is what we see. Where the state has moved while you typed, the live value rides along too.
The recent notices	The lines the game showed you (drops, unlocks, warnings) and any script errors it caught. There is no play log on the device: the action log is kept server side only (T31-2), so the report carries the notices list, each section with its own size ceiling, newest lines kept.
The build id	Which version you were running.
No screenshot	Nothing is captured from your screen.

Your save is flushed to the server before the report is sent, so the state the report describes is the state the server holds. The Privacy Policy lists exactly what a report contains and how long it is kept.

What happens to it

The report lands on the server (POST /api/feedback, the world object) and is pulled into the team's queue as a numbered file.
Reports are triaged by kind. A bug is reproduced with a probe before it is fixed; the fix names the report number in the commit, the patch registry and the codex changelog of the page that owns the rule.
A suggestion that needs a design decision goes to D's rulings board rather than straight into the code.
You are not written back to from inside the game. Join the Discord (the invite is on the main menu) if you want to follow a report.

Implementation notes

Client: feedbackSend() builds {kind, title, body, ctx, logs, shot:'', build}; feedbackLogs() is the notices list with per-section ceilings; saveRun() runs first.
Server: /api/feedback is a WORLD path; admins read it at /api/admin/feedback and mark it with /mark; /api/feedback/export feeds the team's pull. The team-side pipeline (clustering, triage console, ratings) is on Feedback Pipeline.
Menu plate: MENU_PLATES.feedback = 'report_a_bug'; the Discord tile is join_the_discord_chat.

Changelog

2026-11-03 — page written (D 2026-11-03: “add whatever sections and systems we have in the game but not on the codex”; dfmc-client lane codexreview-b). WIKI ONLY, no game behaviour. The in-game report panel had no player-facing page: feedback-pipeline.html is the team-side console. This page says what a player fills in, what rides along (open-time state, the notices list, the build; no screenshot; the save is flushed first), and what happens to a report.

What you fill in

What rides along

What happens to it

Implementation notes

Changelog