I know what most devs would say: “Don’t use tools, oh my gosh!” but they can be really good for prototyping something and they’re very intuitive to use.
The one reason I want Tool to make a Motor6D instead of a Weld is pretty obvious: animations. I want it to be able to play animations. In most animated-handle tools that I make, I have to do a really awkward exchange system to turn the weld into a motor. This very minute(?) change in how Tools work saves a lot of code.
Thanks.
I had the same thought a few days ago. Hoping it doesnt break anything that looks for a weld named RightGrip and not a Joint in general
This is probably a stupid question: Why don’t you just have the tool handle invisible and use a separate part with its own Motor6D for collisions and animations?
Code. I’m trying to save how much of it I write.
Alternatively, could you add a small new instance that inherits everything from Tool except creates a motor instead of a weld? Call it MotorTool or something? This way we don’t have any accidental backwards-compatibility issues?
I really believe that this would increase the quality of gear at the very least.
I was just about to make this feature request. I’m programming some tools somebody built, and I wanted them to make the poses and animations. I looked into how to do that myself, and I had to explain to them that they need to paste a program I wrote into the command line and run it to replace the RightGrip with a Motor6D. Additional code is then required to do the same thing when the tool is selected. This is not nice.