OP Permission Fallback (Fabric)

Requires the library mod Collective (Fabric) and the Fabric API. 

OP Permission Fallback (Fabric) exists as a bridge between mods using the standard .hasPermission() function in their code, without providing support for a Permission mod, and servers with a permission-based environment.

When adding the "minecraft.op" (can be changed in the config) permission string to a player, they will be able to do all commands an /op(erator) can do. This also works for cheat-access.

At the moment compatible with permission providers using the fabric-permissions-api. Such as LuckPerms.
Compatibily can be extended in the future, feel free to open an issue on Github with a request for your specific provider.

Why does this exist?
Let's say you have created an extensive ecosystem of permissions within your server, and do not use the /op feature of Minecraft. You now add a new mod which is not set up for permissions. With OP Permission Fallback, you can add the "minecraft.op" permission to your admins, which means they will be able to use all commands from mods which only check for operator/cheat-access.

As a mod creator you can also reference this mod to avoid having to provide support for permissions yourself.


Configurable: ( how do I configure? )
defaultOpPermissionString (default = "minecraft.op"): The permission string to make players act like /op(erators) in-game. By default 'minecraft.op'.

------------------

You may freely use this mod in any modpack, as long as the download remains hosted within the CurseForge ecosystem.

Serilum.com contains an overview and more information on all mods available.

Comments are disabled as I'm unable to keep track of all the separate pages on each mod.
For issues, ideas, suggestions or anything else there is the Github repo. Thanks!