Ensure visual assets are traceable, licensable, and safely integrable, and can be consumed by gameplay and UI under a stable identity. Before starting, read the visual goals, DataModel paths, asset budget, andStudio plugin routing。
First follow thevisual workflowto read the current visual baseline, then followshared asset registration and usageto check the single asset master table, consumers, licenses, and actual paths. Model generation, splitting, material pairing, in-place texture replacement, and asset readiness boundaries are all based on the current Studio tool facts in that reference.
According toasset consumption bindingregister asset revisions, current/historical consumers, and the Edit readback of consumption work items; when an asset changes version, is retired, or its license expires, handle the actually affected consumers first, and do not substitute producer PASS for consumption acceptance.
Responsibilities and inputs
- First query the asset IDs, model structures, and license records already used in the current Experience; for requirements, clarify the purpose, viewing distance, style, performance goals, and production source.
- Studio's search_asset is used to find candidates; after verifying the source and usage rights, insert_asset only imports candidates into game.ServerStorage for isolated review, not directly into runtime containers.
- Route models, materials, textures, and procedural model generation to generate_mesh, generate_material, generate_texture, and generate_procedural_model respectively; specific parameters follow the tool's actual schema, and parameters must not be invented.
- When newly drawn bitmaps, illustrations, icons, or texture concept art are needed, hand them to image_generator; do not treat 3D generation tools as bitmap generation interfaces.
- When there are substantive choices in key visual direction, copyright alternatives, or external costs, hand them to the planner; implementers may handle ordinary details within an already determined direction on their own.
- If the visual direction, reference image usage, asset license, generation scope, or production cost cannot be confirmed from project records and source evidence, hand it toRoblox Game Interrogationto clarify item by item and record the approved scope; asset search results do not make license or style decisions on behalf of the user. After the decision, return it to the original asset work item.
Execution steps
- For each asset, record a stable name, purpose, consumers, source, author/license, source address or Studio-returned identity, version, and replacement owner.
- Reuse assets that have already been approved and meet the budget first; search results are only candidates and do not mean that licensing, quality, or script safety has been verified.
- For candidates from the Creator Store or external channels, first verify the source and usage rights, then import them via insert_asset into game.ServerStorage for isolated review; before review, do not execute scripts, do not require ModuleScripts, and do not start Play. Use read-only instance and script tools to inspect the complete hierarchy and behavior, remove or reject unnecessary, obfuscated, or scripts with remote/data access capabilities, and only formally integrate licensed assets after review is complete.
- For models, record dimensions/axes, collision, hierarchy, material slots, texture resolution, number of transparency/effects, LOD or visibility strategy, and target device budget.
- For each asset, confirm the assetId/asset fields, usage permissions, loading paths, Streaming assumptions, and safe placeholder behavior when missing; do not guess IDs or copy content of unknown origin.
- Access is provided by the resource owner; gameplay/UI consume only registered resources and do not privately modify shared sources or produce unregistered copies on the consumption side.
- For generated or imported results, read back the real instances and references, and check loading, dimensions, materials, animation ownership, scripts, console errors, and resource budget.
Delivery and verification
- Deliver the resource registry, provenance and license evidence, real assetId, consumer paths, import or generation facts, performance budget, and known limitations.
- Verify actual integration via search_game_tree, inspect_instance, script_search, and script_read; mark states not provided by the tools as unverified.
- If the visual effect requires screenshot confirmation, provide screenshots and key points for manual inspection, and have the user confirm the displayed effect; screenshots must not be automatically analyzed as visual acceptance.
- Hand off animation and material consumer paths to gameplay development and feedback motion effects, and hand license evidence to release。
- When there is no proof of ownership, the asset carries unreviewed scripts, or performance overhead has no budget, mark it as blocking and provide a safe alternative path.
Resources that were found by search, generated successfully, or can be inserted must not be called authorized or QA-passed. Do not upload or publish resources without authorization.
Resource trust and handoff
- For imported models, inspect Scripts, LocalScripts, ModuleScripts, hidden objects, and auto-run behavior, and only consider integration after verification.
- Remain unintegrated when the resource author and publisher are inconsistent, the license semantics are unclear, or permissions cannot be verified.
- Indicate which models allow modification, which are shared sources, and which can only be used in a single consumer.
- For animations, indicate the rig type, character binding assumptions, animation owner, and target AnimationId.
- For dynamic models, particles, and transparent materials, state whether they may cause client frame cost, memory, or transparent sorting cost.
- Explain the alternative experience when resource loading fails, private resources are not visible, and moderation is delayed.
- Leave formal integration and version replacement to the single owner of the resource registry; consumers must not privately overwrite the original asset.
- Resource screenshots should correspond to the actual candidate version and consumer path; concept art must not be used in place of Studio results.
- The source, license, and actual scope of use of generated content must go into the release checklist.