How to Fix and Refine a PromptBlox Game

Find the problem in play#

A scene preview shows the layout; it does not prove that the gameplay works. Export your game and test it in Roblox Studio. Begin at the real spawn and try the action a new player would take.

Record the location, steps to reproduce the problem, and what happened. A screenshot can help explain a visual issue. For a script error, include the relevant message and when it appeared, without sharing private account information.

Preserve a version you can return to#

Keep your original export. If saved versions are available in History, identify the version you are comparing against before requesting a larger change. Do not delete a working copy while investigating a regression.

Saved drafts live in Library. If a build is stopped, use the recovery or continuation options shown for that build. Continue build depends on retained progress and available allowance; an unfinished attempt may not have a usable scene yet.

Describe the repair#

A useful message has four parts:

• Where: name the area, object, or interaction.
• Observed behavior: explain what happens now.
• Expected behavior: explain what should happen instead.
• Preserve: name the layout, art, or systems that should stay the same.

At the entrance to the harbor market, the delivery counter blocks the doorway and I cannot reach the parcel pickup. Move the counter far enough inside to leave a clear route from the plaza. Keep the building exterior, delivery destinations, reward amounts, and current objective flow unchanged. Make the pickup reachable on foot and with touch interaction.

Fix the highest-impact issue first#

Start with a blocked route, broken interaction, missing reward, or failed respawn. Then work on readability, balance, and decoration. Group changes that belong to the same issue; avoid mixing a new game mode with a small repair.

When Game Graph is available in your workspace, use it to identify the relevant area or system. You can also describe the location directly in chat. A structural view helps target the edit but does not replace testing it.

Compare the new result#

Repeat the original reproduction steps. Then try the nearby interactions that might have been affected: the return route, another objective, a restart, or a second player collecting the same reward.

Refinements use allowance for the work performed. Review each result before requesting the next change. If a repair fails, describe what still happens instead of repeatedly sending “fix it.”

When the problem is a paused build#

Read the build status and available action. “Paused,” “stopped,” and “finished” describe different states. Do not assume that a paused build will restart automatically or that a stopped build has saved every in-progress change.

If the workspace cannot offer a recovery option, retain the build link and contact support through Contact with the status and time of the attempt. Check your Library and History before beginning a replacement build.

When to change the original idea#

If the requested feature needs a different map or an entirely new game loop, treat it as a planned expansion. Explain what the new loop needs and what should carry over. For a cleaner first request, revisit prompting basics.