Armory

Armory 1.4.0

Gives players instant access to a box with unlimited supplies
Documentation License Changelog (4) Version History Discussion
Works With
Gamemode Core, Gamemode Aim Train, Better No Escape




The Rust plugin provides players with instant access to virtual storage containers filled with unlimited items. Server admins can create multiple armories with different item sets and control access through permissions. Players can open armories using chat commands or by holding the USE key (configurable). Perfect for any PVP or battlefield-focused server.

Creating Your First Armory

1. Create the armory:
/arma create
Click to expand...
2. Add items:
  • A storage container opens automatically
  • Add items from your inventory or spawn them
  • Arrange items as desired
  • Close the container when done
3. Note the permission:
  • The plugin will tell you the permission (e.g., armory.1)
4. Grant permissions to players:
oxide.grant group default armory.use
oxide.grant group default armory.1
Click to expand...

Creating Additional Armories

Repeat the process for different item sets:
  • Armory #1: Basic starter kit
  • Armory #2: PVP loadout
  • Armory #3: Building materials
  • etc.
Grant different groups access to different armories based on rank or donor status.

Permissions

  • armory.use - Required to open armories. Players must have this permission AND permission for at least one specific armory to access the system.
Each armory has its own permission in the format:
  • armory.N(where N is the armory number)
    • armory.1 - Access to armory #1
    • armory.2 - Access to armory #2
    • armory.3 - Access to armory #3
    • etc.
  • armory.admin - Required to use admin commands for creating, editing, and managing armories.

Commands

Player Commands:
  • /arm - Opens the armory interface if the player has permission.
Admin Commands:
  • /arma - Displays help information for admin commands.
  • /arma create - Creates a new armory and opens a container for item configuration.
  • /arma edit <number> - Edits an existing armory's contents.
  • /arma remove <number> - Permanently deletes an armory.
  • /arma list - Lists all created armories with their details.
  • /arma info <number> - Displays detailed information about a specific armory.

Configuration

JSON: 
{
  "Version": "1.4.0",
  "Open Armory Chat Command": "arm",
  "Enable Hold Use To Open Armory": false,
  "Cooldown Between Opens Seconds": 0.0
}
  • Open Armory Chat Command - The chat command players use to open armories.
  • Enable Hold Use To Open Armory - When enabled, players can hold the USE key for 3 seconds to open armories
  • Cooldown Between Opens Seconds - Time in seconds players must wait between opening armories. Set to 0 to disable cooldown.

Stored Data

JSON: 
{
  "Permission": "armory.1",
  "Icon": "assets/prefabs/weapons/smg/smg.icon.png",
  "Items": [
    {
      "Short Name": "rifle.ak",
      "Display Name": null,
      "Skin Id": 0,
      "Amount": 1,
      "Blueprint": false
    },
    {
      "Short Name": "ammo.rifle",
      "Display Name": null,
      "Skin Id": 0,
      "Amount": 500,
      "Blueprint": false
    },
  ]
}
Each armory is saved as a separate file named by number: 1.json, 2.json, etc.

Icon Customization

Common icon paths:
Weapons:
  • assets/prefabs/weapons/ak47u/ak47u.icon.png
  • assets/prefabs/weapons/smg/smg.icon.png
  • assets/prefabs/weapons/bolt rifle/bolt_rifle.icon.png
Armor:
  • assets/prefabs/clothes/hat.coffeecan/hat.coffeecan.png
  • assets/prefabs/clothes/vest.roadsign/vest.roadsign.icon.png
Items:
  • assets/prefabs/ammo/rifle/ammo_rifle.png
  • assets/prefabs/plants/corn/corn.icon.png
Tools:
  • assets/prefabs/weapons/pickaxe/pickaxe.icon.png
  • assets/prefabs/weapons/bandage/bandage.icon.png

Localization

JSON: 
{
  "Error.NoPermission": "You do not have permission to use this.",
  "Error.OnCooldown": "You must wait {0} before opening another armory.",
  "Error.NoArmoryAccess": "You do not have access to any armories.",
  "Error.InvalidNumber": "'{0}' is not a valid armory number.",
  "Error.NotFound": "Armory #{0} does not exist.",
  "Admin.Help": "<size=16><color=#FFD700>Armory Admin Commands</color></size>\n<color=#90EE90>/arma create</color> - Create a new armory\n<color=#90EE90>/arma edit <number></color> - Edit an existing armory\n<color=#90EE90>/arma remove <number></color> - Remove an armory\n<color=#90EE90>/arma list</color> - List all armories\n<color=#90EE90>/arma info <number></color> - View armory details",
  "Admin.UnknownCommand": "Unknown command '{0}'. Type <color=#90EE90>/arma</color> for help.",
  "Admin.SessionInProgress": "An editing session is already in progress. Close the current container first.",
  "Admin.MaxReached": "Maximum number of armories (10) has been reached.",
  "Admin.BoxCreateFailed": "Failed to create the armory container.",
  "Admin.NoneExist": "No armories have been created yet. Use <color=#90EE90>/arma create</color> to create one.",
  "Admin.CannotRemoveWhileEditing": "Cannot remove armory #{0} while it is being edited.",
  "Admin.Created": "Created armory <color=#90EE90>#{0}</color> with permission <color=#FFD700>{1}</color>.\nAdd items to the container and close it to save.",
  "Admin.EditUsage": "Usage: <color=#90EE90>/arma edit <number></color>\nExample: /arma edit 1",
  "Admin.Loaded": "Loaded armory <color=#90EE90>#{0}</color> for editing.\nModify items and close the container to save changes.",
  "Admin.Saved": "Saved <color=#90EE90>{0}</color> items to armory <color=#90EE90>#{1}</color>.",
  "Admin.RemoveUsage": "Usage: <color=#90EE90>/arma remove <number></color>\nExample: /arma remove 1",
  "Admin.Removed": "Removed armory <color=#90EE90>#{0}</color>.",
  "Admin.ListHeader": "<size=16><color=#FFD700>Armories</color></size>",
  "Admin.ListEntry": "  <color=#90EE90>#{0}</color> - {1} items - <color=#FFD700>{2}</color>",
  "Admin.InfoUsage": "Usage: <color=#90EE90>/arma info <number></color>\nExample: /arma info 1",
  "Admin.InfoHeader": "<size=16><color=#FFD700>Armory #{0}</color></size>",
  "Admin.InfoPermission": "  Permission: <color=#FFD700>{0}</color>",
  "Admin.InfoIcon": "  Icon: {0}",
  "Admin.InfoItemCount": "  Items: <color=#90EE90>{0}</color>",
  "Admin.InfoContents": "  Contents:",
  "Admin.InfoContentEntry": "    - {0} x{1}",
  "Admin.InfoMoreItems": "    <color=#808080>... and {0} more items</color>"
}

Developer Hooks

C#: 
object CanOpenArmoryBox(BasePlayer player)
Called when a player attempts to open an armory box.
Parameters:
  • player - The player opening the armory
Return Values:
  • null - Allow opening
  • false - Prevent opening (silent)
  • string - Prevent opening and show message to player
Example Usage:
C#: 
object CanOpenArmoryBox(BasePlayer player)
{
    // Prevent in combat zones
    if (IsInCombatZone(player))
        return "You cannot open armories in combat zones!";

    // Prevent if raiding
    if (IsRaiding(player))
        return false;

    // Allow otherwise
    return null;
}
  • Like
Reactions: (Manky)sieve
Author
VisEntities
License duration
Unlimited
Price
9.99 USD
First release
Last update

Ratings

0.00 star(s) 0 reviews
Donate

Also by VisEntities

  • Workbench Equip Only
    Workbench Equip Only
    Requires players to be near workbenches to equip weapon mods
  • No Event Markers
    No Event Markers
    Removes map markers for events such as patrol helicopters, hackable crates, and cargo ships
  • Patrol Heli Cant Flare
    Patrol Heli Cant Flare
    Disables the flare functionality for patrol helicopters when targeted by homing missiles

Latest updates

  1. 1.4.0

    Admin commands have been restructured. Use /arma for all admin operations (create, edit, remove...

  2. 1.3.0

    Added Cooldown Seconds Between Opens config option that lets you set how long players must wait...

  3. 1.2.0

    Added option to disable opening the armory box by holding the use button. Fixed initialization...
Read more…
  • About us
    Game4Freak is a Rust plugin marketplace and modding platform offering free and premium plugins for server owners looking to improve and take their servers to the next level.
  • Our
  • Your
Back
Top
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. Parameters in < > are required, while [ ] are optional.
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.
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. Ensure 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 -