roblox-studio
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseRoblox Studio
Roblox Studio
Use the MCP tools to work against the place currently open in Studio. Keep new work under .
roblox-studioWorkspace/MapDrafts使用 MCP 工具操作当前在 Studio 中打开的 place。所有新工作都应放在 下。
roblox-studioWorkspace/MapDraftsPreflight
预检
- Confirm the MCP tools are available. If they are missing or reports offline, read setup.md.
studio_ping - Run before every work session.
studio_ping - Inspect the relevant hierarchy with ; use
studio_get_treeandstudio_find_instancesfor targeted reads.studio_get_properties - State the place and target root before changing anything. Never imply that Studio changed when the bridge is offline.
- 确认 MCP 工具可用。如果工具缺失或 报告离线,请阅读 setup.md。
studio_ping - 每个工作会话开始前运行 。
studio_ping - 使用 检查相关层级结构;使用
studio_get_tree和studio_find_instances进行定向读取。studio_get_properties - 进行任何更改前,说明当前 place 和目标根节点。bridge 离线时,绝不能暗示 Studio 已发生更改。
Choose a Workflow
选择工作流
- New map or major rebuild: read scene-spec.md, draft one SceneSpec, then use .
map_apply_scene_spec - Fast graybox: use , then validate the route before visual refinement.
map_create_blockout - Existing generated map repair: inspect first and batch related edits with .
studio_patch_instances - Before a substantial repair, use to keep a private local model backup.
studio_export_model - Focused property edit: use ; use
studio_set_propertiesonly inside a managed root.studio_create_instance - Terrain-only task: use with an explicit bounded size.
terrain_generate - Luau plus Rojo output: set to
codegen.targetand review every script before apply.both - Tool choice or argument uncertainty: read tools.md.
- 新建地图或重大重建:阅读 scene-spec.md,起草一份 SceneSpec,然后使用 。
map_apply_scene_spec - 快速灰盒:使用 ,然后在视觉细化前验证路线。
map_create_blockout - 修复现有生成的地图:先进行检查,并使用 批量执行相关编辑。
studio_patch_instances - 进行较大规模修复前,使用 创建私有本地模型备份。
studio_export_model - 定向属性编辑:使用 ;仅在受管理的根节点内使用
studio_set_properties。studio_create_instance - 仅处理地形:使用 ,并明确指定有限范围的大小。
terrain_generate - Luau 与 Rojo 输出:将 设置为
codegen.target,并在应用前审查每个脚本。both - 不确定工具选择或参数时:阅读 tools.md。
Build Loop
构建循环
- Translate the request into named areas, player route, scale, style, interactions, and acceptance checks.
- Preserve existing content unless the user explicitly asked to replace or edit it.
- For a SceneSpec, run with
map_apply_scene_spec.dryRun=true - Review target root, object count, services touched, filesystem writes, scripts, terrain, and reported risks.
- Apply with when the user requested the build or explicitly approved the dry run.
dryRun=false - Run on the exact returned map root with
map_validate.strictGeometry=true - Run for playable maps; use
map_readiness_checkonly for its named house contract.profile="house" - Inspect from useful angles with ,
studio_focus_instance, andstudio_set_camera.studio_visual_probe - When behavior matters, review a managed test ModuleScript returning . Raise an error on failure and return a JSON-serializable value on success. Call
function(args)withstudio_run_test, optionalconfirmToken="RUN_STUDIO_TEST"(modeorrun), andplay(integer 1-120, default 30). Tests execute ordinary project code, not a sandbox. Use a working copy and disable or mock persistent/external writes.timeoutSeconds - Repair concrete failures and repeat validation. Prefer a scoped patch over rebuilding a sound map.
- 将请求转化为命名区域、玩家路线、尺度、风格、交互和验收检查。
- 除非用户明确要求替换或编辑现有内容,否则应保留现有内容。
- 对于 SceneSpec,运行 ,并设置
map_apply_scene_spec。dryRun=true - 审查目标根节点、对象数量、涉及的服务、文件系统写入、脚本、地形和报告的风险。
- 当用户请求构建或明确批准 dry run 后,使用 应用更改。
dryRun=false - 对返回的准确地图根节点运行 ,并设置
map_validate。strictGeometry=true - 对可游玩地图运行 ;仅在其指定的 house 契约中使用
map_readiness_check。profile="house" - 使用 、
studio_focus_instance和studio_set_camera从有用的角度进行检查。studio_visual_probe - 当行为逻辑重要时,审查一个受管理的测试 ModuleScript,其返回值为 。失败时抛出错误,成功时返回可进行 JSON 序列化的值。调用
function(args)时,设置studio_run_test,并根据需要设置confirmToken="RUN_STUDIO_TEST"(mode或run)和play(整数 1-120,默认 30)。测试执行常规项目代码,而不是在沙箱中执行。使用工作副本,并禁用或模拟持久化写入和外部写入。timeoutSeconds - 修复具体失败项并重复验证。优先采用限定范围的补丁,而不是重建一个本身正常的地图。
Quality Bar
质量标准
- Include a SpawnLocation, readable route, safe landings, and an obvious destination for playable maps.
- Use unique, semantic names and models/folders for levels, buildings, routes, and systems.
- Ground normal maps with ; use
layout.grounding.mode="raycast"for a known elevation andmanualonly for intentional sky or void maps.none - Put doors, buttons, elevators, teleporters, and checkpoints in . Bind a behavior to existing visible geometry with
functionalObjectswhen possible.target - Treat validation warnings about terrain intersections, blocked doors, stair headroom, unreachable landings, or solid overlaps as repair work.
- Do not call a map visually ready from object counts or alone.
map_validate - Use for real viewport evidence after native permission is granted. Never substitute a desktop capture, invent a frame, or trigger permission dialogs during a background-only task. Review in-world text before sharing an image.
studio_capture_viewport
- 可游玩地图应包含 SpawnLocation、清晰可辨的路线、安全落点和明确的目的地。
- 为关卡、建筑、路线和系统使用唯一且具有语义含义的名称,以及 models/folders。
- 普通地图应使用 进行落地设置;已知高度使用
layout.grounding.mode="raycast",仅对刻意的天空或虚空地图使用manual。none - 将门、按钮、电梯、传送点和检查点放入 。尽可能使用
functionalObjects将行为绑定到现有的可见几何体。target - 将有关地形相交、门被阻挡、楼梯净空不足、落点不可达或实体重叠的验证警告视为需要修复的问题。
- 不能仅凭对象数量或 就认定地图在视觉上已准备就绪。
map_validate - 获得原生权限后,使用 获取真实的视口证据。绝不能使用桌面截图、虚构画面,或在仅后台运行的任务中触发权限对话框。分享图片前应检查场景内的文字。
studio_capture_viewport
Guardrails
防护规则
- Never request Roblox credentials, cookies, or .
.ROBLOSECURITY - Never send the bridge token anywhere except the local Studio plugin.
- Never use external asset IDs without a user-supplied allowlist.
- Keep direct edits and deletes inside managed roots. Deletes require the configured confirm token and explicit user intent.
- Do not enable to bypass declarative tools. If it is genuinely required, explain the exact code and risk first.
studio_execute_luau - Avoid remote code, HTTP, ,
require(assetId), and hidden loaders in generated Luau.loadstring
- 绝不请求 Roblox 凭据、cookies 或 。
.ROBLOSECURITY - 除本地 Studio 插件外,绝不能将 bridge token 发送到任何位置。
- 未经用户提供允许列表,绝不能使用外部 asset ID。
- 将直接编辑和删除操作限制在受管理的根节点内。删除操作必须使用已配置的确认 token,并获得用户的明确意图。
- 不得启用 来绕过声明式工具。如果确实需要使用,应事先说明具体代码和相关风险。
studio_execute_luau - 避免在生成的 Luau 中使用远程代码、HTTP、、
require(assetId)和隐藏加载器。loadstring
Handoff
交付说明
Report the exact map root, manifest path, Rojo files, validation/readiness result, playtest result, warnings left, and the next manual Studio check. Separate verified results from visual judgment.
报告准确的地图根节点、manifest 路径、Rojo 文件、验证和就绪状态检查结果、试玩测试结果、遗留警告以及下一项需要手动在 Studio 中完成的检查。应将已验证的结果与视觉判断分开报告。