Since: v0.309.0 (PR #411) — powered by Discord Presence 0.19.0

When you die, a Give Feedback button appears on the death screen. It opens a short survey that walks you through one question at a time — a 0–10 rating plus an optional comment each — and posts every answer to the community Discord. Dungeon Train ships one question ("How would you rate the difficulty progression?"); Discord Presence contributes a built-in NPS question ("How likely are you to recommend this game to a friend?") that is always asked first.

The survey system is owned by Discord Presence, not Dungeon Train — DT only contributes its question as a data file, so any mod or datapack can add questions the same way (see Adding questions).

                You Died!   (run recap)
        [  New World  ][  Title Screen  ]
              [  Give Feedback  ]          ← while you have unanswered questions

  click ─▶   Question 1 of 2
             How likely are you to recommend this game to a friend?
             [0][1][2][3][4][5][6][7][8][9][10]      ← pick a rating (selected one is outlined)
             [ What's the main reason for your score? (optional) ]
             [ Submit & next ]  [ Skip ]

  submit ─▶  Question 2 of 2
             How would you rate the difficulty progression?
             [0]…[10]   [ comment… ]   [ Submit ]  [ Skip ]      ← last one reads "Submit"

  submit ─▶  closes back to the death screen; both answers are now in Discord

• The button sits at the bottom of the death screen, clear of the recap and the New World / Title Screen row.
• One question per screen. Submit & next posts that answer to Discord and advances; the last question's button reads Submit. Skip advances without recording (you'll be offered it again next death).
• Answers are tracked per player. The survey re-opens on every death and via /feedback, so you can give feedback as often as you like — and you can turn off any question you've already answered (see Skipping questions below).

The whole survey lives in Discord Presence (so it's reusable by any mod); Dungeon Train contributes only data:

• On death, the server sends the player their unanswered questions in ask-order; the client shows the Give Feedback button only while that list is non-empty (re-evaluated each frame, so a question that arrives just after the screen opens still surfaces the button).
• The survey screen walks the list locally — each Submit sends the answer to the server, which validates + records it (per player, persisted) and posts it to Discord, then the client advances to the next question.
• Each answer posts into the player's own Discord thread (the same thread as their join / death / advancement messages) as a small embed: the question as the description, plus a Rating (8 / 10) and an optional Comment field.
• The built-in NPS question is always first; data-driven questions follow, ordered by an optional order field.
• Each answer carries a small tag — the embed footer in the player's thread, and the header line of the copy in the survey-results channel (see below).

🟠 DT 0.1093.0 · Russian · Mods: 87 · Games 12 · (3) → <link to the threaded original>

The newest release is read from the relay at most every 30 minutes; when it cannot be reached the dot falls back to the build's age alone and is never green. Built by SurveyTag and VersionFreshness, handed to Discord Presence (≥ 0.65.0) through its surveyEmbedFooter(playerId, clientLanguage, timesAnswered) seam; Discord Presence keeps the per-question answer counts in its discordpresence-surveys.json. Mod recommendations and hack reports from the death screen carry the same tag.

Responses go out through the same relay/webhook the rest of the Discord Presence integration uses, so on a default Dungeon Train install they land in the community feed. The survey only runs when Discord is configured (and, in singleplayer, after the one-time network-consent prompt).

Since: PR #1253

The survey is offered fresh on every death, so a question you have answered comes back around. From the second time you are shown a question you already answered, it carries a "Don't ask me this again" tick box under the rating row. Tick it and that question stops appearing in the death screen's normal page walk for good.

Skipping is not the same as losing it. An envelope button sits on the death screen's last page, beside the $ support chip. Press it and the screen walks you through every feedback question in turn — the skipped ones included — then hands you back where you started. A skipped question draws its tick box already ticked, so that walk is also where you put a question back into the normal flow.

The start page's Submit Bug shortcut reaches the bug question the same way, whether or not it has been skipped, and /feedback and /bug ignore skipping entirely — those are asked for, not offered.

Skips are stored per player in dungeontrain-client.toml under [deathScreen] (answeredForms and mutedForms), so they follow you across worlds and servers. The Video Tools profile reset's one-time prompts item clears them.

You don't have to die to give feedback:

• /feedback opens the full survey at any time, in any game mode — the same question walk shown on the death screen.
• /bug (since v0.415.0, PR #687) jumps straight to the bug-report question ("Did you face any bugs in this run?"), skipping the rating questions — a fast path when you just want to report a problem.

Both commands are not op-gated (anyone can run them) and are whitelisted in the cheat classifier, so using them never marks your run as cheated. /feedback is contributed by Discord Presence; /bug is a Dungeon Train command that opens DP's survey filtered to the bug question.

When you answer the bug-report question with anything other than No — from the death screen or from /bug / /feedback — Dungeon Train collects your recent client logs and ships them to the server, which archives them under logs/<version>/<user>/ and posts them (with the chosen option) to the community feedback feed. For a Lag answer it also folds in a short system-spec summary (allocated game memory, CPU/GPU, OS, launcher) so lag reports carry the hardware context needed to diagnose them. Choosing No sends nothing. This is best-effort and only runs when Discord is configured and network use is allowed (see the consent note above).

Questions are data files — drop a JSON at data/<namespace>/dp_surveys/<name>.json in any mod or datapack and Discord Presence loads it (reloadable with /reload). The file's resource id (<namespace>:<name>) becomes the question's stable id.

{
  "prompt": "How would you rate the difficulty progression?",
  "scale_min": 0,
  "scale_max": 10,
  "allow_comment": true,
  "order": 100
}

Dungeon Train's own question lives at data/dungeontrain/dp_surveys/difficulty_progression.json — add more DT questions by dropping more files there, no code required.

• Persistence / reset: answers are stored per player UUID in config/discordpresence-surveys.json. Delete that file to re-offer every question (handy for testing).
• Config: Discord Presence's surveyEnabled (default on) gates the whole feature; surveyEmbedColor sets the embed colour.
• Version trail: Discord Presence 0.17.0 introduced the survey + death-screen button + the built-in NPS question; 0.18.0 made questions data-driven (the dp_surveys data files); 0.19.0 added the one-sitting multi-question walk. Dungeon Train 0.309.0 wires it up and ships the difficulty question.

• Death screen — run recap & buttons — the survey button shares this screen.
• Compatibility › Discord Presence — the bundled mod that owns the survey and posts to Discord.