Assets and uploads
Understand generated assets, local records, Roblox upload consent, retry behavior, and Studio insertion boundaries.
Asset records
NexusRBX can generate local asset records for icons, textures, and model-related outputs. A local asset can remain usable in the workspace even when Roblox upload is disabled or still pending moderation.
- Keep the local asset preview and metadata available for review.
- Track upload state separately from generation state.
- Show retry and poll actions when an upload fails or remains pending.
Roblox upload consent
| Setting | Behavior | Failure handling |
|---|---|---|
| Enabled | Attempt Roblox upload after generation using server-owned OAuth handling. | Keep the local asset and show retry or poll state. |
| Disabled | Do not write to Roblox. | Keep the local asset available in the tray. |
| Pending moderation | Do not assume the Roblox asset is immediately usable. | Poll or retry based on the status returned by the backend. |
Studio insertion
Studio insertion should use trusted records and server-owned orchestration. Browser-supplied metadata is helpful context, but it is not authoritative for privileged writes.
- Use explicit review or confirmation gates before inserting into Studio.
- Keep OAuth and privileged upload handling server-side.
- Preserve the local asset when Roblox upload fails.
Was this page helpful?