Jump to content

Scalbox

Creator
  • Posts

    794
  • Joined

  • Last visited

Everything posted by Scalbox

  1. Scalbox

    Support for crafted chassis

    Plugin updated, Version 1.1.2
  2. Scalbox

    Support for crafted chassis

    Send me a video of the problem
  3. Scalbox

    Support for crafted chassis

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

    Small Bug maybe?

    Changed Status from Pending to Closed Changed Fixed In to 1.1.1
  5. Scalbox

    Small Bug maybe?

    I have released an update that fixes the issue: version 1.1.1
  6. Changed Status from Pending to Not a Bug
  7. Perfect, no problem
  8. 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 },
  9. can you send me your config file?
  10. 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
  11. Can you send me a full screen image with the plugin open? I think it's a resolution problem. You can, try giving this command, and let me know if the autocloser screen opens: ultimatelocker.autoclosing.cmd
  12. Type these 2 commands and send me the output: 1) oxide.show perm ultimatelocker.autoclosing.enabled 2) oxide.show user <YOU MUST PUT YOUR STEAMID HERE>
  13. hello you need to enable the ultimatelocker.autoclosing.enabled permission in the group you want, and make sure that the players are in that group. After that you will see the button at the bottom, when you type /autolock
  14. Hi The setting you have set, only applies to people who have never used the plugin, so for people who have already used it, they will have to change the configuration manually via the /autolock command. I am not clear what the problem is, you must enable the property to true for "other lockable entities" and players who have used the plugin before this change, will have to change the setting manually. These are settings that the plugin uses, for the first use by a player. I am not clear what the problem is
  15. Scalbox

    Small Bug maybe?

    yes, because for the computer the leading 0s are removed, all leading 0s are not counted as numbers
  16. Scalbox

    Small Bug maybe?

    I don't think it's a big deal that you can't use 0000 as your passcode, but if it's that important to you, I can enable it.
  17. Scalbox

    Small Bug maybe?

    Hello the number must be composed of 4 digits and cannot be 0000, as it is not a valid code
  18. Scalbox

    Broken.

    Changed Status from Pending to No Response
  19. Changed Status from Pending to Not a Bug
1.7m

Downloads

Total number of downloads.

7.9k

Customers

Total customers served.

119.5k

Files Sold

Total number of files sold.

2.4m

Payments Processed

Total payments processed.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.