Block clone command in command block
In the current era of kaboom, people are often abusing the "cloop" (short for command loop) to dominate server by running ekill, deop, effect give blindness... over and over.
These cmd loops are abusing the clone command, to clone command blocks with desired command, and run the commands in an infinite loop, effectively bypassing the repeating command block prevention
The simplest solution would be to just prevent that command from running whatsoever, and thats what im proposing here. It definitely wont stop community made bots spamming commands, but will stop command blocks, that do not require any interaction from outside (aka. sending tons of packets over and over)
I think better solution will be disabling /sudo in command blocks
disable /clone in command block better
Cloop can be easily destroyed with /gamerule commandModificationBlockLimit 0, but spamming /sudo will prevent you from running any command
ohh, disable /deop and /sudo in command block
in some cases it's very useful to be able to run /sudo in command blocks, so i do not like disabeling it enitrely.
the only reason it's a problem right now is that commands executed by /sudo count towards the command cooldown of that player, which can be abused to disable chatting and running commands.
if /sudo commands didn't count towards the ratelimit cloops wouldn't be a problem, sinc you can just break them with the gamerule commandModificationBlockLimit, as said above
I agree with you
ayunboom (rip) moment
But in all seriousness, it seems like a really good idea, there are other methods of creating cloops that don't involve /clone but they are way more obscure and most probably won't be abused
going out of topic, i've just noticed i wrote a wrong word, and the sentence had no sense, fixed the typo
This is what's happening to kaboom once in a while.
ayunboom (rip) moment
But in all seriousness, it seems like a really good idea, there are other methods of creating cloops that don't involve /clone but they are way more obscure and most probably won't be abused
You can make cloops with spawners, but they're slower.
if /sudo commands didn't count towards the ratelimit cloops wouldn't be a problem, sinc you can just break them with the gamerule
commandModificationBlockLimit, as said above
While this would make it easier, it's still problematic if you're being spam deopped
ayunboom (rip) moment But in all seriousness, it seems like a really good idea, there are other methods of creating cloops that don't involve /clone but they are way more obscure and most probably won't be abused
You can make cloops with spawners, but they're slower.
there are better ways