Mobs do not immediately stop when removing their movement via component group.

Partner Rank: 4

Partner Team Reporting: Noxcrew

Verification builds: 1.9.0.5_beta_9-4_rc1

Summary:

Removing a mob's ability to move via component group does not cause the mob to immediately stop moving. I believe this is happening because the mob isn't releasing it's previous goal, which in this case is to force it to panic. In the example world/attached video, I have added "minecraft:scale": {"value": 3.0} to the component group at the same time I have removed "minecraft:movement": { "value": 0.3 } in favor of "minecraft:movement": { "value": 0 }. The mob also swaps variants at this point. You can see clearly that the mob does not stop immediately when this swap happens.

 

Impact:

We're working with limited tools to try to make unique mobs, and currently swapping component groups to trigger simultaneous variant/behavior/sound interchanges is our best tool. When things don't happen when they should, it hurts our ability to make things polished and convincing. This is not blocking our content, but will allow us to make our stuff to a higher quality when it is fixed.

Repro Steps:

1. Ask for the bpmovementbug.mcworld from @greggo on slack
2. Load the world, /summon cat
3. Damage the cat
4. Watch him run around, and note how his movement continues even after the variant/size change happens.

Observed Results:

The cat moves after the size/variant change happens.

Expected Results:

The cat should stop moving after the size/variant change happens.

Screenshots/Videos attached: 

 https://drive.google.com/file/d/1kO20xFjJNZ45JX48GXAVo-L8umPb__aF/view

 

Regression Builds:

I have no reason to believe this has ever not worked this way.