Bypass on workspace.FallenPartsDestroyHeight

Mimibienv · October 29, 2025, 5:06pm

Hello !
So, basically, in Roblox, the property FallenPartsDestroyHeight from the workspace has to be a number value between -50,000 and 50,000. This makes it so that, any unanchored part of the height Y that goes past that value gets destroyed. This limit is there to, I suppose, limit bugs due to the floating points in Lua.
However, there is a bug where this can be bypassed by executing workspace.FallenPartsDestroyHeight = 0/0. By doing that, the value becomes nan, which is not a number and therefore not interpretable by the Roblox physics engine since it can not be used in mathematical operations.

We therefore get this when exploiting that bug :

And so, this bug lets users bypass this FallenPartsDestroyHeight limit set by Roblox by breaking it, as you can see here :

choconatto · October 30, 2025, 3:47pm

For now, setting workspace.FallenPartsDestroyHeight = 0/0 is permitted.

Partcline · October 30, 2025, 4:50pm

In a way this can also be great, especially for games that wish to bypass the vertical limitations and handle height-related debris on their own.

Any hopes we might be able to see a permanent method in achieving this in the future?

choconatto · October 30, 2025, 7:07pm

We have no current plans to surface such a bypass explicitly via API.

index_self · October 30, 2025, 11:25pm

What about FallHeightEnabled? It was added back in January but hasn’t been enabled yet.

I’d like to stop using this nan hack as soon as possible since it feels like a ticking time bomb waiting to delete the whole workspace due to a regression.

Mimibienv · October 31, 2025, 11:25am

Yep, fallheightenabled was a great idea but it doesn’t work LOL