Question about the project's vision

[jsjtxietian]

Hi, Thank you for sharing this project! I find it very interesting and appreciate the effort you've put into it. I see a lot of potential in this project.

I have a few questions regarding the vision and future direction of this project. Could you share your thoughts on what you aim to achieve with it in the long run? Are there any specific goals or features you are planning to implement?

Additionally, I have some small observtions/suggestions:

• I suspect Can't run Add component #3 could be related to the fact that the code did not add enough assembly for the Mono's built-in compiler, for example, After I add options.ReferencedAssemblies.Add(typeof(UnityEngine.BoxCollider).Assembly.Location); cursor can help me add a box collider compoment. A lot of work needs to be done for a perfect experience. Also maybe can use Roslyn instead of mono in the future?
• More API(Available Tools) would be helpful and maybe a more structured way of defining and implementing them.
• Better UI to show the activity of Unity's behaviour instead of just logging them.

I’d love to hear your thoughts on these points. I'm willing to help in any way I can. Thanks again for your work!

[jackwrichards]

Hey! Thanks for the feedback - it's super helpful to hear from users about what they need!

You're absolutely right about the assembly references. Right now I'm only including the basics:

options.ReferencedAssemblies.Add(typeof(UnityEngine.Object).Assembly.Location);
options.ReferencedAssemblies.Add(typeof(UnityEditor.Editor).Assembly.Location);

I should definitely add more common Unity assemblies like BoxCollider, Rigidbody, etc. That would make adding components way more reliable.

The Roslyn idea is pretty cool too! It would give us better error messages and support for newer C# features. Right now I'm using Mono's compiler which is... well, let's just say it could be better 😅

As for the UI, yeah it's pretty basic right now. I could make it way more useful with stuff like:

• A proper scene hierarchy view
• Better log filtering
• Visual feedback for what's happening
• Maybe even a mini-inspector

I am looking for contributors. I could definitely use help with:

• Testing and finding bugs
• Adding more Unity component support
• Making the UI better
• Creating new tools
• Writing docs

The project is getting pretty popular huh? In the near future I am looking to:

1. Add a CONTRIBUTING.md file with guidelines
2. Set up issue templates for bugs and feature requests
3. Add some basic project documentation
4. Maybe set up a Discord server for the community?

Let me know if you want to contribute anything/help!

[jsjtxietian]

Thanks for the explanation! I would like to help all the point you mentioned!

I would suggest first can clean the file a bit, maybe seperate tools from connection file so it's more organized and easy to extend.

The ability to excute C# code generated by llm directly is awosome. We can cache the Microsoft.CSharp.CSharpCodeProvider so we don't have to create a new one each time, speed up the process (especially when many assembly are added to it in the future).

Also I found another repo similar to this one, we can get some inspirations about what tools others might need https://github.com/CoderGamester/mcp-unity/tree/main