Remove the Region3 part limit

Why is it there to begin with? I’m always discouraged from using them exclusively because there’s a chance it’ll return inaccurate results. We can always recreate a version of Region3 in Lua, but it isn’t quite as efficient.


Its set to 100 because of performance. If you call the :FindPartsInRegion3() method in an area with 1000 parts? That could potentially have a very negative impact.

Increasing the limit can be discussed I believe, but I don’t think removing it entirely is a good idea.

An alternative solution is to split up your Region3.

Remove limit for 100, instead allow any number between 0-math.huge, but the default would always be 100.

There, we can have best of both worlds.


The default is 20 currently