Report a bug

A bug report with a support bundle is fixable. Without one it is a guess. There are two ways to send one: from inside Creator with SEND REPORT, or by posting it yourself in the forum. Either way nothing leaves your PC until you press SEND or post it yourself.

Send it from Creator

HELP has two buttons for reaching the Creator team, on its ABOUT tab:

Button	What it sends
SEND FEEDBACK	A message you type (up to 2000 characters), and the version line. No name is attached.
SEND REPORT	A support bundle, with a message if you want to add one, the version line and the name.

1. Press F9 while the problem is on screen, if it is something you can see. Creator runs a short automatic check and saves screenshots to Desktop\CreatorDiag\run-<stamp>\. Wait for it to finish: the newest report goes into the bundle.
2. Open HELP and click SEND REPORT. Creator builds the support bundle, saves it to your Desktop and shows its size.
3. Say what you did, what you expected, and what happened. In that order, in plain words, in the message field.
4. Read the line above SEND. It lists exactly what will leave your PC.
5. Press SEND. The report is posted to the #feedback forum on Discord, where the Creator team and the other members of that server can read it. The box says when it has arrived, or why it did not.

SEND FEEDBACK works the same way without a bundle: type your message and press SEND. A box you leave keeps what you typed until you come back to it or close Creator.

A bundle over 8 MB cannot be sent from Creator; the box says so before anything is sent. Post it in the forum instead, as below.

Post it yourself

1. 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. This button uploads nothing.
2. Attach the zip and the F9 folder, plus the .map you were working on if you can share it.
3. 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.
4. Say what you did, what you expected, and what happened.
5. Post it in the bug and feedback forum on Discord.

If Creator will not start far enough to reach HELP, attach Player.log instead. It is in %USERPROFILE%\AppData\LocalLow\Rook\Creator\.

A .map is never sent by SEND REPORT. If the problem is about a specific map, post the map in the forum yourself.

What is in the support bundle

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

Inside	What it is
version.txt	The exact build, the engine, and the command line it was started with.
content.txt	Where Creator reads Rust’s files from (your Rust install or a private copy) and which Rust build that is.
system.txt	GPU, CPU, memory, screen and render settings.
map.txt	Which map this is: its name, size and prefab count.
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.
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 is removed before anything is written.

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

A report can say STATUS: OK while the screen looks wrong, so attach the screenshots. 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.