How to Write a Useful Broken-Script Report

“It doesn’t work” leaves an editor guessing. Is the page missing, is Copy doing nothing, or did a particular action fail in a particular setup? A good report narrows that down before it proposes a cause.

You can also report an unclear listing without running its code. The filled example below uses wording visible on a real catalog page, which is enough to raise a specific question.

Choose the type of issue first

Pick the issue category first. A platform-description correction needs different evidence from a browser clipboard problem, and mixing both into one report can obscure each.

A filled example based on visible information

In the catalog on 2 November 2026, Amorestar’s description mentioned PC, Xeno and Solara, while its compatibility field named Delta. Here’s a report about that wording, without claiming a runtime failure:

Issue type: Incomplete or conflicting environment information
Record: Amorestar — San Diego Border Roleplay
Page: https://deltascripts.co/#script-san-diego-amorestar
Language: English
Observation date: 2 November 2026

Observed information:
The description mentions PC, Xeno and Solara.
The separate compatibility field names Delta.

Question for the editor:
Which Delta-specific source, platform and version support that field?
Please clarify whether the description applies to the same revision.

Review coverage:
Page information only. No script was executed for this report.
No account details, keys or private logs are included.

Notice what the example gives the editor: a record, a URL, the two relevant statements and a question. It also says the review covered the page only, so nobody has to guess whether the script was run.

Use numbered reproduction steps for an action failure

For an action failure, write numbered steps from a stable starting page. Include the language and filters if they affect the result. Another reader should be able to follow the same route without reconstructing your whole browsing session.

Put the expected and observed results on separate lines. For Copy, you might expect the displayed code in the clipboard and instead see a permission notice. That describes a browser problem without making a claim about execution.

For a Studio project you own, save the smallest reproduction and note the Script’s location and RunContext. The first relevant error and its line usually tell a helper more than a screenshot of the final scene.

A reusable report form

Record name and game:
Record or collection URL:
Page language and active filters:
Issue category:
Date and approximate time, with timezone:

Expected result:
Observed result:

Steps to reproduce:
1.
2.
3.

Relevant environment, if known:
- Device and operating system:
- Product and version:
- Script revision or saved text:
- Studio context, for your own project:

Exact relevant message, with private material removed:
What changed since the last known observation:
What I have not established:

Copy the form and fill only what you know. Write “unknown” for a missing version. A few honest gaps are easier to work with than precise-looking details supplied from memory.

Keep secrets out of text and screenshots

Read a log before sending it. Remove passwords, cookies, access keys, verification codes and unrelated personal information. If a URL includes a private token, redact that part while keeping the useful structure.

Inspect screenshots beyond the error box. The address bar, other tabs, notifications and side panels may contain private material. Crop to what’s needed and check the result before sharing.

Roblox’s account-safety guidance applies during troubleshooting too. A request for help doesn’t make account secrets suitable diagnostic evidence.

Report the first useful observation, not a theory

“The source request returned an error” describes an observation. “The author removed the project” proposes a cause. Keep the first when you haven’t established the second; it saves an editor investigating a conclusion your evidence never supported.

Add a dated follow-up when you learn more. Keep the original conditions visible so someone can understand what changed between the first report and the update.

Send it through the appropriate channel

Send catalog problems through the report form. Article comments are public discussion, not a place for private logs. Roblox account recovery belongs with Roblox Support.

Before sending, ask whether the report makes the next check obvious: open this record, repeat this step or compare these fields. If it does, you’ve given the editor something they can use.

Further reading

• The site’s reporting guide.
• Information to preserve when behavior changes.
• Roblox account safety.