.Nathaniel.
-
Posts
100 -
Joined
-
Last visited
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by .Nathaniel.
-
Hi there, is this still happening?
-
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. -
No problem!
-
When you reloaded the plugin did you rejoin the server?
-
Can you let me know if this is still happening on the new version.
-
This has been fixed in 1.1.2
-
Changed Status from Work in Progress to Fixed
-
Sorry for the delay, this has been fixed
-
Changed Status from Work in Progress to Fixed
-
Apologies, having issues getting Rust to stay open on my computer. I will have an update asap!
-
Just got home, going to look into it right now.
-
Changed Status from Pending to Work in Progress Changed Fixed In to Next Version
-
Just got home, will look into it right now!
-
Can you please send your config?
-
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.
-
Please double-check your perm setup and make sure you're being removed from the on-duty role.
-
Changed Status from Pending to Work in Progress Changed Fixed In to Next Version
-
No problem! Let me know if you need anymore help! I try to check codefling as often as possible. But for faster support join our Discord!
-
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.
-
Changed Status from Pending to Fixed Changed Fixed In to 1.1.1
-
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.
-
My deepest apologies for this I will fix it as soon as I get home in about an hour and a half.
-
Version 1.1.2
17 downloads
True Staff Toggle Highly customizable staff toggle plugin. With this plugin, you can allow players to switch between AuthLevel 0 and the AuthLevel they joined with. Additionally, each specific staff group can have a separate on-duty group attached to it. No more one on-duty group for everyone. Chat Commands /duty - Toggles OnDuty Status (Calls truestafftoggle.duty console command.) /auth - Toggles AuthLevel Status (Calls truestafftoggle.auth console command.) Console Commands truestafftoggle.duty truestafftoggle.auth Permissions truestafftoggle.useduty - Permission to use the /duty chat & console command. truestafftoggle.useauth - Permission to use the /auth chat & console command. Default Configuration { "Debug Mode": false, "Steam User Icon ID": 0, "Staff Groups - Should be 'maingroupname': 'maingroupname_onduty'": { "groupname1": "groupname1_onduty", "groupname2": "groupname2_onduty" }, "Auto Auth On Duty - Bumps the staff up to their authlevel granted in the server config.": false, "Log Duty Toggle": false, "Log Auth Toggle": false } Localization { "AuthToggleOn": "You have been put into AuthLevel {0}", "AuthToggleOff": "You have been taken out of AuthLevel", "OnDuty": "You are now on duty.", "OffDuty": "You are now off duty.", "NoPermission": "You do not have permission to run this command!", "NoAuthLevel": "You do not have any auth levels assigned to you." } WIP I plan to add Discord Webhook support for logging status changes. Currently in the testing phase is: Simple/Advanced Status Compatibility.$4.99 -
Raidable Bases randomly owned by players.
.Nathaniel. replied to .Nathaniel.'s Support Request in Support
Hey there, sorry about bothering you. I think I may have found the issue. We should be good here! -
Hi there, I am noticing that when players die from sentries or alike at a Raidable Base, the Death Note says: "<Killer Name>'s Sentry has killed <Target Name>" Giving the idea that these bases are spawned in owned by a random player. Is there anything I can do to fix this?
