Feature/recompile scripts tool #83
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I want the MCP to support the following workflow: make changes → recompile → run tests → repeat. I want it to run in the background so it doesn’t block me from working on other tasks and projects.
To achieve this, I made two changes: implemented a
recompile_scriptstool and movedMcpUnityServer.Instanceinitialization to a method decorated with[DidReloadScripts]. This is not equivalent to the previousEditorApplication.delayCallapproach, but it is sufficient to wait until the end of a domain reload and, unlikedelayCall, it doesn’t require the Editor to be focused. Note, however, that I couldn’t exhaustively test this change across all tools and intended workflows, because I don’t fully understand the exact edge cases you had in mind while designing theMcpUnityServer. That said, I’ve used the MCP after applying these changes, and had no issues with it.