Option to prevent players that are in combat from executing commands #17

Closed
opened 2025-01-11 04:51:31 -06:00 by Codestech1 · 4 comments
Codestech1 commented 2025-01-11 04:51:31 -06:00 (Migrated from github.com)

A config option that prevents players that are in combat from executing commands.

A config option that prevents players that are in combat from executing commands.
virtualspan commented 2025-01-12 04:49:20 -06:00 (Migrated from github.com)

I also need this feature, because otherwise players can just use /home or /spawn to tp away.

I also need this feature, because otherwise players can just use /home or /spawn to tp away.
WildToastyMop commented 2025-03-12 19:36:42 -05:00 (Migrated from github.com)

I haven't been able to figure this one out yet (probably a mixin to intercept commands?) but I will keep looking into it

I haven't been able to figure this one out yet (probably a mixin to intercept commands?) but I will keep looking into it
elhertz commented 2025-03-13 05:59:42 -05:00 (Migrated from github.com)

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 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](https://modrinth.com/plugin/luckperms) permissions and we could pair it with [Universal Perms](https://modrinth.com/mod/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
WildToastyMop commented 2025-03-14 20:03:53 -05:00 (Migrated from github.com)

I figured it out using mixin this is now in 2.3

I figured it out using mixin this is now in 2.3
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
WildToastyMop/CombatLog#17
No description provided.