Summary:

I know there was an issue with spreadplayers causing the server to drop to 3 ticks, but this issue is regarding the behavior where the server struggles when spreadplayers is used in an area with a little/no valid blocks to place players on (such as in an ocean). In my context, I am using this command to spread some entities apart semi-randomly to check for specific types of blocks, but when players cross into oceans, the server struggles.

To reproduce:

Use the spreadplayers command with a spread distance that encompasses only invalid blocks (water, lava, and I assume void)

Extra info:

I am assuming this is happening because it is attempting to find a valid block, then when it fails, it tries again. Though I don't know for sure if this is a bug or just a known side affect of intentional behavior.

Now at this point I have to admit that this is walking the line of bug report, and suggestion, but I assume a fix to this would be to add an argument which limits the check to one pass (or even a user defined amount). So in my example, it would only check once in open waters, then stop.

Sorry if this has already been reported, I could not find anything specifically related to this.