WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
Skip to content

Conversation

@Rothes
Copy link
Contributor

@Rothes Rothes commented Dec 10, 2025

This makes it possible:

    checks:
      - "Elytra"
      - '!ElytraA'

@ManInMyVan
Copy link
Contributor

we could also just remove the enabled thing since we have per-check exempt permissions, or we could put it in config.yml as <check>.enabled

@Rothes
Copy link
Contributor Author

Rothes commented Dec 11, 2025

we could also just remove the enabled thing since we have per-check exempt permissions, or we could put it in config.yml as <check>.enabled

I feel that placing this setting in config.yml is redundant—most checks don't offer additional options, and putting it in config.yml would require two lines of text to disable it.

In punishments.yml, this only requires one line. Besides, it has always been dedicated to configure check on/off settings.

I believe using Permission would draw a small amount of additional overhead—it at least requires access to the cache. And that's designed for a specific player, not globally.

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

Successfully merging this pull request may close these issues.

2 participants