A BodyPosition with an infinite MaxForce and a Position of Nan will not only delete itself, but also the delete the parent Object

Bug Reports Engine Bugs
,
1

If you have a BodyPosition with an Inf value somewhere in the MaxForce property and set its position to Nan (or the parent baseparts position to Nan), it will delete the parent object immediately.

This behaviour is very unusual as no other physics constraints do anything like this as far as I’m aware.

Here’s a video showcasing the issue:

The main reason I mention this is because if you accidentally set the position to nan, instead of being able to recover, your object is just gone, which complicates things way more and is not documented behaviour.

2 Likes
2

Does anything change if you set Workspace.FallenPartsDestroyHeight to nan?

1 Like
3

It does not, I’ve tried with nan and with the default values

1 Like
4

Hello,

Thank you for bringing this up to you.
Unfortunately, we don’t plan on working on the old Body Movers because they’re deprecated - we recommend migrating to the newer Mechanical and Mover Constraints.
The best one for BodyPosition should be AlignPosition: AlignPosition | Documentation - Roblox Creator Hub

Best,
M0bsterLobster