-
Posts
53 -
Joined
-
Last visited
-
Days Won
2
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by JulioJuajez
-
Hi, I think there’s a misunderstanding. My plugin never automatically places a code lock on items. It only makes them “lockable,” meaning that players can manually add a code lock or a key lock if they want. If you previously saw a code lock appear automatically, that must have come from another plugin or a different configuration, but not from this one.
-
Changed Status from Work in Progress to Not a Bug
-
Changed Status from Pending to Work in Progress Changed Fixed In to 2.1.0 Can you explain what you mean regarding the update that is not working? Please provide me with the error message, tell me what is not functioning because it works perfectly on my end without any error message, and I won't be able to help you.
-
No critical bug — the request was about lock placement. In v2.1.0 we fixed the position and added some QoL: /lockoven_refresh to re-enable locks after wipes /lockoven_add (with a hammer) to add custom ovens/refineries that contain “furnace” or “refinery” Per-oven configurable lock positions If anything looks off on a specific prefab, ping me with the prefab path and I’ll add a tuned default.
-
Thanks for the nudge — plugin is updated to v2.1.0. Fixed the lock position so the code lock now appears on top of the oven/refinery (not stuck on the side). You can fine-tune placement per oven in Lockposition/Lockrotation in the config, and list the supported ovens with: /lockoven_list If you added ovens before the update, run: /lockoven_refresh to reapply the placements.
-
We pushed v2.1.0 today. After a wipe, please run: /lockoven_refresh This makes all existing ovens/refineries lockable again. Also check your permissions: by default players don’t need any, but if you enabled usage perms in the config, grant it to your player group: oxide.grant group default lockoven.use (Admins can use /lockoven_* commands with lockoven.admin.) If you still have issues, delete the Lockoven.json once to let it regenerate and reload the plugin.
-
Changed Status from Pending to Fixed
-
I'll take care of it next week.
-
-
Hey Airpex, Really glad to hear that everything is working now! It looks like the small optimization made the difference. If you're not seeing any error messages in the server panel console and there are no crashes, it sounds like we're on the right track. If you run into any more issues or if you have any suggestions on how to improve the plugin, please don't hesitate to let me know. Your feedback is very important for maintaining the stability and performance of the plugin. Thanks for your patience and for giving it another try. Best regards!
- 15 comments
-
- #lock
- #composter
-
(and 3 more)
Tagged with:
-
- 15 comments
-
- #lock
- #composter
-
(and 3 more)
Tagged with:
-
- 15 comments
-
- #lock
- #composter
-
(and 3 more)
Tagged with:
-
Hello Jeremy, It seems that you are experiencing an issue with the lock deployment feature of the mod. I assure you that the mod is up to date and should be functioning correctly. If you have enabled the ActivatePermUse option in the configuration file, you must ensure that users are granted the lockoven.use permission to be able to deploy a lock. Here’s how you can assign this permission: Use an admin console or RCON tool to assign the permission. Type the following command, replacing <username> with the player's username: oxide.grant user <username> lockoven.use If you'd like to assign the lockoven.use permission to an entire group, you can do so with this command: oxide.grant group <groupname> lockoven.use Replace <groupname> with the name of the player group that should receive the permission. This will allow all players in that group to deploy locks as per the mod's functionality. If ActivatePermUse is set to false, then no additional permissions are necessary, and players should be able to deploy locks without any issue. If you continue to encounter difficulties, please don’t hesitate to let me know so I can provide further assistance.
-
- 3 comments
-
- 15 comments
-
- #lock
- #composter
-
(and 3 more)
Tagged with:
-
- 15 comments
-
- 1
-
-
- #lock
- #composter
-
(and 3 more)
Tagged with:
-
Version 1.1.0
856 downloads
Lock Your Barrels v1.1.0 Make all your storage barrels lockable in Rust! Supports vanilla barrels and all DLC content (Abyss, Jungle). Key Features Auto-lock barrels - All barrels become lockable on spawn DLC Support - Works with Abyss & Jungle DLC barrels Dynamic Addition - Add new barrel types with a hammer Simple Commands - Easy admin management Multilingual - English & French support Quick Start Install the plugin Grant admin permission: oxide.grant user <name/id> lockbarrels.admin Use /lockbarrels_refresh to make existing barrels lockable NEW: Use /lockbarrels_add + hammer to add custom barrels Commands /lockbarrels_refresh - Make all barrels lockable /lockbarrels_add - Toggle barrel addition mode /lockbarrels_list - List supported barrels /lockbarrels_clean - Remove duplicate entries /lockbarrels_reset - Reset to defaults Adding Custom Barrels Type /lockbarrels_add to enable addition mode Equip a hammer Hit any barrel to add it Type /lockbarrels_add again to disable mode Supported Barrels (Default) Storage Barrel B & C (Base DLC) Abyss Horizontal & Vertical Barrels Wicker Barrel (Jungle DLC) Bamboo Barrel (Jungle DLC) Configuration Located in oxide/config/LockBarrels.json: { "Command": "lockbarrels_refresh", "AddCommand": "lockbarrels_add", "ListCommand": "lockbarrels_list", "CleanCommand": "lockbarrels_clean", "ResetConfigCommand": "lockbarrels_reset", "PermAdmin": "lockbarrels.admin", "SupportedBarrels": ["..."] } Permissions lockbarrels.admin - Required for all commands Pro Tips Barrels placed before plugin installation need /lockbarrels_refresh New barrels are automatically lockable Remove unwanted barrels from config - they won't be re-added Use /lockbarrels_clean if you have duplicates Language Support Automatically detects player language from Steam (French/English)Free- 3 comments
- 2 reviews
-
- 2
-
-
- 15 comments
-
- 1
-
-
- #lock
- #composter
-
(and 3 more)
Tagged with:
-
- 15 comments
-
- #lock
- #composter
-
(and 3 more)
Tagged with:
-
Changed Status from Work in Progress to Closed Changed Fixed In to 1.0.2
-
Version 1.0.1
19 downloads
This plugin allows you to authorize the installation of codelock and lock on doors that do not allow it Autorisation : lockalldoors.admin Command: /alock => activates or deactivates the right to modify the locking state of a door You can change this command via the language file. You can customize messages with your server name by modifying SERVERNAME in the configuration file The plugin is translated into English and French.$9.90 -
- 13 comments
-
- #christmas sale
- #tfar
-
(and 3 more)
Tagged with: