Report a bug

A bug report with the two attachments below is fixable. Without them it is a guess. Both are one click each, and nothing is uploaded anywhere: you make the files, you read them, you decide whether to send them.

Do this

1. Press F9 while the problem is on screen. The diagnostic harness flies a set route, samples real frame rates, captures screenshots and writes everything to Desktop\RustCreatorDiag\run-<stamp>\. Wait for it to finish.
2. Open HELP and click CREATE SUPPORT BUNDLE. It packs the list below into a single zip on your Desktop and opens the folder so you can find it.
3. Attach the zip and the F9 folder, plus the .map you were working on if you can share it.
4. Include the version string. It identifies the exact build you are running, which is the first thing anyone will ask for. HELP > About Creator shows it with a COPY button beside it.
5. Say what you did, what you expected, and what happened. In that order, in plain words.
6. Post it in the bug and feedback forum on Discord.

If Creator will not start far enough to reach HELP, run it once from a command prompt with RustCreator.exe -bugbundle: it writes the same zip and exits immediately, without loading a map.

What is in the support bundle

One zip, Creator-support-<date>-<time>.zip, on your Desktop.

Inside	What it is
manifest.txt	The contents list, and what is deliberately NOT collected.
version.txt	The exact build, the engine, and the command line it was started with.
content.txt	Which Rust content snapshot you are on and how fresh it is.
system.txt	GPU, CPU, memory, screen and render settings.
map.txt	Which map this is: its name, size, prefab count, and a fingerprint (sha256) of the file.
report.txt	Your most recent F9 diagnostic run, if you have made one.
crash-report.txt	The most recent crash, if there was one: the error and the log around it.
Player.log	This session’s log, capped at its first and last few MB.
alerts.txt	Every warning and error Creator showed you this session.

Your maps and screenshots are never collected automatically. Attach the .map yourself if the problem is about a specific map. Your Windows user name and folder paths are replaced with placeholders before anything is written.

Why the map fingerprint matters. It says whether the .map you send is the same file the problem happened on. Re-saving a map changes it, which is completely normal and is exactly what that line exists to make visible.

STATUS: OK in a diagnostic report is blind to visual bugs

The first line of report.txt means “nothing crashed, the shaders are supported and the frame rate is fine”. It says nothing about what the screen looked like. A report can read STATUS: OK while a roof is exploded in the screenshots beside it, which is why the PNGs matter more than the status line. Attach the whole folder, and say what you saw.

What counts as a bug

At this stage, more than you might think. Confusing counts as a bug. So does a message that did not tell you what to do, a number that disagrees with this documentation, and anything that made you close the app and start again. Creator is in alpha, and the fastest way to shape what gets fixed is to say what you hit.