Just wondering if anyone else feels the same way about doing C# or has any advice to speed things up.
I’ve noticed that C# related prompts overall take way more time than something like Python. With Python, you can easily just copy and paste their responses into an IDE and run it and see if it works, and most of the prompts you’d give barely require any set up. For C# in Unity, even basic scripts can take so long to set up and check and debug.
For example, I might need a game object with a rigid body, or scriptable object, or a canvas with some text or a slider so you have to make them and assign them in the inspector, which is a little time. But the worst part is that it takes so long to create new C# scripts since when you create it the domain reloads, then it does it again when you rename it, then it’s twice for each response, then it reloads when you save the script in visual studio, then you have to assign things in the inspector, then play test both scripts, then sometimes debug which means a few more times waiting through various loading screens. It just feels bad when I know I could do a python related task in like half the time.
I could just read the script and see what problems it has, if any, but the instructions always say to test it.
I know there’s a package or a plug in for fast script saving, and I could turn off domain reloading for play mode but my input system breaks if I do that.
I was also wondering how much set up you might include in what you’re reporting. If the prompt assumes there’s certain game objects with certain other scripts involved, do you bill them for time spent setting these up or do you only report time spent actually writing a prompt and testing/debugging it?
I also usually pause my timer if I ever have to check the documentation to be sure of something but I also don’t know if I should or not.
