Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Block /clone in command blocks only. #362

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

GEOEGII555
Copy link
Contributor

Closes kaboomserver/server#140

The reason behind putting it here and not in the main server repo is so that I can block the clone command only in command blocks - let normal people use it anyways.

@nellieldev
Copy link

-1: Breaks many things and there's no obvious reason for me for disabling clone in cmd blocks.

@Yaodeowo
Copy link

-1: Breaks many things and there's no obvious reason for me for disabling clone in cmd blocks.

because some player abuse cloop, "server blocker" "smp mode" thing.

@GEOEGII555
Copy link
Contributor Author

-1: Breaks many things and there's no obvious reason for me for disabling clone in cmd blocks.

because some player abuse cloop, "server blocker" "smp mode" thing.

Didn't you make the smp mode?

@GEOEGII555
Copy link
Contributor Author

GEOEGII555 commented Aug 21, 2024

-1: Breaks many things and there's no obvious reason for me for disabling clone in cmd blocks.

Valid point, but people are just tired of server blockers. I made my own recently as a proof of concept

@GEOEGII555
Copy link
Contributor Author

@kaboombot so? What do you think?

@OptimisticDeving
Copy link
Contributor

This solution won't prevent server blockers. You may stop them for a few days, but eventually the people designing the server blockers will implement one of the other command loop methods. Also, the earliest server blockers were bots with command cores.

Blocking commands that can be abused in a command loop for command blocks would also be similarly ineffective. They will find other commands to abuse, and perhaps might even discover a new way to bypass the command blocker. The commands you would abuse in a server blocker are also very useful as one-off executions, and in the logic of bots.

@Yaodeowo
Copy link

This solution won't prevent server blockers. You may stop them for a few days, but eventually the people designing the server blockers will implement one of the other command loop methods. Also, the earliest server blockers were bots with command cores.

Blocking commands that can be abused in a command loop for command blocks would also be similarly ineffective. They will find other commands to abuse, and perhaps might even discover a new way to bypass the command blocker. The commands you would abuse in a server blocker are also very useful as one-off executions, and in the logic of bots.

TRUE

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

Block clone command in command block
4 participants