Option to prevent players that are in combat from executing commands #17
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
WildToastyMop/CombatLog#17
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
A config option that prevents players that are in combat from executing commands.
I also need this feature, because otherwise players can just use /home or /spawn to tp away.
I haven't been able to figure this one out yet (probably a mixin to intercept commands?) but I will keep looking into it
In the meantime you could add a way to allow us to negate LuckPerms permissions and we could pair it with Universal Perms to disable those commands that don't support permissions, as a stopgap measure. You will need to manually add the permissions manually to the config file (this will allow you to disable interactions with mods that support permissions aswell)
There's a simpler option and it would require you to set up your luckperms' permissions by creating a permission group with higher priority than all the other groups. You can negate all the permissions you want in this group. Then you can add this group to CombatLog's config and the mod will set combatlogged people into this group, effectively negating all permissions and commands (if you use UniversalPerms for the commands that don't support permissions)
Hope that was helpful
I figured it out using mixin this is now in 2.3