i said for you to say that i’m talking about you
That’s why we are asking for an official way to disable it, setting FallenPartsDestroyHeight to nan with 0/0 works fine, been using it for years
as someone that has custom logic and specialized behavior for parts in the game i’d want this to be officially supported so i don’t have to do hacky work arounds
we should have the option to chose how our game behaves, if someone has a performance issue because they disabled something then it is a skill issue and it’s their problem, competent devs shouldn’t suffer because of those who aren’t
6 Likes
I’m not patronising you, I’m trying to reason that having too many parts can cause lag and even crashing if it’s too much, so FallenPartsDestroyHeight is recommended.
I’m trying to reason that having too many parts can cause lag and even crashing if it’s too much, so FallenPartsDestroyHeight is recommended. Many devices on Roblox are low end and they are probably not powerful enough to handle too many parts. The device could slow down or possibly crash.
If Studio isn’t letting anyone else use math to modify the DestroyHeight, it’s because only plugins are allowed to set it to a value beyond its limits.
Here is a small plugin I made that sets the value to NaN.
DestroyHeightPlugin.lua (467 Bytes)