Scalbox

Changed Status from Pending to Closed Changed Fixed In to 1.1.3

Plugin updated, versione 1.1.3. try now. Thanks

Hi maybe Clans reborn uses different Hooks than other Clans plugins. I don't have the Clans reborn plugin, but I'll try to replicate the problem. I'll update you in a few hours

Changed Fixed In from 1.1.90 to Next Version

Changed Status from Pending to Closed Changed Fixed In to 1.1.2

Plugin updated, Version 1.1.2

Send me a video of the problem

they don't work because they are not base vehicles. I will add them to the plugin as soon as possible

Changed Status from Pending to Closed Changed Fixed In to 1.1.1

I have released an update that fixes the issue: version 1.1.1

Changed Status from Pending to Not a Bug

Perfect, no problem

Found the problem, you have not enabled any auto close. You need to enable at least 1 auto close, enable what you want the plugin to close automatically "Auto Closing Configuration": { "Player Can Pickup Door Closer. (Default: TRUE)": true, "Enable automatic closing of Door. (Default: FALSE)": false, "Enable automatic closing of Double Door. (Default: FALSE)": false, "Enable automatic closing of Garage. (Default: FALSE)": false, "Enable automatic closing of Ladder Hatch. (Default: FALSE)": false, "Enable automatic closing of External Gate. (Default: FALSE)": false, "Enable automatic closing of Fence Gate. (Default: FALSE)": false, "Enable automatic closing of Legacy Wood Shelter Door. (Default: FALSE)": false, "Minimum Closing Delay Time. (Default: 10 seconds)": 10, "Maximum Closing Delay Time. (Default: 60 seconds)": 60, "Default Closing Delay Time. (Default: 30 seconds)": 30 },

can you send me your config file?

For some reason, it does not take your permissions, as you can see it clearly says that you do not have permission and for this reason the button does not appear. Unfortunately this does not concern the plugin directly but some problem with the permissions. Try to follow these steps, we remove the roles from all the groups and assign the roles to use it, but only with the default group. So in the meantime we will see if this solves it, and then we will see how to do it for the other groups. Run these commands: oxide.revoke group vip_1 ultimatelocker.use oxide.revoke group vip_1 ultimatelocker.admin oxide.revoke group vip_1 ultimatelocker.bypass.force oxide.revoke group vip_1 ultimatelocker.autolock.enabled oxide.revoke group vip_1 ultimatelocker.autolock.nolockrequired oxide.revoke group vip_1 ultimatelocker.autoclosing.enabled oxide.revoke group vip_1 ultimatelocker.autoclosing.nodoorcloserrequired oxide.revoke group default ultimatelocker.use oxide.revoke group default ultimatelocker.admin oxide.revoke group default ultimatelocker.bypass.force oxide.revoke group default ultimatelocker.autolock.enabled oxide.revoke group default ultimatelocker.autolock.nolockrequired oxide.revoke group default ultimatelocker.autoclosing.enabled oxide.revoke group default ultimatelocker.autoclosing.nodoorcloserrequired oxide.revoke group vip_2 ultimatelocker.use oxide.revoke group vip_2 ultimatelocker.admin oxide.revoke group vip_2 ultimatelocker.bypass.force oxide.revoke group vip_2 ultimatelocker.autolock.enabled oxide.revoke group vip_2 ultimatelocker.autolock.nolockrequired oxide.revoke group vip_2 ultimatelocker.autoclosing.enabled oxide.revoke group vip_2 ultimatelocker.autoclosing.nodoorcloserrequired oxide.revoke group vip_3 ultimatelocker.use oxide.revoke group vip_3 ultimatelocker.admin oxide.revoke group vip_3 ultimatelocker.bypass.force oxide.revoke group vip_3 ultimatelocker.autolock.enabled oxide.revoke group vip_3 ultimatelocker.autolock.nolockrequired oxide.revoke group vip_3 ultimatelocker.autoclosing.enabled oxide.revoke group vip_3 ultimatelocker.autoclosing.nodoorcloserrequired oxide.grant group default ultimatelocker.use oxide.grant group default ultimatelocker.autolock.enabled oxide.grant group default ultimatelocker.autoclosing.enabled