I think Muse should suggest code with implemented best practices like not making public fields just to see them in the inspector and adding a required when the script expects a component attached to the game object.
Another example is suggesting code with better performance. I asked it how to make an object move over time and it suggested moving the object by multiplying moveDirection.normalized * moveSpeed * Time.deltaTime;. This is not wrong and the code works but ideally we should change the order and put the Vector in the last position.
I know those are small things that for most games won’t have a noticeable impact, but people will be using Muse to learn and ideally, we should learn the best practices too.
1 Like