Explore and edit
Select Rivio in the Activity Bar and expand your project. Selecting an instance opens its Properties; selecting a script opens its source. Use property search to find the value you want to edit.
Right-click a supported service or folder to create a Script, LocalScript, ModuleScript, or Folder. Give it a readable name without adding a script extension. Use the context menu to rename, delete, or reveal files.
For Rojo projects, Rivio keeps script types and project mappings aligned with supported file operations. Keep the Rojo sync connection running to see filesystem changes in Studio.
Work with the right place
Check the connected place name before editing. When several Studio windows are connected, select the intended place in Explorer and name it explicitly in assistant requests.
Use Studio directly to navigate and inspect the live scene. Rivio’s Animator and Scene Editor have their own authoring views.
Normal persistent scene edits require Studio edit mode. Stop a playtest before changing the saved scene. Changes made during play are temporary unless a supported workflow explicitly saves them.
Use a short test loop
- Save a checkpoint or commit before the task.
- Describe one outcome, the relevant place, and what should stay unchanged.
- Inspect the proposed or completed change in your script or scene.
- Run a playtest, try the affected interaction, and inspect Studio Output.
- Stop the test, fix any issues, then save the working result.
Give your assistant useful context
Good requests identify a visible result and a way to check it. For example: “In my Lobby place, inspect the door script, fix why it opens twice, then test the interaction and report any remaining errors.”
For visual work: “Create a short entrance animation for this R15 rig. Show me a preview before installing it in Studio.”
For risky or broad work, ask for an inspection and plan first. Review generated code and content before publishing your experience.
Use Output when something goes wrong
Open Studio Output from Rivio Explorer’s overflow menu. Check the originating place and the first relevant error, not only the last line.
For captures, input, and runtime tools, enable Roblox Studio’s own MCP server in Studio settings when the feature requires it. The Studio connection and your assistant’s Rivio MCP connection serve different purposes.
If an import or export appears stuck, check its reported status before repeating it. Save your work before updating plugins or restarting applications.