What happens when you send a bug report

Automatic bug reports are on by default. Detected errors and unexpected previous exits can be sent with filtered diagnostics without a prompt. Turn this off in Mods > Settings & Help to use manual reporting only. Opening Report Bugs does not upload anything; manual reports require Send report.

Automatic reports use a generated description; manual reports use the description you enter. The FTK Mod Framework reporting service hosted on Railway creates a public GitHub issue for either kind. You do not need a GitHub account. The service uses its own repository credential; no GitHub credential is stored in the game.

Automatic reports include diagnostics. Manual reports include diagnostics when Include diagnostics is selected. Diagnostics contain a filtered recent game/framework process log dump, including informational messages, warnings and errors, plus game and framework versions, installed mods, your framework tweak settings and which tweaks are active, and diagnostic session context. Log capture begins when reporting initializes and keeps at most 128 KiB of UTF-8 text per session. For a previous unexpected exit, this may include preserved diagnostics from that session; the latest entries can be lost in an abrupt exit. Older reports without recorded logs cannot recover them later. These diagnostics are public: excerpts appear in the issue and download links expose the sanitized diagnostic JSON and readable .log dump to anyone with a link.

For manual reports, you can turn off Include diagnostics before sending. Save files, screenshots, and account credentials are not intentionally collected. Automatic filtering removes known sensitive fields and patterns such as common credentials, home-folder names, email addresses, and Steam IDs. Filtering cannot guarantee removal of every personal detail a mod writes to a log, or details you type yourself. Manual reports can review the optional diagnostic preview before Send; automatic reports are sent without a preview. Avoid personal information in your description.

The service removes report descriptions and diagnostic bundles from its storage after 30 days (cleanup runs hourly). GitHub issue text and excerpts remain public until removed by a repository maintainer. Other people may retain copies. Minimal submission receipts (random report ID, content hash, submission time, issue number and URL) remain to prevent duplicate issues.

Network addresses are used transiently for abuse limits and are not written to report bundles. Railway and GitHub may process connection information under their own policies. The service does not log request bodies, credentials, or player network addresses.

To request removal, contact a repository maintainer through the report's GitHub issue. This community framework reporting service is not operated by the game's original developer.