OldRusty

also getting this error Failed to call hook 'OnTeamLeave' on plugin 'TCAuth v1.5.6' (InvalidOperationException: Collection was modified; enumeration operation may not execute.) at System.Collections.Generic.HashSet`1+Enumerator[T].MoveNext () [0x00013] in <8b0c76c7efa244bc95eeee75bf1314cd>:0 at Oxide.Plugins.TCAuth.OnTeamLeave (RelationshipManager+PlayerTeam team, BasePlayer player) [0x001e1] in <690fc366f33043678171852333d8561d>:0 at Oxide.Plugins.TCAuth.DirectCallHook (System.String name, System.Object& ret,

Yes in the list of players in the image, I am the only one with bypass permission, so its 4 players authorised on it, when it is set to only allow 3.

Hi there I since the recent update I have been experiencing an Issue where the max number of players permitted to authorise on a TC is being ignored as you can see from the screen shot below this TC has 5 players authorised on it, despite my limit being set to 3. could you have a look into this for me please.

thank you very much.

Hi there, so I have disabled the plugin, and all players that were prevented from joining with the above error can now all get back on, It appears when the plugin was loaded if a player authorised on a TC that already has 1-2 player authorised on it (a raider for example) , it automatically authorised the the raiders team, pushing it over the 3 player limit and then kicked the entire team with the "Entities out of Order" I don't know why the plugin has started doing this recently but I'm having to keep it disabled for now I've got about 20 players that have been kicked in the last few days, if there is anything else I can do to help trouble shoot. Regards Old Rusty

will give it a try, Im starting to suspect its actually the Unity Engine update facepunch did then rolled back. will check it out again after wipe this week.

Many of my players are getting kicked out with the error "Entities out of order: expected 20, received 19'" and then unable to re-join the server.

with regard the icons, I am only getting this issue when using a gradient colour, they work perfectly ok for single colours, just cant add a gradient.

Also been seeing this error a few times, do you know what is causing it? Exception while calling NextTick callback (NullReferenceException: Object reference not set to an instance of an object) at Oxide.Plugins.TCAuth+<>c__DisplayClass26_0.<OnCupboardAuthorize>b__0 () [0x00198] in <d7b017df3d034400aa78124611a8afef>:0 at Oxide.Core.OxideMod.OnFrame (System.Single delta) [0x00051] in <d646191a355d43a6b3ab36b7ee14c740>:0

yes most definitely, I've only just purchased the plugin so only have downloaded that version,

I keep getting issues like this when trying to add an icon/emoji into the group name:

Can someone please tell me what the format for the gradient command is, the plugin says /gradien <color> <color> [color...] no matter what I have tried I just get <red> invalid color or if i try [blue] again its an invalid colour can someone give me the actual format for this.

Yes that would be fantastic and thought that was already a part of the plugin, so it would prevent teams larger than that provided by the tc limit from being authed,. My server is a solo/duo/trio and I have limited group size to three to prevent teaming, I would also include the caveat that it be impossible to auth on the TC if it exceeds the limit auth capacity or the person trying to auth are non team members of the owner UNLESS they wipe the TC fully. or there be some mechanic that will show players who are not members of the team who own the cupboard unless its wiped for example show the non team members name in purple no matter if they are online or not. Regards Old Rusty.

I just found another tc with 8 authorised on it.

When raiding a base owned by two team members, using a standard type raid (I don't have any plugins for this my server is Vanilla+). The situation becomes particularly intricate if the raider does not clear the authorization list from the Tool Cupboard (TC). Instead, if the raider only authorizes himself on the TC, the system automatically adds the entire raider team to the TC authorization list. As a result, when I inspect the TC, it displays multiple authorized players, often reflecting the raiding team members as well. This leads to considerable confusion and time spent trying to discern team affiliations, base ownership, and the identities of the raiders. I was under the impression that regarding the authorization limits on a TC. I believed that when two players are authorized on a TC, only one additional player can be authorized. However, the current mechanics allow the addition of the entire raiding team upon a single authorization action by the raider. This can result in multiple unintended authorizations, complicating the identification process further. In the scenario mentioned above, the picture provided illustrates how two more players from the raider's team were automatically added to the TC authorization list, compounding the complexity of the situation. Regards Old Rusty.

I think this is happening because its not clearing the players after a raid has happened, its making it impossible for me to see who is and isn't authed on this TC. Can you let me know if there is a way to fix this? My discord is just being spammed with reports.

The 3 players Uncle Propa, Pew and SoilaCerda11 are in a team the other two Gipsyrat and Sappige Sandra are in another team.

Further to this I have found a TC with 5 players authed on it despite it clearly being set to only 3 players.

No it seems to have started working now.

I did what you said, using /tssettings I set Automatically remove base parts to On, and reloaded the plugin, players could remove base parts, I then using the /tssettings changed it back to automatically remove base parts to off, reloaded the plugin again and players can still remove base parts no matter how old they are.

will test it out and see what happens. will get back to you.

Players who are authorised on TC can remove parts of a base hours after being placed instead of the 10 mins.I have attached my Config. TCAuth.json

Im getting notifications in Discord saying a player that owns a TC trying to authorise on the TC is this right?