Bigger bet: Unity Editor bridge for compile errors, console and tests (build vs integrate)
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 25/100
- Issue 类型
- 功能
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
调研方向
Start with the proposed Unity Editor bridge and MCP tools, then do the short competitive scan named in the issue to compare building with integrating an existing bridge. The work spans a design decision, a UPM package, and MCP server changes; done means the design doc compares both approaches and read-only compile errors and console access work end to end in Unity 6.
由索引模型根据 Issue 内容生成。
描述
Why it matters
Everything today is static text. Several open-source Unity MCP servers already bridge into a running Unity Editor (reading the console, scenes, compile errors, running tests). This project's distinct strength is curated, opinionated Unity 6 guidance. Combining that with a lightweight editor bridge would make it a complete AI workflow for Unity, rather than a reference pack competing on docs alone.
Proposal (bigger bet, phased)
- Read-only bridge: a small UPM package that runs in the Editor and exposes compile errors, console logs, the active scene hierarchy, and Test Runner results to the MCP server (local socket or files under
Library/). - New tools:
get_compile_errors,get_console,run_tests(batchmode or via the bridge),get_scene_summary. - Close the loop: skills tell the agent to scaffold, then check compile errors, then fix, then run tests.
- Later: guarded write actions (create GameObject, assign component) behind explicit opt-in.
Alternative: integrate or interoperate with an existing Unity MCP bridge and position this project as the "knowledge and conventions" layer that pairs with it. Decide based on a short competitive scan.
Done when
A design doc exists comparing build vs integrate, and phase 1 (read-only compile errors and console) works end to end in Unity 6.
- 主要语言
- C#
- 星标
- 4
- 派生
- 0
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
TMHSDigital/Unity-Developer-Tools 的其他 Issue
-
难度 4/5 3-5 天 新手友好度 35/100
-
ci priority: low skills
难度 3/5 1-2 天 新手友好度 55/100
-
good first issue skills testing
难度 3/5 1-2 天 新手友好度 58/100
-
ci priority: medium testing
难度 4/5 1-2 天 新手友好度 57/100
-
documentation marketing priority: medium
难度 5/5 一周以上 新手友好度 35/100
查看 TMHSDigital/Unity-Developer-Tools 的全部 Issue
相似的 Issue
-
type:task ux
难度 2/5 1-3 小时 新手友好度 72/100
elsa-workflows/elsa-foundation#5253 ·
维护者通常 1 天内回复