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

opPlayerNoCheat missing commands #36

Closed
CodeF53 opened this issue Aug 24, 2021 · 4 comments
Closed

opPlayerNoCheat missing commands #36

CodeF53 opened this issue Aug 24, 2021 · 4 comments

Comments

@CodeF53
Copy link

CodeF53 commented Aug 24, 2021

There are several commands that the rule opPlayerNoCheat misses.

Here are the ones I have found so far:
/fill - should be disabled for the same reason /setblock is

/enchant - allows enchanting tools without xp/books

/experience and /xp allows giving self or others xp.

@CodeF53
Copy link
Author

CodeF53 commented Aug 24, 2021

/advancement

@CodeF53
Copy link
Author

CodeF53 commented Aug 24, 2021

/effect - give saturation to self / instantly kill others
/defaultgamemode - can really cause issues
/kill
/data - /data modify block 542 66 903 Items[0].id set value "minecraft:diamond_block"

@Fallen-Breath
Copy link
Contributor

Rule opNoCheat is not designed for disabling all possible cheaty commands, but for disabling commands that are cheaty and can be unintended triggered

e.g.

  • /gamemode: via F3+N
  • /teleport: via clicking in minimap mods

I won't add commands that don't have unintended triggering cases

@Fallen-Breath
Copy link
Contributor

Fallen-Breath commented Aug 25, 2021

Since you already have op permission, if you do want to cheat, you can just disable this rule with /carpet opPlayerNoCheat false

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

No branches or pull requests

2 participants