Region3 Size is becoming negative?

[R8YMER]

Apparently @Sharksie pointed this out in 2015. I wonder what’s the reason why it doesn’t automatically do this checks-and-balances.

Region3s can have negative size very easily

> print(Region3.new(Vector3.new(1,1,1),Vector3.new(-3,-3,-3)).Size) -4, -4, -4 Just by supplying the lower vector second you can give a region3 negative size and then it won’t be able to detect anything with FindPartsInRegion3. It really shouldn’t even be possible for size to be negative.