openmotion-game
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseOpenMotion Game Studio
OpenMotion Game Studio
Turn a one-line brief into a playable local game. Resume an explicitly supplied game id; otherwise use with prompt, multiplayer and optional genre/style/setting. Read before editing. Local templates are read-only: use the market's Remix action to create an owned draft. OpenMotion does not run an internal game Agent.
openmotion_game_createopenmotion_game_get- Interview only for missing decisions, with at most two short questions: solo/co-op/versus multiplayer mode, and whether to publish to the local market. Reuse answers and authorization already supplied.
- Read game design, style and genre recipes and quality floor. Choose the matching recipe (free-form briefs: pick the closest and say which) and copy its must-haves and acceptance checks into the plan. The quality floor is mandatory: a game-first full-screen playfield (never a landing-page layout with a hero headline beside a small game box), a goal readable in three seconds, at least three kinds of feedback, a 30–120 s session with a ramp, restart in two seconds or less, and characters with real silhouettes instead of bare primitives. Propose the visual direction and one English 60–90 word style formula covering rendering, shapes, palette roles, light and perspective. Preserve explicitly selected style; resolve unclear direction before costly assets. Save the formula in and write
design/style.mdwithdesign/plan.md: experience formula, target metrics with numeric thresholds, reference route must win / idle must lose, and the wave/difficulty plan. Writeopenmotion_game_write_fileswith at least asset, source, license and cost. Starter drafts are inputs to revise for this brief, not completed acceptance records.design/assets.csv - Optional in-game art/icon generation: discover configured media models, state the actual cost or that it is unknown, and obtain the user's spending approval before . Never invent a price, quota or provider capability. Poll the original job; a queued job is not an asset. No automatic paid retry. Use textures, 2D, 3D, procedural motion and audio only as needed. The game write tool accepts text, not binary uploads: use available authorized local file operations to place completed binary assets in this game's
openmotion_generate_asset; otherwise use procedural art and report the limitation. Never write binaries as text/base64.assets/ - Set with
building. Writeopenmotion_game_set_statusand optionalindex.html,client.js,style.css,logic.jswithassets/**, id and a batch ofopenmotion_game_write_files. Preserve the game id and existing decisions. Read flow and logic contract before multiplayer authoring. Multiplayer shooter or 3d briefs receive the offline co-op kit, vendored Three.js and CC0 Mage/Knight characters; other briefs receive the arcade-2d kit (full-screen canvas, local fixed-step loop over logic.js, keyboard/mouse/touch/one-button input, feedback helpers, best score, portrait switch, test hook and pilot-based referenceRoute). Start from the kit you received; replace its sample rules, art and strings, keep its loop, input layer and hooks, and preserve relative paths and licenses. Rooms support late joins and 30-second session-token recovery in one local process, not internet hosting. Code controls, win/loss/restart and loading/error states, not just an attractive scene.{path,content} - Before publication run twice with the planned player count and tick budget:
openmotion_game_simulatemust finish with winners, andscripts:"reference"must finish with no winners and the intended loss state. A tick-budget timeout is not a loss. Use the game-provided exportedscripts:"idle"or explicit tick routes; keep these ordinary validated actions, never state edits. Record exact inputs, terminal ticks, summary and known limits inreferenceRoute(playerIndex). Rundesign/verification.md; fix diagnostics and address advisory warnings for missing covers or fewer than 20 approximate changed starter-kit lines. A low line count is a signal to inspect the requested gameplay, not an instruction to add filler. Read the rubric. Never operate, attach to or capture the user's visible browser, existing Chrome profile or desktop. Useopenmotion_game_validatefor server-owned headless testing, with 1–4 clients sharing a room and meaningful per-client key/mouse scripts. Review console errors, failed requests, screenshots, roomJoined/playerCount and RAF pacing and each pass/fail assertion. The kit exposesopenmotion_game_playtestandwindow.__omGame={getState,getStats,sendAction}(FPS, draw calls, entities, tick). Playtest reads authoritative snapshots, verifies player count and phase, requires scripted net displacement >0.5 world units by default, and checks horizontal overflow at 390×844. Missing hooks fail state assertions; omitted scripts perform a short W movement on each client. Test both players' movement/skills, plus deterministic rule tests for damage, revive, cooldowns and restart. Co-op defaults allow one player to start. Touch controls are required; distinguish implemented touch controls from actual touch-device acceptance. If Chrome/loopback is unavailable, report the exact blocker and unverified checks; never fall back to the user's browser.?debug - Set concise title/description/controls and translations through
zh-CN. Useopenmotion_game_update_metafor every gameplay cover, with optional room, input actions and delay. It starts isolated headless Chrome on the server, screenshots only the game canvas/#game root at 1280×720 toopenmotion_game_capture_cover, and sets cover metadata. Never use a desktop/full-window screenshot containing tabs, address bars, profiles or other apps. Imported/generated image metadata must be at least 960×540 and 16:9 ±5%; image generation still requires spending approval and does not replace the game-only capture requirement. Inspect the capture diagnostics and image rather than assuming a nonempty PNG proves gameplay. Set ready after checks; publish locally only with existing publication authorization. Update design/verification.md with tested revision, inputs, thresholds, actual results and gaps; never leave starter pending rows presented as completed. Validation reports one non-blocking reminder per missing design artifact. Report returned warnings, actual screenshot paths and playtest evidence. Publish returns three nextSteps prompts, using the plan’s Follow-up opportunities section when available; show them as optional user prompts and do not execute them automatically. Server headless results do not establish human fun, real GPU/mobile performance or audible quality.assets/cover.png - Final message to the user (plain language, the user's language, no tool names, file dumps, ids or JSON): one bold line saying what is playable now (say "playable first version" when limits remain); the play link; two to four bullets on how to play, how to invite friends (multiplayer) and the controls; what was verified and what was not (human fun, real devices, sound); the cost note (no paid generation used, or the approved spend); the cover path. If asked about cost, report only exact spend from tool results, otherwise say it is unknown and name what you will not generate from now on.
For MCP-only hosts, begin with ; its linked references are available through workflow resources. Model execution and optional media tools depend on the connected host's actual discovery. If is absent, explain that boundary; do not claim that another tool name is available without checking.
openmotion://workflow/game/startopenmotion_generate_asset将一行需求简述转化为可在本地游玩的游戏。如果明确提供了 game id,则继续该游戏;否则使用 ,传入 prompt、multiplayer 以及可选的 genre/style/setting。编辑前先读取 。本地模板是只读的:使用市场中的 Remix 操作创建一份归你所有的草稿。OpenMotion 不会运行内部游戏 Agent。
openmotion_game_createopenmotion_game_get- 仅就缺失的决策进行访谈,且最多提出两个简短问题:单人/合作/对抗多人模式,以及是否发布到本地市场。复用已提供的回答和授权。
- 阅读 游戏设计、风格 和 类型配方与质量底线。选择匹配的配方(对于自由形式的需求:选择最接近的一种并说明),并将其必备项和验收检查复制到计划中。质量底线是强制要求:以游戏为中心的全屏游玩区域(绝不能采用在大型标题旁放置小游戏框的落地页布局)、三秒内即可读懂的目标、至少三种反馈、包含难度爬升的 30–120 秒单局、两秒以内重启,以及拥有真实清晰轮廓而非仅有基础几何体的角色。提出视觉方向,并给出一条英文 60–90 词风格公式,涵盖渲染方式、形状、调色板角色、光照和透视。保留明确选定的风格;在生成成本高昂的素材前解决不明确的视觉方向。将公式保存在 中,并使用
design/style.md编写openmotion_game_write_files:体验公式、带数值阈值的目标指标、reference route 必须获胜 / idle 必须失败,以及波次/难度计划。编写design/plan.md,至少包含 asset、source、license 和 cost。初始草稿是供你针对当前需求进行修改的输入,而不是已完成的验收记录。design/assets.csv - 可选的游戏内美术/图标生成:发现已配置的媒体模型,说明实际费用或说明费用未知,并在调用 前获得用户的消费批准。绝不臆造价格、配额或提供商能力。轮询原始任务;处于排队状态的任务不算素材。不得自动付费重试。仅按需使用 纹理、2D、3D、程序化运动 和 音频。游戏写入工具接受文本,不接受二进制上传:使用可用且已授权的本地文件操作,将完成的二进制素材放入该游戏的
openmotion_generate_asset;否则使用程序化美术并报告限制。绝不把二进制内容写成文本/base64。assets/ - 使用 将状态设置为
openmotion_game_set_status。使用building编写openmotion_game_write_files以及可选的index.html、client.js、style.css、logic.js,传入 id 和一批assets/**。保留游戏 id 和已有决策。编写多人功能前先阅读 流程与逻辑约定。多人射击或 3D 需求会获得离线合作工具包、随附的 Three.js 以及 CC0 的 Mage/Knight 角色;其他需求会获得 arcade-2d 工具包(全屏 canvas、基于{path,content}的本地固定步长循环、键盘/鼠标/触控/单按钮输入、反馈辅助函数、最高分、竖屏切换、测试钩子以及基于 pilot 的logic.js)。从收到的工具包开始;替换示例规则、美术和字符串,保留其循环、输入层和钩子,并保留相对路径和许可证。房间支持成员中途加入,并支持在单个本地进程内进行 30 秒的 session token 恢复,而不是互联网托管。代码要实现控制、胜利/失败/重启以及加载/错误状态,而不只是营造一个好看的场景。referenceRoute - 发布前,使用计划中的玩家数量和 tick 预算运行 两次:
openmotion_game_simulate必须以存在获胜者结束,scripts:"reference"必须以没有获胜者且进入预期失败状态结束。tick 预算超时不算失败。使用游戏提供的导出函数scripts:"idle"或显式 tick 路由;将这些保持为普通的已验证操作,绝不能直接修改状态。在referenceRoute(playerIndex)中记录精确输入、终止时的 tick、摘要和已知限制。运行design/verification.md;修复诊断问题,并处理关于缺少封面或相对初始工具包改动少于约 20 行的提示性警告(advisory warning)。较低的改动行数意味着应检查所要求的玩法,而不是为了凑数添加填充内容。阅读 评分标准。绝不操作、连接或捕获用户可见的浏览器、现有 Chrome 用户配置或桌面。 使用openmotion_game_validate进行由服务器托管的无头测试,让 1–4 个客户端共享一个房间,并为每个客户端提供有意义的键盘/鼠标脚本。检查控制台错误、失败的请求、截图、openmotion_game_playtest/roomJoined、RAF 节奏以及每项通过/失败断言。工具包暴露playerCount和window.__omGame={getState,getStats,sendAction}(FPS、draw calls、实体数、tick)。Playtest 会读取权威快照,验证玩家数量和阶段,默认要求脚本造成的净位移 >0.5 世界单位,并检查 390×844 下的水平溢出。缺少钩子会导致状态断言失败;省略脚本时,每个客户端会执行一段短暂的 W 移动。测试两名玩家的移动/技能,并针对伤害、复活、冷却和重启运行确定性规则测试。合作模式默认允许一名玩家开始。触控控制是必需的;要区分“已实现触控控制”和“已在真实触控设备上验收”。如果 Chrome/loopback 不可用,报告确切阻塞项和未验证的检查;绝不回退到用户的浏览器。?debug - 通过 设置简洁的标题、描述、操作说明和
openmotion_game_update_meta翻译。每张游戏封面都必须使用zh-CN,可选择房间、输入操作和延迟。它会在服务器上启动隔离的无头 Chrome,仅截取游戏 canvas/#game 根节点,输出为 1280×720 的openmotion_game_capture_cover,并设置封面元数据。绝不能使用包含标签页、地址栏、用户配置或其他应用的桌面/整窗截图。导入/生成的图像元数据至少应为 960×540,且为 16:9 ±5%;图像生成仍需获得消费批准,且不能替代仅使用游戏画面捕获这一要求。检查捕获诊断信息和图像,不要假定非空的 PNG 就证明存在游戏画面。检查完成后设置为assets/cover.png;仅在已有发布授权时在本地发布。使用经过测试的修订版、输入、阈值、实际结果和差距更新ready;绝不能把初始素材中仍待处理的项目当作已完成项展示。每个缺失的设计产物,验证报告都会给出一条非阻塞提醒。报告返回的警告、实际截图路径和 playtest 证据。发布会返回三条 nextSteps 提示;当计划中有design/verification.md部分时,使用其中的内容;将其显示为可选的用户提示,绝不自动执行。服务器无头测试结果不能证明游戏是否好玩、真实 GPU/移动设备性能或音质。Follow-up opportunities - 给用户的最终消息(使用通俗语言、用户所用语言,不含工具名称、文件转储、id 或 JSON):用一行粗体说明当前可玩的内容(仍有局限时写“可玩的首个版本”);提供试玩链接;用 2–4 个要点说明如何游玩、如何邀请好友(多人模式)以及操作方式;说明已验证和未验证的内容(真人乐趣、真实设备、声音);给出费用说明(未使用付费生成,或注明获批支出);提供封面路径。如果被询问费用,仅报告工具结果中的准确支出,否则说明费用未知,并说明从现在起不会生成哪些内容。
对于仅支持 MCP 的宿主,先执行 ;其关联的 references 可通过 workflow resources 获取。模型执行和可选媒体工具取决于所连接宿主实际发现到的能力。如果 不存在,请说明这一边界;未经检查,不得声称有其他工具名称可用。
openmotion://workflow/game/startopenmotion_generate_assetAfter publication: optional gameplay trailer
发布后:可选的游戏预告片
Offer to make a gameplay trailer after publishing. With the user's request, call with , then read . Do not claim completion until status is ; report and . This creates a separate editable native Motion project in the user's project catalog. Use the existing project-opening operation to open it when requested. The recording is silent; no paid music or asset generation is implied. Never use the user's browser or desktop for trailer footage.
openmotion_game_trailer{id,action:"start"}{id,action:"status"}readyprojectIdvideoUrlThe server records three real five-second headless gameplay clips at 1280×720, builds a roughly 19-second title/highlights/Play now composition and uses the existing verified MP4 export pipeline. Chrome, ffmpeg and the pinned native export runtime must already be available; the tool does not download or install them. Automated movement/fire/skills are sampling inputs, not proof of a winning run or human acceptance. Inspect the footage and final video. Failed jobs retain their clips and any created project; report the error and unverified stages.
发布后,主动提供制作游戏预告片的服务。收到用户请求后,调用 并传入 ,然后读取 。在状态变为 前不得声称完成;报告 和 。这会在用户的项目目录中创建一个独立且可编辑的原生 Motion 项目。需要时,使用现有的项目打开操作将其打开。录制内容为静音;不包含付费音乐或素材生成。绝不使用用户的浏览器或桌面来拍摄预告片素材。
openmotion_game_trailer{id,action:"start"}{id,action:"status"}readyprojectIdvideoUrl服务器会录制三段真实的五秒无头游戏片段,分辨率为 1280×720,制作约 19 秒的标题/精彩片段/立即游玩合成视频,并使用现有的、已验证的 MP4 导出流程。Chrome、ffmpeg 和固定版本的原生导出运行时必须已经可用;该工具不会下载或安装它们。自动移动、射击和技能操作只是采样输入,不能证明完成了一次获胜流程或获得真人验收。检查 footage 和最终视频。失败的任务会保留片段和任何已创建的项目;报告错误和未验证的阶段。
Mandatory multiplayer entry acceptance
强制多人加入入口验收
Every multiplayer game joins on load from ; generate a short random room id when missing. The local play entry redirects missing-room URLs to and preserves other query parameters on both API prefixes. The client must still handle a missing parameter for standalone/embedded use, including opaque sandbox origins where history replacement may fail. Never ask the player to type a room code or perform a Join room step.
new URL(location.href).searchParams.get('room')?room=...- Opening the game joins within five seconds, with no click or typing.
- Lobby displays the room code, a Copy invite link button and one primary Start button; one player can start. Copy uses the current room in the invite URL. No room-code input or Join room button, on desktop or touch.
- passes: room-code text inputs or Join room/加入房间 buttons in index.html/client.js are blocking diagnostics. A missing room-query read is an advisory warning; static heuristics do not prove automatic joining.
openmotion_game_validate - reports the
openmotion_game_playtestassertion passed for every client before it clicks Start or executes scripts. Evidence is the room socket's joined message orautoJoinwith selfId and the corresponding player. Joining after five seconds or only after an input fails, even if later gameplay works. Report unavailable Chrome/loopback separately.window.__omGame.getState()
See provenance and execution boundaries; the original MIT notice is retained in LICENSE-HIGGSFIELD.
每个多人游戏都必须在加载时通过 加入;当参数缺失时生成一个短随机 room id。本地试玩入口会将缺少 room 参数的 URL 重定向到 ,并在两个 API 前缀下保留其他查询参数。客户端仍必须处理参数缺失的情况,以支持独立/嵌入使用,包括 history replacement 可能失败的不透明 sandbox origin。绝不要求玩家输入房间代码或执行“加入房间”步骤。
new URL(location.href).searchParams.get('room')?room=...- 打开游戏后五秒内自动加入,无需点击或输入。
- 大厅显示房间代码、“复制邀请链接”按钮和一个主要“开始”按钮;一名玩家即可开始。复制操作使用邀请 URL 中的当前房间。无论桌面端还是触控端,都不应有房间代码输入框或“加入房间”按钮。
- 通过:
openmotion_game_validate/index.html中的房间代码文本输入框或“Join room/加入房间”按钮属于阻塞性诊断。缺少读取 room 查询参数的行为属于提示性警告(advisory warning);静态启发式检查无法证明自动加入。client.js - 报告每个客户端的
openmotion_game_playtest断言均已通过,然后才点击“开始”或执行脚本。证据应为 room socket 的 joined 消息,或autoJoin中包含 selfId 和对应 player。加入时间超过五秒,或只有在输入后才加入,即使之后玩法正常也算失败。另行报告 Chrome/loopback 不可用的情况。window.__omGame.getState()
参阅 来源与执行边界;原始 MIT 声明保留在 LICENSE-HIGGSFIELD 中。