no but the leaked scripted file from when garou was added says so 
1 Like
linear velocities suck bro. I already tried both and bodyvelocities are overall simpler ,better and more efficient tbh i dont even know why they deprecated them
1 Like
Like I said, i got a pretty smooth dash by using linear velocity and using a for loop (on the client). Also linear velocity isn’t even that complicated.
1 Like
maybe they changed it since then 
1 Like
well, at the end of the day everyone has their favorite velocity that they feel more comfortable with i guess
1 Like
ah yes they would change it to the laggier linearvelocity which doesn’t even send you to the destination properly half the time because of how laggy it is
1 Like
yip yap why would roblox deprecate it and make it worse, that wouldn’t make sense
1 Like
Joined Nov 26 '23 makes sense. also i don’t recall asking for you to act all high and mighty while spreading obvious and proven misinformation. don’t bother bringing logic into the BodyMovers deprecation there was nothing wrong with BodyMovers they were fine. Roblox just wants to act all corporate and versatile with their incomplete new instances with a bajillion new properties and more complex and unnecessary physics calculations that cause more lag and issues for everyone at the end of the day. It makes sense why you would willingly spread misinformation and use the laggier alternative though because “An idiot admires complexity, a genius admires simplicity". Not that i’m saying i’m a genius of course in this case it’d be more like “An idiot admires complexity, a normal human being admires the complete non buggy bodymovers”. Also notice how when you scroll down on the thread half of it is people arguing with you because you’re spreading ovbious misinformation?
You didn’t need to write a paragraph 
. If roblox were to deprecate something, it would be because it doesn’t work properly. So why would roblox deprecate something fully functional? It wouldn’t make any sense. Also the join date argument is pretty dumb. If anything, you are acting high and mighty just because you joined before me.
1 Like
Roblox sometimes deprecates things that are fully functional because they are superseded by better alternatives. The reasons for this could be that the newer versions are optimized better or simply easier to use. No matter the case, you shouldn’t use anything that’s deprecated, because on top of alternatives being better, Roblox sometimes eventually removes deprecated things entirely, so your game would end up breaking in the future.
1 Like
1 Like
Firstly, don’t attack people for their join date, it doesn’t define intelligence. Sure, experience matters, but I’ve seen plenty of people that started programming less than a year ago know more than people that have been programming for years.
Secondly, from what I know, the new movement systems are more advanced and conform better to Roblox’s current methods of modeling with joints and all that. Obviously, it’s newer, so it’ll also be more optimized, and since BodyMovers are deprecated, the newer systems will be updated, supported, and maintained while BodyMovers will not be.
Claiming the new systems are bad because they have “a bajillion new properties” and have “more complex and unnecessary physics calculations” is absurd. If having more customization and control is such a bad thing, then I don’t know what to tell you. It’s really not that complicated, either. You just need to learn about it. If you don’t understand it, just say that. Don’t claim they’re not good because you couldn’t get them to work properly. I guarantee it’s your own fault, not the system’s.
Lastly, Roblox themselves tell you not to use BodyMovers, and I think the literal company that made the instances knows what they’re talking about. Please, stop telling others to use them. They’re deprecated for a reason.
But hey, what do I know, I only started developing on Roblox 6-7 years ago and have only been on the platform for 14 years.
1 Like
6-7 years experience and you don’t even know about all the downsides with the new VectorForces? Seems like someone’s trying to act smart without showing how much better the “optimizations” they’re talking about are. Oh and just because they’re deprecated for a reason doesn’t mean it’s a good reason. Roblox just deprecated them to add more complex physics related instances which should not be used too much in new work as they are infact way laggier than the old “deprecated” instances. oh but what would I know I only started developing on Roblox 5 years ago and have only been on the platform for 7 years
1 Like
I don’t know if this was mentioned before but they did an update that fixes laggy behaviour with these new VectorForces, there is a setting in the workspace called “MoverConstraintRootBehaviour” and if enabled fixes replication problems and makes them really smooth. I am currently using LinearVelocity for my own project and it is way better then these other BodyMovers in my opinion since you have way more control over them.
3 Likes
I mentioned this but it was added way after strongest battleground so they still wouldn’t have used this
1 Like
What leaked scripted file??? I tried finding it everywhere I couldn’t find it
1 Like
or… you could experiment with different velocity types…
(try bodyvelocity or bodyposition)
1 Like
Yes, they use bodyvelocity, these are close settings to what you are trying to get
–front
maxforce 40000, 0, 40000
p 1250
velocity ?
–they tween the speed attribute from (170-23)–
–back
maxforce 50000, 0, 50000
p 1250
velocity ?
–left and right
maxforce 50000, 0, 50000
p 1250
velocity ?
1 Like