There's no indication that legacy BodyMovers are deprecated

body-movers

#1

https://developer.roblox.com/articles/BodyMover

Legacy BodyMovers are deprecated, yet there is no indication of such either on the page linked above or the individual pages of the legacy BodyMovers.


#2

They’re deprecated? I know there’s new objects, but I didn’t think the old ones were deprecated


#3

AFAIK constraint BodyMovers superseded legacy BodyMovers and legacy ones have limited support left. Nothing public was really said except for the announcement of the new BodyMovers.


#4

I heard rumors about this, but I sincerely hope that this isn’t the case. I have started using them, and they are the foundations of my game.


#5

Even if it is. It shouldn’t affect your game at all. They just won’t continue to update them, hence ‘depreciated’.


#6

I think we’re still missing an equivalent for BodyVelocity so I’d be surprised if they’re deprecated as there was no indication.


#7

If I am correct, BodyMover works by changing the velocity of the object. If that is the case, maybe the same behaviors could be achieved using a ModuleScript. That way BodyMovers could be deprecated reliably (perhaps body movers could even rely on an official ModuleScript to retain future compatibility).


#8

I have some information on this when I was writing the BodyMover pages. I did ask about this and the response that I got was that BodyMovers are legacy, not deprecated. The difference is the intention on their removal - BodyMovers are so widely used they aren’t going anywhere anytime soon. Neither legacy nor deprecated things will be updated, but deprecated could be removed at any time. See also the legacy font for text UI objects.

In other words, it’s better practice if you use more modern alternatives.

Edit: I noticed you linked to what looks to be an out-of-date article on BodyMovers, rather than the API reference page of the BodyMover class. I don’t see much use in keeping the old article, if anyone has some suggestions on the content a help article should have I’m all ears. I did not author the article, but I did author the API reference page.