Customize and Playtest Your Game in Roblox Studio

Open a saved copy#

Download the .rbxlx game from PromptBlox and open it in Roblox Studio on a supported computer. Save a separate working copy before making changes. Follow Install and open Studio if this is your first time.

The file you edit in Roblox Studio and the saved project in PromptBlox are separate copies. Local changes do not automatically appear back in the PromptBlox project.

Inspect the world at player scale#

Begin with spawn, routes, doors, stairs, and the first objective. A layout that looks connected from above may still have a raised join that stops the character. Look for overlapping surfaces, obstructed sightlines, and props that block movement.

Use Explorer to select the intended object and Properties to inspect it. Change one area at a time. Renaming objects or moving scripts between containers can affect gameplay, so keep a copy and test after structural edits.

Test as a player#

Choose Test in Studio's playtest dropdown, then press Play or F5 to insert your avatar at the normal spawn. Test Here starts near the editor camera. Run does not insert a player, so use Test for checking the player's route.

Stop returns the simulation to the editing state. Make changes you intend to keep after stopping. During a test, switch between Client and Server views and inspect Output to locate errors; what the client displays and what the server records can differ.

Try this sequence:

1. Spawn and identify the first goal without moving the editor camera.
2. Reach it and use the required interaction.
3. Check the visible feedback, inventory, score, or reward.
4. Fail once and verify respawn or recovery.
5. Complete the loop, then restart and complete it again.

For a vehicle, include entering, moving, steering, exiting, and resetting. For a collection game, try collecting the same object twice and filling the inventory.

Check touch and multiplayer behavior#

Open Studio's Device Simulator to inspect a smaller screen and touch controls. Verify that the HUD leaves the world and movement controls visible. A simulated screen does not establish real-device performance; follow up on a target device when possible.

For multiplayer, select Server & Clients, choose two clients, and press Play. Use End Session when finished. Check what happens when both players use an object at once or one leaves mid-activity. Test shared rewards, late joins, and round resets separately.

Choose where to make the next change#

Make a small visual adjustment directly in Roblox Studio if you want exact control over it. Use a PromptBlox refinement when you want to describe a larger change in plain language, while remembering which saved copy the refinement will affect.

Where game import is enabled, you can save an .rbxlx place and import it into PromptBlox as a new project for further work. This is not a live sync with the existing project. Keep the original place and inspect the imported result.

Record the result#

Write down the version, the action tested, and any issue that remains. “Collected three crystals, opened the observatory, restarted successfully” is useful evidence. “Looks good from above” answers a different question.

When the complete loop works, follow the publishing guide. If it fails, turn the reproduction steps into a focused refinement.

Official reference#

This is an independent PromptBlox walkthrough. Roblox's Studio testing documentation explains the current testing modes and simulation tools.