Workbench Equip Only

Workbench Equip Only 1.0.1

Sign in to download
Requires players to be near workbenches to equip weapon mods
Documentation License Changelog (1) Version History Discussion
This plugin restricts equipping weapon mods to players who are near workbenches. You can specify the required workbench level for each attachment in the config.






Permissions

  • workbenchequiponly.ignore - Allows the player to bypass the workbench requirement for equipping weapon mods.

Configuration

JSON: 
{
  "Version": "1.0.0",
  "Required Workbench Level For Attachments": {
    "weapon.mod.flashlight": 1,
    "weapon.mod.simplesight": 1,
    "weapon.mod.muzzlebrake": 2,
    "weapon.mod.muzzleboost": 2,
    "weapon.mod.holosight": 2,
    "weapon.mod.lasersight": 2,
    "weapon.mod.extendedmags": 2,
    "weapon.mod.silencer": 3,
    "weapon.mod.small.scope": 3,
    "weapon.mod.8x.scope": 3
  }
}

Workbench Levels

  • 1 - Requires a level 1 workbench.
  • 2 - Requires a level 2 workbench.
  • 3 - Requires a level 3 workbench.
Attachments not listed in the config don't need a workbench to be equipped.

Localization

JSON: 
{
  "WrongWorkbenchLevel": "You need to be near a level {0} workbench to equip this attachment."
}
Author
VisEntities
Downloads
16
First release
Last update

Ratings

0.00 star(s) 0 reviews
Donate Contribute on GitHub

Also by VisEntities

  • You Shall Not Spawn
    You Shall Not Spawn
    Prevents certain entities from spawning
  • No Gibs
    No Gibs
    Prevents debris from spawning when entities are destroyed in various ways
  • Armory
    Armory
    Gives players instant access to a box with unlimited supplies

Latest updates

  1. 1.0.1

    Fixed an issue where players would only receive the WrongWorkbenchLevel message once and not...
Read more…
Back
Top
This plugin uses Oxide's permission system. Grant or revoke permissions using oxide.grant and oxide.revoke. You can assign them to individual players or groups using their Steam id or group name.
Chat commands start with a /, while console commands can be entered directly in the F1 console or server console. Use find <keyword> in console to search for available commands related to the plugin.
Settings are stored in the config file found under the config/ directory. You can edit this file manually, then reload the plugin to apply your changes.
Persistent data is saved in the data/ directory. This includes things like saved settings, usage stats, or player progress depending on the plugin. Deleting a data file will reset stored progress or customizations.
Language files are located in the lang/ folder. To translate messages, copy the en.json file into your target language folder (e.g. fr, de) and edit the values. Reload the plugin after changes to apply new messages.
This section lists public methods exposed by the plugin for use in other plugins. You can call these via the CallHook method. Make sure the plugin is loaded before calling its API to avoid null reference errors.
These are custom hooks that other plugins can listen for. Simply define a method with the same name and expected parameters in your plugin to handle the event. Hooks are triggered at key moments and are useful for extending or reacting to plugin behavior.
These hooks are injected into the game's code using Harmony. They let the plugin run code at key points in the game's internal logic. You can return values to block or modify behavior. Use with caution — these are powerful and can affect core mechanics.
Cart

Cart

Total -