UltimateLocker - Lock Everything, Auto Lock & Auto Closing 1.5.5

On 9/14/2025 at 9:54 PM, Madstayen said:

Maybe you misunderstood me, my apologies. Let me rephrase my question. Is it possible to add a config option to choose between using the new Flight Control Codelock (If you own the DLC) or the standard codelock?

Plugin updated

1) Added: Option to automatically use the Flight Control Codelock skin.

On 9/15/2025 at 8:21 PM, Scalbox said:

Plugin updated

1) Added: Option to automatically use the Flight Control Codelock skin.

This will only be an option if the player owns the DLC, yes?

2 hours ago, Rust Admin said:

This will only be an option if the player owns the DLC, yes?

Yes, but you can bypass the check via configuration or permissions.
But this can only be done on test/creative servers; otherwise, it violates FacePunch's TOS, and if you're caught, your server can be banned from Rust.

⚠ Only allowed on creative/test servers, otherwise you violate Facepunch's TOS! ⚠

6 hours ago, Scalbox said:

Yes, but you can bypass the check via configuration or permissions.
But this can only be done on test/creative servers; otherwise, it violates FacePunch's TOS, and if you're caught, your server can be banned from Rust.

⚠ Only allowed on creative/test servers, otherwise you violate Facepunch's TOS! ⚠

I understand - that is why I dont want players to be able to use it, unless they own the DLC 
Great plugin and thank you!

On 9/14/2025 at 11:08 PM, Grumpy Old Man said:

We use /locker to open the PortableLocker. 
in UltimateLocker you added two months ago an option  Line 15 of the config "     "Add Lock manually - Chat Command": "locker", "

So i check it for locker222 so player can still use /locker. 

now every work that have locker it show "code lock deployed and lock Code: 1234 in chat .

i try to change /locker for /plocker, did not work,  /portlocker did not work,  always place in chat  "code lock deployed and lock Code: 1234 in chat .

i think it create confusion. .

Hi, you haven't opened a ticket yet. Have you solved the problem?

16 minutes ago, Scalbox said:

Hi, you haven't opened a ticket yet. Have you solved the problem?

yes sorry, all good, thanks