enable /locate and /locatebiome

Good point.

I need someone more expert to explain if the command has the potential to lag the server if abused.

This is all I could find on it.

This was blocked because on flat worlds like the flatlands, it would just crash the server due to Mojang's incompetence in regards to getting something from a flat world where that shit doesn't exist.

↩  videogamesm12 What about making TFM block it only if used in flat worlds?

Neutral I blocked it for a reason a long time ago due to the server instantly crashing but I think Steven said that after some testing it doesn’t do any damage

If this actually crashes the server, I’ll just try to find something manually instead.
Otherwise, vouch.

I remember using /locatebiome once and had no problems, so I believe Steven is right that they're not dangerous in 1.16.5.

I vouch to whitelist the commands in overworld, nether and end

This thread highlights for me that we shouldn't take for granted that everything that was blocked in the past still needs to be blocked now. By now it has also been a while since my test: maybe it's still fine, maybe it's broken again. We should however actually be checking that instead of defaulting to keeping everything blocked.

↩  SuperRyn Suggestion are reviewed sorted by oldest reply, so you've probably delayed this one 😛

↩  SuperRyn

To quote Ryan himself;

Quote

Bumping suggestions results in them going to the bottom of the list to be reviewed. They’re reviewed based on their last post.

So you've just made this suggestion the last one to be looked at.

Vouch I do projects where I need structures that are generated and I have to ask staff that don’t always really do it so then I ask people if they know where one is it is really annoying :

I've decided that im vouching as long as it checks if the player that runs the command is in flatlands, plotworld, mbworld, adminworld, etc.
And then if they're in one of those worlds it just cancels it.

Or anything similar that keeps it from going crash command for ops goes brrrrrrrrrrrrrrr

I need to check but I think this was fixed in 1.17 and the intent was to re enable it then but we wont re enable it before that and I won't have the developers write duplicate commands like this just to fix a mojang fuck up.

↩ @'Ryan' when is the update to 1.17

↩  matscalle When it's ready.

↩ @'Ryan' that is in how long?