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

Ouverte
#45 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
25/100
Type d'issue
Fonctionnalité
Clarté
Clairement spécifiée
Activité
Active
Stack technique
csharp, unity

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
C#
Étoiles
4
Forks
0
Métriques de merge des PR
Aucune PR mergée en 30 j

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de TMHSDigital/Unity-Developer-Tools

Toutes les issues de TMHSDigital/Unity-Developer-Tools

Issues similaires

Plus d'issues C#

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.