As a Roblox developer, it is currently too easy to mistakenly use HTTP instead of HTTPS inside an AnimationId property.
If Roblox is able to address this issue, it would improve my development experience, and the development experience of many others, because this animation-not-replicating problem would occur way less frequently.
If you make it a habit to use the rbxassetid:// protocol, it makes it harder to fall into this pitfall, and it’s better practice than linking the roblox.com location of the asset file since the former is agnostic to where the asset is actually hosted.
Oh okay – I wouldn’t take the default animation script as best-practice, it’s really poorly written. I’m guessing no engineer has touched that in a while.