AnimationTrack:AdjustWeight improperly replicates

Note: This happens when Workspace.FilteringEnabled is true or false

AnimationTrack:AdjustWeight leads to some interesting results when played on a Server/Test Server.

Attached it a repro file.

The following videos attempt to demonstrate what’s going on. Pay close attention to the Head part

Working as intended!

(left server, right client)

You can see in the Test Server example that neither screen is accurate.
On the left its business as usual
On the right, both animation weights appear to be set to 1 (with the Down animation taking priority due to being play second)

WeightRepro.rbxl (13.5 KB)


Not surprised. Animation weights are hardly supported as it is.

Er… yes. That’s why I made this bug report…


Just a side comment, hoping ROBLOX will consider supporting it more than they currently are.

Everything in the Repro is in a Script inside of the Dummy in Workspace.

This is still a thing, and I keep running into it. Over the summer @Davidii had it fixed and enabled it but was turned off and has yet to be re enabled.

I currently have to play everyone’s animations locally per client to take advantage of weight. It’s not an ideal work around to the bug and it should replicate the same as speed.


I didn’t know this got turned off. I thought it worked fine… hm.

This issue is still very much affecting developers today, preventing me from being able to implement directional movement animations through blending walk cycles.

As many games are working around this issues by creating their own replicating systems, or even resorting to semi-custom characters, it would be fantastic if this is looked into. Especially since @Davidii worked on a solution in the past and the Speed property of animations does replicate correctly, which is nearly identical in the ways of interaction and replication.

Upon further investigation I found out that there is one working way to replicate the weight of animations to other clients:

  • Play animations with a weight of 1 (not 0)
  • Ensure AdjustWeight never sets to 0 (0.01 at minimum)

The issue seems to be related to other clients stopping animations when Weight is set to 0. By using this workaround you can achieve your desirable effect until Roblox fixes this issue.

Here is another bug report about the 0-weight issue specifically:


This is still extremely frustrating and affecting development. At times, the replication of animations is seemingly random – I have 4 different animation tracks with the exact same asset id; when the weights are changed to different values, only one animation actually replicates to other clients. Even when one animation is then returned to a weight of 1, and the other animations to a weight of 0.01, the animation will still not play on other clients. There is seemingly no method to the madness.

This problem can be alleviated by using different asset ids (even if the actual animation is exactly the same). This sort of unexpected behaviour should not be happening, especially when you can break the replication of Roblox’s own default character animation script by simply setting the asset IDs of the walking and running animation to the same asset.