Bigger bet: Unity Editor bridge for compile errors, console and tests (build vs integrate)

Aberta
#45 1 comentário 0 reações 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
25/100
Tipo de issue
Funcionalidade
Clareza
Claramente especificada
Status de atividade
Ativa
Stack de tecnologia
csharp, unity

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

feature priority: low

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)

  1. 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/).
  2. New tools: get_compile_errors, get_console, run_tests (batchmode or via the bridge), get_scene_summary.
  3. Close the loop: skills tell the agent to scaffold, then check compile errors, then fix, then run tests.
  4. 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.

Linguagem predominante
C#
Estrelas
4
Forks
0
Métricas de merge de PRs
Nenhum PR com merge em 30d

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de TMHSDigital/Unity-Developer-Tools

Todas as issues de TMHSDigital/Unity-Developer-Tools

Issues semelhantes

Mais issues de C#

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.