Troubleshooting
Fix common NexusRBX issues with Studio pairing, authentication, source conflicts, Roblox upload states, and generated scripts.
Common issues
Pairing code expired
Return to /ai, generate a new short-lived code, and enter it in the Studio plugin panel before it expires.
401 or signed-out workspace
Sign in again and reopen the workspace. If a public prompt started the flow, NexusRBX should restore the generation intent after authentication.
source_conflict
The target script changed after NexusRBX read it. Re-read the script, verify the new source, and retry with the updated expectedSourceHash.
Roblox upload pending
Keep the local asset. Poll or retry from the asset tray instead of assuming the Roblox asset ID is ready.
Generated script errors in Studio
Read the first Output error, confirm script type and location, verify object names, and test multiplayer changes with Start Server.
Debugging checklist
- Paste the exact Output error into NexusRBX.
- Name the script type and location.
- Confirm whether the issue happens in Play Solo, Start Server, or both.
- Mention recently changed scripts or assets.
- Use Agent Build when the fix may touch multiple scripts.