New tool cupboard syncing old locksFixed
I hand an instance today where a player found an old cave base without TC, put his own TC down and found he had access to the previous owners locks. Luckily he's one of the good guys and repoted it. Check the logs when the TC was placed and didn't see anything.
The only other TC Auth plugins we use are Sam and ATs, incase they might conflict. 
I also have seen an exploit using Code Sync.  Whilst the description says "Get raided, and the raiders will be unable to abuse the mechanic to open all your doors, as placing a new tool cupboard down won't give access to the doors in the base." This is not the case. I have seen and tested the following. Raiders placed a new TC and enter a new code. Say the old code was '1234' they place a new code '0000' and whilst this does not give auto access ie they can't just press 'E' to open. They can go up to the door lock enter the new code '0000' and the lock code is reset to '0000' and they can open the door.
 
Still having this issue, and people use this to raid the rest of the base without explosives. 
Any ideas on a fix?
Any movement on a possible fix for this?
Ouch yes wish I would of read this sooner. This is a major issue, plugin is broken based on that exploit.
I'll try to take a look at this when able. Open to patches as well.

Love the plugin idea, but it is not working.

I was thinking about this approach:
1) TC has a codelock with a code
2) All codelocks with the same code as TC, can be opened without enetering the code (if auth to TC)
3) Codelocks with different code then TC cannot be opened automatically (must know code)
4) On TC code change, all codelocks have to change their code manually

Fixed: Once someone raids a base, the TC will not change the door lock codes.
Downside: If you want to change the TC code for some reason, you have to do it on all codelocks in building. The TC will not change any codelock codes in building.

Conclusion: Without the plugin, the downside i mentioned is a normal thing in Rust, so it's not a big deal. As long as you are using the same code on all codelocks, the plugin will still work flawlessly.

The new feedback message should be something like this: "After auth on TC codelock, you do not have to enter code on each codelock in building, but their codes must be the same" (I guess someone could write it better)

I tried this (commenting these two lines) and it works:

CodeLock tcLock = GetCupboardLock(building);
            if (tcLock != null)
            {
                if (tcLock.code == code && codeLock.code != code)
                {
                    //COMMENTING THE LINE UNDERNEATH
                    //codeLock.code = code;
                }
                else if (tcLock.guestCode == code && codeLock.code != code)
                {
                    //COMMENTING THE LINE UNDERNEATH
                    //codeLock.guestCode = code;
                }
            }


Please give feedback if you find any problems with this approach. I am using this on a server and I need to know it is bulletproof. Thanks

Merged post

The approach mentioned in my last post (above this one) is working good. Anyone with the same problem, go to CodeSync.cs and comment out those two lines of code with two front-slashes //
@Wulf any update on this issue? I really wanna use CodeSync but this exploit is a deal breaker :(
mSLy3XICRDYD7SY.jpg tobipolar
@Wulf any update on this issue? I really wanna use CodeSync but this exploit is a deal breaker :(
I'll look into applying the above today.

probably not the right thread to ask but did this plugin just switch authors/developers?

C3TeYLuJsbulAe4.jpg tobipolar

probably not the right thread to ask but did this plugin just switch authors/developers?

Yes, I don't have a lot of time for plugins at the moment, so I passed it along to someone else that said they are willing.

Pushed what I had for now though.

NX8tVvXUGvAdaR4.jpg Wulf

Yes, I don't have a lot of time for plugins at the moment, so I passed it along to someone else that said they are willing.

Pushed what I had for now though.

Fair enough 🙂👍🏻

Locked automatically