Clarify how AnimationTrack:Stop() with a fadeTime of 0 affects Motor6Ds

[Starveldt]

Changes

When calling AnimationTrack:Stop() with a fadeTime of 0, poses do not freeze under all circumstances. It happens due to the MaxVelocity of Motor6Ds in the rig being zero, meaning they cannot return back to their desired angle (since they inherit Motors).

I believe the misconception in the passage I edited was due to the default StarterCharacter rigs having the MaxVelocity of all joints set to zero rather than something like tau (which should be optimal, given MaxVelocity is in radians). I've also tested this below.

Rig with MaxVelocity set to 0 for all Motor6Ds, calling AnimationTrack:Stop(0):

Rig with MaxVelocity set to tau for all Motor6Ds, calling AnimationTrack:Stop(0):

Bones are not affected by this issue since they do not inherit Motor.

Checks

By submitting your pull request for review, you agree to the following:

• This contribution was created in whole or in part by me, and I have the right to submit it under the terms of this repository's open source licenses.
• I understand and agree that this contribution and a record of it are public, maintained indefinitely, and may be redistributed under the terms of this repository's open source licenses.
• To the best of my knowledge, all proposed changes are accurate.

[github-actions]

Hi @Starveldt, thanks so much for helping improve the Roblox creator documentation! Our technical writing team will review your pull request soon. In the meantime, please ensure you've read through the README.md, contribution guidelines, and style recommendations.