Report a Bug

There are two ways to report: from inside the game, or from the form on this page. No GitHub account is needed for either. The in-game reporter is worth the extra step when you can use it — it records your build and platform for you, and those are the first two things we would otherwise have to ask you for.

Reporting from inside the game

Press … during play to open the bug reporter. That is the default bind; every key in the game can be reassigned, so if it does not respond, check Keybindings on the game's main menu. That screen lists what your copy is actually bound to, and it is the only thing that can answer the question for a copy that has been rebound. (Rebinding lives on the main menu, not in the in-game Settings menu.)

What it fills in for you

You write a title and a description. Attached to that, without you doing anything:

your operating system
the game version, and the Godot engine version it was built with
a UTC timestamp

There are tick boxes to also include a screenshot and a copy of your most recent save, and to put your name to the report if you would like the credit. Leave the name blank and the report is filed as anonymous. Nothing is sent anywhere until you send it yourself — see below.

What happens to the report

The game does not transmit it. The reporter writes a .json file to your own machine, plus the screenshot and save file if you ticked them, and then shows you the full path to it. Getting that file to us is a manual step, and if you skip it we never see the report. Automatic submission is intended for a later release; this build does not have it.

Once you have the path, either:

email the file to the address the game's confirmation message shows you — it currently names pip@beacongcr.org; or
attach it to the form further down this page. It accepts .json, so the saved report goes through as-is, along with anything you want to add.

Those are two different addresses for the same thing — the game names one, this site uses another. That inconsistency is ours and we are consolidating it. Until then, use whichever address the route you chose puts in front of you, rather than picking between them.

Two keys worth knowing before you report

These are also defaults, and also listed on the Keybindings screen. Both work in a normal release build.

… takes a screenshot. A picture of the wrong thing on screen is usually faster than describing it.
… exports the game log to a file you can attach. Worth including for a crash or anything that only happens sometimes.

Dev mode

Dev mode is a developer tool, and you probably do not have it. It is an overlay showing live internal game state plus controls for forcing situations while testing. It sits behind a build flag that is compiled into the game, and a clean release build is meant to ship with that flag off. Nothing in the export tooling sets it automatically, so whether it is present in any given download depends on how that build was cut.

If you want to try: the default bind is …. If nothing happens, your build has the flag off, and there is no setting that turns it on — it would need a different build. That is expected, not a fault, and nothing about it is needed to file a good bug report.

What you can reach in any build is the debug overlay on …, which shows game state, recent errors and performance figures. If a report is about slowness or a wrong-looking number, a screenshot of that overlay is useful evidence.

Reporting from this page

Use this if the game will not start, if it is already closed, or if you would simply rather type it here. You can attach a screenshot, log, or config file (up to 500 KB) and it comes through with your report.

Issue Title *

Bug Type

Select the category that best describes your issue

Description *

Include steps to reproduce, expected behavior, and actual behavior

Your email (optional)

Only if you'd like a reply. Sent privately to the team — never published, never added to a public issue.

Name for credit (optional)

If you'd like credit for finding this, tell us what to call you — a first name, a handle, anything. Unlike your email, this one may be shown publicly (release notes, credits, or a linked issue). Leave it blank and you stay anonymous — the report is just as welcome either way.

Attach a File (Optional)

A screenshot, log, or config file — it comes through attached to your report. Max 500 KB. Supported: .txt, .log, .json, .zip, .png, .jpg

Where these reports go

The form emails your report to team@pdoom1.com, a private inbox. If you filled in the optional email field, it goes there too and nowhere else. A name entered for credit may be published; an email address never is.

One caveat we would rather state than hide: the mail step can fail on our side without telling us, and without telling you — the page would still show a success message. We cannot confirm delivery from here. So if a report matters to you and you hear nothing back, it is reasonable to assume it went missing and send it again, or use the GitHub route.

If the submission fails outright, the page opens a pre-filled GitHub issue instead, so the report is not lost. That path is public and needs a free GitHub account, but it is the one where you can see for yourself that it arrived.