Hi there, sorry to hear you're having troubles with the plugin.
Was there any errors in your console during plugin initialization?
Additionally, does your group have the `truestafftoggle.useduty` permission?
In the config you'd have your main group as the key and the onduty group as your value.
For example if you're main group is owner, it would look something like:
"owner": "owner_onduty"
Owner should at least have the useduty permission.
Just as a note the fact you had to rejoin after a reload was a bug causing auth levels not to be restored correctly upon plugin unload. This was fixed in 1.1.2 as well.
So hopefully you won’t have to rejoin anymore when you unload or reload the plugin.
You may have an underlying problem then, if you're being removed from the group and that group is the only one that gives those perms then. All this plugin does is add and remove you from the onduty group.
This plugin lets you set up separate on-duty groups for different staff roles.
The group on the left (e.g., "admin") holds the core permissions that staff should always have, like an admin chat tag, muting, and other basic tools.
The group on the right (e.g., "admin_onduty") provides elevated powers that should only be available when on duty, such as base upgrades without resources, vanish, or god mode.
The plugin ensures that staff always stay in their base group.
When a staff member runs /duty, it adds them to the on-duty group. Running /duty again removes that group, leaving them only in the base group.
Additionally, if you want, you open the cs file and look at the top of the file, look where I reference, “Oxide.Ext.Discord” and just remove that line. Dave the file then reload.
Codefling is the largest marketplace for plugins, maps, tools, and more, making it easy for customers to discover new content and for creators to monetize their work.
We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.