Search the Community

This plugin adds variety of NPC sets with very high number of parameter sets on standard and custom monuments. Also it is added during dropping the server AirDrop, locked crate and destroying a tank or helicopter Dependencies (optional, not required) AlphaLoot CustomLoot True PVE Kits Economics Server Rewards IQEconomic PveMode Custom maps Maps that have default settings for their custom monuments. For these maps, you will not need to create places for the appearance of NPCs, they have already been created by the map developer and are located inside the archive when buying the map You can also download all these files for all maps here Detroit: Irreparable Damage Oregon 2: Last Hope Lostly Island Frontier – American Old West Oregon: Land of Dead Badlands Foreign Lands Namalsk Kong: Skull Island Destroyed World Deathland Dreamland Last Train Pandora Railway Island Wasteland Cataclysm: Fury of Nature Last Oasis Crazy Island Standard monuments This item of the plugin settings is used for appearing NPCs in all standard monuments. All these settings are located in the Monument folder (oxide/data/BetterNpc/Monument). Each file in this folder corresponds to a standard monument If there is no standard monument file in the folder, you can create it (you need to name the file the same way as the standard monuments on the map inside the game). You can copy the settings from any other standard monument Configuration parameters: Enabled? [true/false] – It allows to enable/disable the appearance of NPC on the monument. If you need NPCs appearing on the map and don’t need it on another map, you can use this option simply The size of the monument – this parameter contains two values. It is the length and width of the monument. This parameter is necessary for random appearance of NPC on the monument and indication of limits of removal of standard NPCs on the monument (if it is necessary) Remove other NPCs? [true/false] – It deletes the standard NPCs inside the limits of this monument Presets – It is a list of all the NPC presets to appear on the monument (the description of the NPC preset settings is located below) Custom monuments This item of the plugin settings is responsible for the appearance of NPCs on custom monuments. All these settings are located in the Custom folder (oxide/data/BetterNpc/Custom). Each file in this folder corresponds to a custom monument If you have bought a map with already configured NPC appearance files for custom monuments you will copy these files into the Custom folder. If you want to create and configure the appearance of NPC in your custom location on the map, you will use the command in the administrators’ chat /SpawnPointAdd {name} (see the description of this command below in the instruction) Configuration parameters: Enabled? [true/false] – It allows to enable/disable the appearance of NPC on the monument. If you need NPCs appearing on the map and don’t need it on another map, you can use this option simply Position – It is a position of the custom monument on the map Rotation – It is a rotation of the custom monument on the map (this parameter is necessary for using custom places to appear of NPC on the monument, if the monument is used on more than one map) Radius – It is the radius of the custom monument from the position on the map Remove other NPCs? [true/false] – It removes the standard NPCs inside the limits of this monument Presets – It is a list of all the NPC presets to appear on the monument (the description of the NPC preset settings is located below) Roads This item of the plugin settings is used to appear NPCs on all types of roads. All these settings are located in the Road folder (oxide/data/BetterNpc/Road). Each file in this folder corresponds to a particular road type ExtraNarrow – It is a narrow, unpaved walkway ExtraWide It is a wide, paved, two-lane, beltway road Standard – It is a regular, paved road Configuration parameters: Enabled? [true/false] – It allows to enable/disable the appearance of NPC on the road. If you need NPCs appearing on the map and don’t need it on another map, you can use this option simply Presets – It is a list of all the NPC presets to appear on the road (the description of the NPC preset settings is located below) Biomes This item of the plugin settings is used to appear NPCs on all types of biomes. All these settings are located in the Biome folder (oxide/data/BetterNpc/Biome). Each file in this folder corresponds to a particular biome type (Arctic, Arid, Temperate, Tundra) Configuration parameters: Enabled? [true/false] – It allows to enable/disable the appearance of NPC on the biome. If you need NPCs appearing on the map and don’t need it on another map, you can use this option simply Presets – It is a list of all the NPC presets to appear on the biome (the description of the NPC preset settings is located below) In-game events This item of the plugin settings is used to appear the NPCs in standard Rust events. All of these settings are located in the Event folder (oxide/data/BetterNpc/Event). Each file in this folder corresponds to its own type of event The supported events: When the plane drops the server AirDrop, it will be guarded by specific NPC presets CH47 – When the chinook drops a locked crate during patrolling the map, it will be guarded by specific NPC presets Bradley – When someone destroys a tank, its crates will be guarded by specific NPC presets Helicopter – When someone shoots down a patrol helicopter, its crates will be guarded by specific NPC presets Configuration parameters: Enabled? [true/false] – It allows to enable/disable the appearance of NPC on the event. If you need NPCs appearing on the map and don’t need it on another map, you can use this option simply Radius – NPC appearance radius Presets – It is a list of all the NPC presets to appear on the event (the description of the NPC preset settings is located below) The NPC preset parameters Enabled? [true/false] – It is enabling/disabling the preset Minimum numbers – Day – It is the minimum number of NPCs from the day preset Maximum numbers – Day – It is the maximum number of NPCs from the day preset Minimum numbers – Night – It is the minimum number of NPCs from the night preset Maximum numbers – Night – It is the maximum number of NPCs from the night preset NPCs setting – It is all NPC settings of this preset (see the description of NPC settings for details) Type of appearance (0 – random; 1 – own list) – It is a type of NPC appearance. You can create your own list of places of NPC appearance. The NPC will appear only randomly. This parameter is not used in Road appearance types Own list of locations – It is your own list of NPC appearances. You need to use the number of locations at least the maximum possible number of NPCs in this preset. This parameter is not used in Road appearance types The path to the crate that appears at the place of death – It is the full path to the crate prefab that appears at the place of death of an NPC. If you don’t need this parameter, you should leave this blank Which loot table should the plugin use (0 – default; 1 – own; 2 – AlphaLoot; 3 – CustomLoot; 4 – loot table of the Rust objects; 5 – combine the 1 and 4 methods) – It is the type of the NPC loot table in this preset. Type 5 includes two types (1 and 4) at the same time and locates items from both types Loot table from prefabs (if the loot table type is 4 or 5) – It is a setting of the loot tables from Rust objects. You can see the loot table of Rust objects description for more details Own loot table (if the loot table type is 1 or 5) – It’s NPC’s own loot table. You can see the description of your own loot table for more details The NPC settings description Names is a list of NPC names. It is selected from the list randomly Health – It’s the HP amount of the NPC Roam Range – It’s the patrolling area distance. It’s the distance that the NPC can move from the place of appearance during patrolling Chase Range – It’s the chase range of the target. It’s the distance that the NPC can chase his target from the place of appearance Attack Range Multiplier – It’s the attack range multiplier of the NPC’s weapon Sense Range – It’s a target detection radius Target Memory Duration [sec.] – It’s the time that the NPC can remember his target Scale damage – It’s the damage multiplier from NPC to the player Aim Cone Scale – It’s the spread of NPC shooting, the default value in Rust is 2. It doesn’t take negative values Detect the target only in the NPCs viewing vision cone? [true/false] – It’s the parameter that allows detecting the target only in a certain NPC viewing. If you want to detect the target in 360 degrees, you will set the parameter “False” Vision Cone – It’s the NPC viewing. The range of values is from 20 to 180 degrees. If the previous parameter is False, this parameter is not used Speed – It’s the NPC speed. The default value in Rust is 5 Minimum time of appearance after death [sec.] – It’s the minimum time of NPC appearance after the death. This parameter is not used in the NPC Event places Maximum time of appearance after death [sec.] – It’s the maximum time of NPC appearance after the death. This parameter is not used in the NPC Event places Disable radio effects? [true/false] – You can disable/enable radio effects Is this a stationary NPC? [true/false] – If this parameter is True, the NPC will not move or run Remove a corpse after death? [true/false] – This parameter can control the deleting of NPC corpses (only backpacks are left). This parameter improves efficiency if there are a lot of NPCs Wear items – It’s a list of NPCs’ clothes and armor Belt items – It’s a list of weapons and items NPCs’ fast slots. Medical syringes are used for healing. If you give grenades to an NPC, he will use them. Smoke grenades are used for creating smoke screens (if you don’t need them, you should remove them from your inventory). If you give a Rocket Launcher to an NPC, he will raid the target’s building (if the target is inside it) Kits – It gives a pack of Kits plugin. If you don’t need this parameter, you should leave this blank. I recommend using the previous 2 points to configure NPC items A description of the Rust loot table settings Minimum numbers of prefabs –It’s the minimum numbers of prefabs that are needed to appear in the NPC loot table Maximum numbers of prefabs –It’s the maximum numbers of prefabs that are needed to appear in the NPC loot table Use minimum and maximum values? [true/false] – this parameter specifies whether to use the minimum and maximum numbers to limit the number of items List of prefabs – It’s a list of prefabs that need to add in the loot table. It is necessary to indicate the full path to the prefab and the probability of falling out this prefab A description of the own loot table settings Minimum numbers of items – It’s the minimum number of items Maximum numbers of items – It’s the maximum number of items Use minimum and maximum values? [true/false] – this parameter specifies whether to use the minimum and maximum numbers to limit the number of items List of items – It’s a total list of all items that can fall out in the NPC loot table. You can specify any standard items, their blueprints and any skinned or custom items The commands in the chat (for admins only) /SpawnPointPos {name} – To show the local admin’s position coordinates relative to the place where the NPC {name} appears /SpawnPointAdd {name} – To create the NPC appearance point {name} in the Admin’s custom coordinates. A file with this name will be created in the folder Custom and you can configure it as you need /SpawnPointAddPos {number} {name} – To write the local admin’s coordinate into the preset with the positional number {number} (starting from 1) to the place where the NPC {name} appears /SpawnPointAddWear {number} {name} – To write all the admin’s dressed clothes into the preset with the positional number {number} (starting from 1) to the place where the NPC {name} appears /SpawnPointAddBelt {number} {name} – To write all the admins’ quick slots cells into a preset with the positional number {number} ( starting from 1) to the place where the NPC {name} appears /SpawnPointShowPos {number} {name} – To show to the Admin all the custom NPC appearance points in the preset with the positional number {number} ( starting from 1) in the place where the NPC {name} appears /SpawnPointReload {name} – Reload Spawn Point with the name {name} Console commands (RCON only) ShowAllNpc – Shows the number of all NPCs of the BetterNpc plugin on your server Hooks object CanAirDropSpawnNpc(SupplyDrop supplyDrop) – It is called before an NPC appearance to guard an AirDrop. The returning of a non-zero value stops an NPC appearance object CanCh47SpawnNpc(HackableLockedCrate crate) – It is called before an NPC appearance to guard a locked chinook crate. The returning of a non-zero value stops an NPC appearance object CanBradleySpawnNpc(BradleyAPC bradley) – It is called before an NPC appearance to guard the boxes from crushed Bradley. The returning of a non-zero value stops an NPC appearance object CanHelicopterSpawnNpc(BaseHelicopter helicopter) – It is called before an NPC appearance to guard the crates from crushed patrol helicopter. The returning of a non-zero value stops an NPC appearance API void DestroyController(string name) – It destroys the place of appearance NPC with the name {name} void CreateController(string name) – It creates the place of appearance NPC with the name {name} These APIs can be used with standard monuments, custom monuments (NPC locations) and roads. The name of this monument is in standard monuments {name}. It is the name of the file in the Custom and Road folder in custom monuments and roads My Discord: KpucTaJl#8923 Join the Mad Mappers Discord here! Check out more of my work here! Creator of the default configuration – jtedal

Introducing the AutoBan plugin for Rust servers - a powerful and efficient tool for managing and controlling player behavior on your server. This plugin is designed to help server owners and administrators keep their servers running smoothly and free from rule-breaking players. AutoBan's key feature is its ability to automatically ban players based on reports made by other players. If a player exceeds a certain number of reports (configurable by the server owner), they will be automatically banned with a customizable reason message. In addition, the plugin includes a variety of tools for server administrators to manage and view reports and bans, including console commands, chat commands, and a broadcast feature that notifies administrators of new bans. Here is a list of features included in the AutoBan plugin: Automatic banning of players based on the number of reports they have received Customizable reason messages for bans Valid report reasons that can be set by the server owner Option to broadcast ban messages to the chat Ignored players list that allows certain players to be excluded from automatic banning Timer for broadcasting bans to administrators and console Chat commands and console commands for managing reports and bans Permissions system for controlling who can access the plugin's features Detailed logging of all bans and reports Discord Alerts Option to send reports to a url Timed bans Usage: CHAT COMMANDS: /AB.report <username> reason> /AB.viewreports /AB.ban <user> <reason> /AB.unban user /AB.showbans /AB.resetreports <userid> CONSOLE COMMANDS: AB.getreports AB.getbans AB.resetreportsConsole <userid> AB.ban <userid> <reason> AB.unban <userid> <reason> OXIDE PERMISSIONS: AutoBan.report AutoBan.chatreport AutoBan.viewreports AutoBan.ignore AutoBan.ban AutoBan.unban AutoBan.viewbans CONFIG: { "Max reports till user gets banned": 5, "Reason given to banned user": "You have been reported too many times, and have been banned for precautionary measures, an admin will review this suspension soon.", "Valid reasons *searches subject title and message of the report* ( To make sure report is scanned, add different variations of reason; like cheat, cheater, cheating, cheats, etc. )": [ "cheating", "cheats", "hacks", "aimbot", "hacking", "esp", "teaming", "racism", "griefing", "walling", "doorcamping", "spawn killing" ], "Valid report types": [ "cheat", "abusive", "name", "spam" ], "Scan type of F7 reports": true, "Broadcast ban to chat": true, "Ignored Players *Steam ID's Only*": { "76561198000000000": "Admin" }, "Timer for broadcasting bans to admins and console": 820, "Send bans to users with the AutoBan.viewbans permission based on timer ( In-Game )": false, "Send reports to URL": false, "URL to send reports to": "http://example.com", "Send reports to Discord": false, "Send bans to Discord": false, "Discord Reports Webhook URL": "http://example.com", "Discord Bans Webhook URL": "http://example.com", "Ban Timer ( In hours or 'permanent' )": "72" } This plugin is a must-have for any server owner looking to keep their servers running smoothly and efficiently. With its powerful features and easy-to-use interface, AutoBan makes it easy to manage and control player behavior on your server. ROADMAP: Currently adding protection for mass reporting as a team

Creates a unique event at the Harbor monument for players to participate in for rewards. Players must battle numerous NPCs and APCs to access the puzzle to open the loot room! Description This event started off as a warning on the chatbox about the ships coming soon to dock in Port, loaded with precious cargo. After the period has passed, a ship appears in one of the locations at Harbour that are accessible from the map, where the crane loads the container. The loading area is protected by one Tank and 7 NPCs by default. The container door is locked, you must push a button from inside the cranes cockpit to open the door. Inside the container, there is a default security camera, locked box, 2 DMS, 2 Elite, and 2 Military boxes. The locations and loot from all crates/NPCs can be configured within configurations, and unwanted crates/NPCs added or removed. Also, ships will generate the default ship loot, e.g. The config file allows to modify tank as well as loot inside of the ship. When the event occurs, the map displays the markers (configured in the config file). All players that are inside the event area will have a timer counting down the amount of time until the event ends. Dependencies Required NpcSpawn Dependencies (optional, not required) True PVE PveMode GUI Announcements Notify Discord Messages AlphaLoot CustomLoot NTeleportation HeliControl Economics Server Rewards IQEconomic Kits Chat commands (only for administrators) /harborstart – starting of the event /harborstop – ending of the event /harborpos – determining the position and rotation coordinates for changing the location of NPCs and crates.It should write in the configuration (Attention! The event must be started, the current position of the administrator in relation to the cargoship is read) Console commands (RCON only) harborstart – starting of the event harborstop – ending of the event Plugin Config en - example of plugin configuration in English ru - example of plugin configuration in Russian Hooks void OnHarborEventStart() – called when the event starts void OnHarborEventEnd() – called when the event ends void OnHarborEventWinner(ulong winnerId) – called at the end of the event, where the winnerId is the player who did more actions to complete the event My Discord: KpucTaJl#8923 Join the Mad Mappers Discord here! Check out more of my work here!

Allows to automate horse dung gathering, by adding Industial Adapters and BoxStorage to the HitchTrough and Composter. Also auto spliting dungs in the Composter container. Note: During plugin unloading, modified entities are not removed, to prevent the removal of pipes every time the plugin/server is restarted. To remove modifications from entities, you should use the "idung unload" command. industrialdung.admin - Provides unrestricted access to the plugin's functionality. This includes the ability to add/remove or clear modificated entities from other players. Note: In the configuration file, within the "Max ammount of modified entites per group" section, you can specify limits for any existing permission by simply listing its name. "Max ammount of modified entites per group": { "MyPermission": { "HitchTroughs": 5, "Composters": 2 }, ... If you want to create a new permission, you can also include it in the list, but the name must begin with "industrialdung". { "Chat command": "idung", "Use GameTip for messages?": true, "Use auto splitting in the Composter?": true, "Wood Storage Box Workshop Skin ID": 2911301119, "The list of items(short name) available for the composter. Leave empty to use vanilla": [ "horsedung", "fertilizer", "plantfiber" ], "Max ammount of modified entites per group": { "industrialdung.default": { "HitchTroughs": 5, "Composters": 2 }, "industrialdung.vip": { "HitchTroughs": 10, "Composters": 4 }, "realpve.vip": { "HitchTroughs": 15, "Composters": 6 } }, "Popup - Duration": 6.0, "Popup - Icon Url": "https://i.imgur.com/4Adzkb8.png", "Popup - Icon Color": "#CCE699", "Popup - Icon Transparency": 0.8, "Popup - AnchorMin": "0 1", "Popup - AnchorMax": "0 1", "Popup - OffsetMin": "30 -90", "Popup - OffsetMax": "270 -40", "Popup - Text Size": 14, "Popup - Text Color": "#FFFFFF", "Popup - Text Font(https://umod.org/guides/rust/basic-concepts-of-gui#fonts)": "RobotoCondensed-Bold.ttf", "Popup - SubText Size": 12, "Popup - SubText Color": "#FFFFFF", "Popup - SubText Font": "RobotoCondensed-Regular.ttf", "Popup - Text FadeIn": 1.0, "Popup - Sound Prefab Name": "assets/bundled/prefabs/fx/invite_notice.prefab", "Version": { "Major": 0, "Minor": 1, "Patch": 6 } } EN: { "MsgNotAllowed": "You do not have permission to use this command!", "MsgNotHitchOwner": "You are not the owner of this hitch trough!", "MsgNotComposterOwner": "You are not the owner of this composter!", "MsgNotEntity": "You need to look at the hitch trough/composter or provide correct net ID!", "MsgNotModifiedEntity": "This entity is not modified!", "MsgLimitReached": "You cannot to modify this entity as you have reached your limit of {0}!", "MsgPopupTextHitch": "Modify this hitch trough?", "MsgPopupTextComposter": "Modify this composter?", "MsgPopupSubText": "Click on the notification to confirm", "MsgHitchTroughAdded": "The hitch trough has been successfully modified!", "MsgComposterAdded": "The composter has been successfully modified!", "MsgMyRemovedHitch": "The modification from the hitch trough has been successfully removed!", "MsgMyRemovedComposter": "The modification from the composter has been successfully removed!", "MsgMyAllRemoved": "All your modifications from the hitch troughs and composters have been successfully removed!", "MsgPlayerMsgAllRemoved": "All {0}'s modifications from the hitch troughs and composters have been successfully removed!", "MsgAllRemoved": "All modifications from the hitch troughs and composters have been successfully removed!", "MsgAutoModifyEntityEnabled": "Automatic entity modification is enabled!", "MsgAutoModifyEntityDisabled": "Automatic entity modification is disabled!" } RU: { "MsgNotAllowed": "У вас недостаточно прав для использования этой команды!", "MsgNotHitchOwner": "Вы не являетесь владельцем данной кормушки!", "MsgNotComposterOwner": "Вы не являетесь владельцем данного компостера!", "MsgNotEntity": "Вам необходимо смотреть на кормушку/компостер или указать корректный net ID!", "MsgNotModifiedEntity": "Данная сущность не является модифицированной!", "MsgLimitReached": "Вы не можете модифицировать данную сущность, так как вы превысили свой лимит в {0}!", "MsgPopupTextHitch": "Модифицировать данную кормушку?", "MsgPopupTextComposter": "Модифицировать данный компостер?", "MsgPopupSubText": "Нажмите на уведомление для подтверждения", "MsgHitchTroughAdded": "Кормушка успешно модифицирована!", "MsgComposterAdded": "Компостер успешно модифицирован!", "MsgMyRemovedHitch": "Модификация с кормушки успешно удалена!", "MsgMyRemovedComposter": "Модификация с компостера успешно удалена!", "MsgMyAllRemoved": "Все ваши модификации из кормушек и компостеров успешно удалены!", "MsgPlayerMsgAllRemoved": "Все модификации из кормушек и компостеров игрока {0} успешно удалены!", "MsgAllRemoved": "Все модификации из кормушек и компостеров успешно удалены!", "MsgAutoModifyEntityEnabled": "Автоматическая модификация сущностей включена!", "MsgAutoModifyEntityDisabled": "Автоматическая модификация сущностей выключена!" } 1. idung add - Adding a modification to the HitchTrough/Composter that you are looking at from a distance of no more than 10 meters. idung add *netID* - Adding a modification to the HitchTrough/Composter with the specified netID; 2. idung remove - Removing a modification from the HitchTrough/Composter that you are looking at from a distance of no more than 10 meters. idung remove *netID* - Removing a modification from the HitchTrough/Composter with the specified netID; 3. idung clear - Removing all modification from your HitchTroughs and Composters. idung clear *userID* - Removing all modification from specified player's HitchTroughs and Composters. Permission "industrialdung.admin" required. idung clear all - Removing all modification from all HitchTroughs and Composters. Permission "industrialdung.admin" required. 4. idung auto - Enabling/Disabling automatic modification of HitchTroughs and Composters, if possible. 5. idung aclear - Removing all modifications from the HitchTroughs and Composters that were not added to the data files for some reason. Permission "industrialdung.admin" required. 6. idung unload - Unloading the plugin with the removal of all modifications from HitchTroughs and Composters without deleting them from the data file. Permission "industrialdung.admin" required.

Useful auxiliary plugin that allows other plugins to customize the status bar through an API. Note: AdvancedStatus does not display any bars on its own. This is done by other plugins that work with it. An example plugin demonstrating interaction with AdvancedStatus. The ability to specify the frequency of calculating the number of bars; The ability to specify the order of the bar; The ability to change the height of the bar; The abillity to customize the color and transparency of the background; The ability to set a material for the background; The ability to switch between CuiRawImageComponent and CuiImageComponent for the image; The abillity to set own image and customize the color and transparency of the image; The abillity to set sprite instead of the image; The ability to specify custom text. Additionally, customization options for the color, size, and font of the text; No need to pass all parameters; No need to manually delete your bar when unloading your plugin. { "Client Status Bar Count Interval": 0.5, "Bar - Display Layer(https://umod.org/guides/rust/basic-concepts-of-gui#layers)": "Hud", "Bar - Left to Right": true, "Bar - Offset Between": 2, "Bar - Default Height": 26, "Main - Default Color": "#505F75", "Main - Default Transparency": 0.7, "Main - Default Material(empty to disable)": "", "Image - Default Color": "#6B7E95", "Image - Default Transparency": 1.0, "Text - Default Size": 12, "Text - Default Color": "#FFFFFF", "Text - Default Font(https://umod.org/guides/rust/basic-concepts-of-gui#fonts)": "RobotoCondensed-Bold.ttf", "Text - Default Offset Horizontal": 0, "SubText - Default Size": 12, "SubText - Default Color": "#FFFFFF", "SubText - Default Font(https://umod.org/guides/rust/basic-concepts-of-gui#fonts)": "RobotoCondensed-Bold.ttf", "Progress - Default Color": "#89B840", "Progress - Default Transparency": 0.7, "Progress - Default OffsetMin": "25 2.5", "Progress - Default OffsetMax": "-3.5 -3.5", "Version": { "Major": 0, "Minor": 1, "Patch": 14 } } Note: Default values will be used if the external plugin does not pass the property itself. EN: { "MsgDays": "d", "MsgHours": "h", "MsgMinutes": "m", "MsgSeconds": "s" } RU: { "MsgDays": "д", "MsgHours": "ч", "MsgMinutes": "м", "MsgSeconds": "с" } OnPlayerGainedBuildingPrivilege: Called after the player enters their building privilege. OnPlayerLostBuildingPrivilege: Called after the player exits their building privilege. void OnPlayerGainedBuildingPrivilege(BasePlayer player) { Puts($"{player.displayName} entered the authorized building privilege zone."); } void OnPlayerLostBuildingPrivilege(BasePlayer player) { Puts($"{player.displayName} exited the authorized building privilege zone."); } There are 7 methods: CreateBar UpdateContent DeleteBar DeleteCategory DeleteAllBars BarExists InBuildingPrivilege There are 4 types of bar: Default - A simple bar that displays the provided information. Does not update the value of SubText by itself; Timed - Similar to the default bar, but it automatically disappears after the specified time in the TimeStamp parameter; TimeCounter - The SubText shows the remaining time until TimeStamp. Also automatically removed upon expiration of the TimeStamp; TimeProgress - Similar to the TimeCounter bar, but additionally features a progress bar. CreateBar: Used to create a bar or update bar values for a player. To call the CreateBar method, you need to pass 2 parameters. The first one is BasePlayer or <ulong>playerID. The second one is a dictionary with the parameters you need. In the CreateBar method, all parameters are optional, except for two: Id; Plugin. Parameters not specified when creating a new bar will use the values set in the AdvancedStatus plugin's configuration file. Parameters not specified during bar update will retain the values they had before the update. Note: The plugin does not update values automatically, you need to manually send new values. Dictionary<string, object> parameters = new Dictionary<string, object> { { "Id", _barID }, //<string>Unique identifier for the bar in your plugin. ***This is a required field. { "BarType", "Default" }, //<string>Type of the bar. There are 4 types: Default, Timed, TimeCounter and TimeProgress. { "Plugin", Name }, //<string>Name of your plugin. ***This is a required field. { "Category", "Default" }, //<string>Internal plugin category of the bar. { "Order", 10 }, //<int>The position of your bar relative to others. Order is determined by increasing values(ASC). { "Height", 26 }, //<int>The height of your bar. A standard bar is 26 pixels. { "Main_Color", "#505F75" }, //<string>HTML Hex color of the bar background. { "Main_Transparency", 0.7f }, //<float>Transparency of the bar background. { "Main_Material", "assets/content/ui/uibackgroundblur.mat" }, //<string>Material of the bar background(empty to disable). { "Image", "scrap" }, //<string>Name of the image saved in the ImageLibrary or a direct link to the image if ImageLibrary is not used. { "Image_Sprite", "" }, //<string>Sprite image of the bar. (If empty, Image will be used as the image). { "Is_RawImage", true }, //<bool>Which type of image will be used? True - CuiRawImageComponent. False - CuiImageComponent. { "Image_Color", "#6B7E95" }, //<string>HTML Hex color of the bar image. { "Image_Transparency", 1.0f }, //<float>Transparency of the image. { "Text", "Scrap" }, //<string>Main text. { "Text_Size", 12 }, //<int>Size of the main text. { "Text_Color", "#FFFFFF" }, //<string>HTML Hex color of the main text. { "Text_Font", "RobotoCondensed-Bold.ttf" }, //<string>Font of the main text. { "Text_Offset_Horizontal", 0 }, //<int>Horizontal offset for the main text. { "SubText", "35" }, //<string>Sub text. { "SubText_Size", 12 }, //<int>Size of the sub text. { "SubText_Color", "#FFFFFF" }, //<string>HTML Hex color of the sub text. { "SubText_Font", "RobotoCondensed-Bold.ttf" }, //<string>Font of the sub text. { "TimeStamp", Network.TimeEx.currentTimestamp + 6 }, //<double>Used if the bar type is Timed, TimeCounter or TimeProgress. { "Progress", (float)35 / 100f }, //<float>Progress. From 0.0 to 1.0. { "Progress_Color", "#89B840" }, //<string>Progress color. { "Progress_Transparency", 1f }, //<float>Progress transparency. { "Progress_OffsetMin", "25 2.5" }, //<string>Progress OffsetMin: "*left* *bottom*". { "Progress_OffsetMax", "-3.5 -3.5" }, //<string>Progress OffsetMax: "*right* *top*". { "Command", "kit" } //<string>If the field is not empty, the bar becomes clickable, and the specified command is executed upon clicking. Note: the command must be covalence. }; AdvancedStatus?.Call("CreateBar", player.userID, parameters); //Calling the CreateBar method with the passing of BasePlayer/playerID and a dictionary containing the required parameters. UpdateContent: Used to update only the content of an existing status bar. To call the UpdateContent method, you need to pass 2 parameters. The first one is BasePlayer or <ulong>playerID. The second one is a dictionary with the parameters you need. In the UpdateBar method, all parameters are optional, except for two: Id; Plugin. var parameters = new Dictionary<string, object> { { "Id", "MyID" }, //<string>Unique identifier for the bar in your plugin. ***This is a required field. { "Plugin", Name }, //<string>Name of your plugin. ***This is a required field. { "Text", "MyText" }, //<string>Main text. { "SubText", "MyText" }, //<string>Sub text. { "Progress", (float)amount / 100f }, //<float>Progress. From 0.0 to 1.0. }; AdvancedStatus?.Call("UpdateContent", player, parameters); //Calling the UpdateContent method with the passing of BasePlayer/playerID and a dictionary containing the required parameters. DeleteBar: Used to remove the bar for a player. There are two methods for removing a bar by ID: with specifying a particular player; To call this method, you need to pass 3 parameters. The first one is BasePlayer or <ulong>playerID. The second one is Id of your bar and the third one is name of your plugin. without specifying a particular player (which removes it for all players) To call this method, you need to pass 2 parameters. The first one is Id of your bar and the second one is name of your plugin. AdvancedStatus?.Call("DeleteBar", player, barID, Name);//Calling the DeleteBar method with the passing of BasePlayer/playerID, ID of the bar and the name of your plugin. AdvancedStatus?.Call("DeleteBar", barID, Name);//Calling the DeleteBar method with the passing of ID of the bar and the name of your plugin. If you try to delete a bar that doesn't exist, nothing bad will happen. So feel free to delete the bar without checking its existence. P.S. When unloading your plugin, there is no need to manually delete bars for players, AdvancedStatus will handle it automatically. DeleteCategory: Used to remove all bars associated with the plugin's category. To call the DeleteCategory method, you need to pass 2 parameters. The first one is category and the second one is name of your plugin. AdvancedStatus?.Call("DeleteCategory", "Default", Name);//Calling the DeleteCategory method by passing the category and name of your plugin DeleteAllBars: Used to remove all bars associated with the plugin. To call the DeleteAllBars method, you need to pass only 1 parameter. It is name of your plugin. AdvancedStatus?.Call("DeleteAllBars", Name);//Calling the DeleteAllBars method, passing the name of your plugin BarExists: Used to check if the specified bar exists. To call the BarExists method, you need to pass 3 parameters. The first one is BasePlayer or <ulong>playerID. The second one is Id of your bar. And the third one is name of your plugin. (bool)AdvancedStatus?.Call("BarExists", player, barID, Name);//Calling the BarExists method with the passing of BasePlayer/playerID, ID of the bar and name of your plugin. InBuildingPrivilege: Used to check if the player has authorized building privileges. To call the InBuildingPrivilege method, you need to pass BasePlayer or <ulong>playerID. (bool)AdvancedStatus?.Call("InBuildingPrivilege", player, false);//Checking if the player has Building Privilege.

This plugin demonstrates the integration with the AdvancedStatus plugin. It displays the amount of a specific item in the player's inventory in the status bar. In this case, it's Scrap, to track a different item, replace the itemID value on line 16 with the ID of the desired item. This plugin can be downloaded by plugin developers as a reference to understanding how to work with the AdvancedStatus and by server owners to easily display desired items in the status bar.

Clans is an all-in-one manager that lets you create, manage and invite players all from one stunning interface. Toggle friendly fire, view clan, and player leaderboards, create and break alliances, modify gather rates for clan members and set clan skins to identify clan members abroad easily. Features Beautiful user interface Performance Allied clans Gather rate for players (allows you to set how much each clan member must collect resources. For example: each member of the clan must collect 10 thousand sulfur, so that later it can be used to craft explosives and attack another clan) Clan skins (allows you to set common skins for all clan players. All the clothes on the players of the same clan will be the same, which allows you to distinguish your own from the enemies during the battle) The clan TAG min- and max-length can be defined in the config The clan overview shows offline member names Clan members can toggle friendly-fire protection for clan mates and allies Clan creation can check TAG’s against a blocked word list Clan tagging can be optionally disabled Old (not updated since x days) clans can be automatically purged Clans rating Players rating Setting a personal avatar for your clan Autowipe with wipe (optional) Commands clans (display clan menu) clans help (get information about commands) clan create (create a clan) clan leave (leave from your clan) clan join (open UI with invitations) clan ff (toggle friendlyfire status) clan allyff (toggle friendlyfire status for allies) clan invite <name/steamid> (invite a player) clan withdraw <name/steamid> (cancel an invite) clan kick <name/steamid> (kick a member) clan allyinvite <clanTag> (invite a clan to ally) clan allywithdraw <clanTag> (cancel the offer of an alliance) clan allyaccept <clanTag> (accept the offer of an alliance) clan allycancel <clanTag> (cancen the offer of an alliance) clan promote <name/steamid> (promote a member) clan demote <name/steamid> (demote a member) clan disband (disband your clan) clans.loadavatars (download avatars of all players) clans.manage list - lists all clans, their owners and their member-count clans.manage listex - lists all clans, their owners/members and their on-line status clans.manage show [name/userId] - lists the chosen clan (or clan by user) and the members with status clans.manage msg [clanTag] [message] - sends a clan message clans.manage create [name/userId] [clanTag] - creates a clan clans.manage rename [oldTag] [newTag] - renames a clan clans.manage disband [clanTag] - disbands a clan clans.manage invite [clanTag] [name/userId] - sends clan invitation to a player clans.manage join [clanTag] [name/userId] - joins a player into a clan clans.manage kick [clanTag] [name/userId] - kicks a member from a clan clans.manage owner [clanTag] [name/userId] - sets a new owner clans.manage promote [clanTag] [name/userId] - promotes a member clans.manage demote [clanTag] [name/userId] - demotes a member clans.reborn.convert (convert data from Clans Reborn plugin) clans.umod.convert (convert data from uMod Clans (v0.2.2+) plugin) clans.convert.olddata (convert data from old data) clans.convert.old.stats – used to update player data when upgrading from older versions of the game to 1.1.31 and above. Permissions clans.cancreate (permission to create a clan) clans.canjoin (permission to join a clan) clans.canleave (permission to leave a clan) clans.candisband (permission to disband a clan) clans.cankick (permission to kick a clan member) clans.admin (permission to use command 'clans.manage') Loot Types None – used for disabled loot Gather – used for gathering loot LootCrate – used for a loot crate Look – used to look at loot Kill – used to kill entities Craft – used for crafting items HackCrate – used for hacking a loot crate FAQ Q: Where can I see an example of a config? A: Config Q: Does the Clans plugin support other plugins? A: Yes, this Clans plugin has an API similar to other popular clans plugins. If the plugin works with Clans - it works with this plugin too. Q: How do I enable the display of clan ratings on the screen? A: You need to install the Clans Top plugin Q: Does the Clans plugin work with other Rust plugins? A: The Clans plugin is designed to work with a wide range of other Rust plugins, but compatibility may vary depending on the specific plugins you are using.

The New Year is coming and I have prepared for you a new preset customization for the train!After installing the update, customization will be automatically applied to all cars in the configuration of the armored train. To disable this, make the "Customization preset" parameter empty in the config. You can also disable the customization of certain wagons or change the customization of the NPCs in the file oxide/data/ArmoredTrain/NewYear New Year's map from the video: This plugin will add an armored train to your server, which can travel both in the subway and by rail. It can consist of any number of wagons. A helicopter can accompany it. Bradley, npc, turrets, simsites can be installed on the train. The plugin allows you to create any number of train presets, for which the order of wagons, the helicopter preset, the probability of spawn and the duration of patrolling can be specified. Each wagon or locomotive can be configured separately. Any speed can be set by the locomotive.If there is no spawn of trains on the surface on your custom map, read the section “Custom spawn points” Caboose By default, one of the presets of the train is a locomotive and a caboose. This train does not attack players first and there is no loot on it. It is intended only for players to travel around the map. You can add a caboose wagon to any other train, or create your own galley train with any number and any set of wagons. Halloween Update Have you already prepared your server for Halloween? On the eve of the Halloween Rust update, I have prepared for customization of all armored train cars. After installing the update, customization will be automatically applied to all cars in the configuration of the armored train. To disable this, make the "Customization preset" parameter empty in the config. Custom spawn points If you are using a custom map in which there are no spawn trains on the surface, but there is a railway, then for the train to work on the surface, you need to add custom spawn points of the train. Instruction: Stand at the point where you want the train to spawn Enter the command /atrainpoint If you receive a message that a point has been created, enable “Use custom spawn coordinates [true/false]” in config For correct operation, it is recommended to create several spawn points of the train Chat commands (only for administrators) /atrainstart– launches the event in a random configuration /atrainstartunderground - forcibly launches an event underground /atrainstartaboveground - forcibly launches an event aboveground /atrainstart <trainPresetName> – launches the event in the <trainPresetName> configuration /atrainstartunderground <trainPresetName> /atrainstartaboveground <trainPresetName> /atrainstop– stops the event /atrainpoint– creates a custom spawn point of the train in your position Console commands (RCON only) atrainstart– launches the event in a random configuration atrainstartunderground - forcibly launches an event underground atrainstartaboveground - forcibly launches an event aboveground atrainstart <trainPresetName> – launches the event in the <trainPresetName> configuration atrainstartunderground <trainPresetName> atrainstartaboveground <trainPresetName> atrainstop – stops the event Config en – example of plugin configuration in English ru – example of plugin configuration in Russian Dependencies (optional, not required) True PVE PveMode GUI Announcements Notify DiscordMessages AlphaLoot CustomLoot Economics Server Rewards IQEconomic Api bool IsArmoredTrainActive() bool StopArmoredTrain() bool StartArmoredTrainEvent() bool EndArmoredTrainEvent() bool IsTrainBradley(uint netID) bool IsTrainHeli(uint netID) bool IsTrainCrate(uint netID) bool IsTrainSamSite(uint netID) bool IsTrainWagon(uint netID) bool IsTrainTurret(uint netID) Vector3 ArmoredTrainLocomotivePosition() Hooks OnArmoredTrainEventStart OnArmoredTrainEventStop Contact me in Discord: Adem#955

Adds to your server the ability to rent a car and ride it all over the map. You can also install bots in which you can rent a car. Commands share.ferrari [targetId] (give a Ferrari) share.mazda [targetId] (give a Mazda) share.skoda [targetId] (give a Skoda) share.opel [targetId] (give an Opel) Permissions You can set permission in config, for example: "Permission (example: carsharing.use)": "carsharing.use", Config { "Commands": [ "rent", "carsharing" ], "Permission (example: carsharing.use)": "", "Work with Notify?": true, "Economy": { "Type (Plugin/Item)": "Plugin", "Plugin name": "Economics", "Balance add hook": "Deposit", "Balance remove hook": "Withdraw", "Balance show hook": "Balance", "ShortName": "scrap", "Display Name (empty - default)": "", "Skin": 0 }, "Vehicle call item settings": { "Display Name": "RUSTSharing {carname}", "ShortName": "box.wooden.large", "Skin": 2591806406 }, "Cars": [ { "Permission (example: carsharing.vip)": "", "Command to give": "share.ferrari", "Image": "https://i.imgur.com/0GvWGOv.png", "Name": "Ferrari", "Cost per minute": 25.0, "Car class": "Luxe", "Average Speed": "100", "Modular Car Settings": { "CodeLock": true, "KeyLock": false, "Engine Parts Tier": 2, "Fresh Water Amount": 0, "Fuel Amount": 140, "Modules": [ "vehicle.1mod.engine", "vehicle.1mod.cockpit.armored", "vehicle.1mod.cockpit.armored" ] } }, { "Permission (example: carsharing.vip)": "", "Command to give": "share.mazda", "Image": "https://i.imgur.com/fAuuZIS.png", "Name": "Mazda", "Cost per minute": 10.0, "Car class": "Comfort", "Average Speed": "100", "Modular Car Settings": { "CodeLock": true, "KeyLock": false, "Engine Parts Tier": 2, "Fresh Water Amount": 0, "Fuel Amount": 140, "Modules": [ "vehicle.1mod.engine", "vehicle.1mod.cockpit.armored", "vehicle.1mod.cockpit.armored" ] } }, { "Permission (example: carsharing.vip)": "", "Command to give": "share.skoda", "Image": "https://i.imgur.com/u07yAdY.png", "Name": "Skoda", "Cost per minute": 10.0, "Car class": "Comfort", "Average Speed": "100", "Modular Car Settings": { "CodeLock": true, "KeyLock": false, "Engine Parts Tier": 2, "Fresh Water Amount": 0, "Fuel Amount": 140, "Modules": [ "vehicle.1mod.engine", "vehicle.1mod.cockpit.armored", "vehicle.1mod.cockpit.armored" ] } }, { "Permission (example: carsharing.vip)": "", "Command to give": "share.opel", "Image": "https://i.imgur.com/fEzJjIm.png", "Name": "Opel", "Cost per minute": 10.0, "Car class": "Comfort", "Average Speed": "100", "Modular Car Settings": { "CodeLock": true, "KeyLock": false, "Engine Parts Tier": 2, "Fresh Water Amount": 0, "Fuel Amount": 140, "Modules": [ "vehicle.1mod.engine", "vehicle.1mod.cockpit.armored", "vehicle.1mod.cockpit.armored" ] } } ], "Bots": { "8833355776": { "Car Classes (* - all)": [ "Comfort" ] }, "1317845641": { "Car Classes (* - all)": [ "Luxe", "Comfort" ] } } } VIDEO

Adds a new event to the server - zone capture. If you gather resources on the territory of the occupied zone, a commission is removed from you and falls into the "capture cupboard". Features: Markers on the map Spawn in crates/barrels Percentage setting with permissions Setting limits with permissions Bypass setting (for teammates, friends, clanmates, cupboard) Commands give.capturezone [target] [amount] - gives out a cupboard for capturing a zone Permissions capturezone.ignore - allows you not to pay resources for tax Video Config { "Work with Notify?": true, "Zone Radius": 40.0, "Permission (ex: capturezone.use)": "", "Item Settings": { "DisplayName": "Zone Сapture", "ShortName": "cupboard.tool", "SkinID": 2767790029 }, "Marker": { "Enabled": true, "Display Name": "Zone by {owner}", "Radius": 0.3, "Refresh Rate": 3.0, "Duration": 0, "Color 1": "#EA9999", "Color 2": "#A73636FF" }, "Drop Settings": { "Enabled": true, "Drop Settings": [ { "Prefab name": "assets/bundled/prefabs/radtown/crate_normal.prefab", "Min amount": 1, "Max amount": 1, "Chance": 50.0 }, { "Prefab name": "assets/bundled/prefabs/radtown/loot_barrel_2.prefab", "Min amount": 1, "Max amount": 1, "Chance": 5.0 }, { "Prefab name": "assets/bundled/prefabs/radtown/loot_barrel_1.prefab", "Min amount": 1, "Max amount": 1, "Chance": 5.0 } ] }, "Notification during mining in the occupied territory": { "Enabled": true, "Cooldown": 5.0 }, "Percent Settings": { "Default": 20.0, "Permissions": { "capturezone.vip": 25.0, "capturezone.deluxe": 30.0 } }, "Limits Settings": { "Enabled": true, "Default": 3, "Permissions": { "capturezone.vip": 5, "capturezone.deluxe": 7 } }, "Bypass Settings": { "Teammates (Rust in-game system)": true, "Friends": true, "Clanmates": true, "Authorized in the cupboard": true } }

The best plugin that allows you to skip the night on the server. In addition to instant night skipping, you can use night acceleration. You can turn on white nights (under the full moon). Your players will love it! Features: Beautiful interface Voting is automatic (at the specified time in the config, without a command) Easy customization (time settings, text, interface, colors, etc.) Speeding up the day Speeding up the night White Nights (Full Moon) Video: FAQ: Where can I ask questions/get help quickly? My Discord: Mevent#4546 How do I turn on the full moon? 1. Enable nights with a full moon in the config. "Night with a full moon": true, 2. Configure the dates of the full moon in the config (you can get them from https://www.timeanddate.com/moon/phases/usa/new-york?year=2024) "Full Moon Dates": [ "2024-01-25T00:00:00", "2024-02-24T00:00:00", "2024-03-25T00:00:00", "2024-04-23T00:00:00", "2024-05-23T00:00:00", "2024-06-21T00:00:00", "2024-07-21T00:00:00", "2024-08-19T00:00:00", "2024-09-17T00:00:00", "2024-10-17T00:00:00", "2024-11-15T00:00:00", "2024-12-15T00:00:00" ] Config { "Time Settings": { "Day Start": "06:00", "Night Start": "18:00", "Voting time": 60, "Voting start time (time to check)": "20:00", "Time until which hour the voting will take place (time to check)": "21:00", "Time after voting (to which the night passes)": "08:00", "Fast skip the night": true, "Length of the night (minutes)": 5.0, "Length of the FAST night (minutes)": 2.0, "Length of the day (minutes)": 45.0, "Night with a full moon": true, "Full Moon Dates": [ "2024-01-25T00:00:00", "2024-02-24T00:00:00", "2024-03-25T00:00:00", "2024-04-23T00:00:00", "2024-05-23T00:00:00", "2024-06-21T00:00:00", "2024-07-21T00:00:00", "2024-08-19T00:00:00", "2024-09-17T00:00:00", "2024-10-17T00:00:00", "2024-11-15T00:00:00", "2024-12-15T00:00:00" ] }, "UI Settings": { "Destroy Time": 5.0, "Show Image?": true, "Image": "https://i.imgur.com/uNSAY42.png", "Image Width": 42.0, "Image Height": 33.0, "Image Up Indent": 16.0, "Left Indent": 212.0, "Bottom Indent": 16.0, "Width": 178.0, "Height for default version": 82.0, "Height for unfolded version": 184.0, "Background Color": { "HEX": "#F8EBE3", "Opacity (0 - 100)": 4.0 }, "Background Materal": "assets/content/ui/uibackgroundblur-ingamemenu.mat", "Voting Button": { "Width": 150.0, "Height": 30.0, "Bottom Indent": 15.0 }, "Progress Bar": { "Width": 150.0, "Height": 20.0, "Bottom Indent": 55.0 }, "Colors": { "Color 1": { "HEX": "#ABE04E", "Opacity (0 - 100)": 100.0 }, "Color 2": { "HEX": "#595651", "Opacity (0 - 100)": 75.0 }, "Color 3": { "HEX": "#74884A", "Opacity (0 - 100)": 95.0 }, "Color 4": { "HEX": "#FFFFFF", "Opacity (0 - 100)": 100.0 } } }, "Votes Settings": { "Number of votes": 5, "Use a percentage of the online?": true, "Percentage of the online": 30.0 } }

Adds a list of players to your server with convenient options for interacting with them Commands players (open interface) Permissions Permission to use: you can set permission in config, for example: "Permission (ex: playerlist.use)": "playerlist.use", playerlist.hide (hides a player from the player list) FAQ Q: Where can I see an example of a config? A: Config

An event for the Arctic Research Base monument with a plot to rescue both a scientist and a pilot that have been captured by the security group who has been ordered to capture and deal with the attempted sabotage on the Arctic Base Description Welcome to a frosty new adventure in the more recently added Arctic Research Base to so many of our islands! This monument will now have an event with a storyline requiring you and your friends to rescue the Pilot, and the Scientist from their captivity by the Arctic Base security service. You don't want to know what will happen to these two if you don't save them! Our new event begins with a notification (if enabled by default) for players to know that a sabotage is about to take place on the island. There is a plot to come collect biological samples from the burned corpse of one of the recently discovered NPCs, class: Sledge. The players will soon find out that the sabotage has failed and that two of our team have been taken captive by the Artic Research security team! Players will need to free them both from this no prisoners no hostages situation, and protect the scientist while he finishes his portion of the mission. Once the Scientist or Pilot are released, snowmobiles will arrive bringing NPCs, tasked simply with killing the Scientist so he will not be able to carry out his task of reverse engineering a way to continue to combat everything they throw at us! Once the Scientist has completed his task, and the Pilot has been released and has prepped the escape helicopter, their evacuation can take place. The will get into their minicopter and begin their departure. Before you leave and as thanks, the Pilot is going to open up a warehouse full of supplies for you! Once you reach this point in the event, there are several options with different amounts of loot within the stash. If you are able to protect the Scientist, and they are able to evacuate with the pilot, then we can better find things of value on comms with the team as they leave and the looting will be most efficient! Be ready, this minicopter is an actual piece of... well it's Rusty! Let the pilot have some extra time if needed to make sure it is running smoothly before they take off. Here and now the security team will send everything they have at you and your friends. Protect the group from the attacks! In the configuration for the plugin you can change timers, NPC settings and numbers, snowmobile and crate numbers, the Scientists health, and the loot tables! As always the configurations are extensive and the creativity is in your hands to customize this plugin to your liking. Can you and your friends help make sure this sabotage takes place, and these rebels make it off the island? Dependencies (optional, not required) True PVE PveMode GUI Announcements Notify Discord Messages AlphaLoot CustomLoot NTeleportation Economics Server Rewards IQEconomic Kits Chat commands (only for administrators) /abstart - start the event /abstop - end the event Console commands (RCON only) abstart - start the event abstop - end the event Plugin Config en - example of plugin configuration in English ru - example of plugin configuration in Russian Hooks void OnArcticBaseEventStart() – called when the event starts void OnArcticBaseEventEnd() – called when the event ends void OnArcticBaseEventWinner(ulong winnerId) – called at the end of the event, where the winnerId is the player who did more actions to complete the event My Discord: KpucTaJl#8923 Join the Mad Mappers Discord here! Check out more of my work here!

This plugin adds 2 new deployable turrets and IR-traps. Overview Anti-Aerial turret This turret can be accessed via computer station. It has several modes Automatic - shoots multiple homing rockets, which will follow the target Manual (single) - shoots a single rocket Manual (burst) - shoots multiple If the turret is in automatic mode it waits for target. To acquire target player needs to place the crosshair on it and wait some time, which is configured here -> ([AA Turret] Target acquiring time (seconds)). After that the turret will follow the target and player can shoot by pressing Middle Mouse Button. Manual modes just shoot regular rockets. Machine gun Turret This turret can be mounted by pressing E on any of its parts (such as pipes etc.). Players can just aim and shoot. Ammo type can be configured here -> [Machine Gun Turret] Ammo type (short prefab name, must be one of 5.56 Rifle ammo). IR-Traps IR-traps (or flares) are used as a counter-measure to the anti-aerial turret. They can be loaded in the fuel storage of minicopter or scrap heli and can be deployed by pressing E. Stack sizes, amount per use and cooldown are configurable. IR-Traps can also affect SAM sites, this option can be enabled here -> [IR Trap] Affects SAM Sites (true/false) Commands Chat Commands /aaturret - buy anti-aerial turret (requires mountableturrets.aaturret.give permission) /mgturret - buy machine gun turret (requires mountableturrets.machinegun.give permission) Admin Chat Commands Following commands require mountableturrets.admin permission to work. See "Permissions" chapter for more info. /mt command must be ran a monument you want to modify. Positions are saved relative to the monument and persist even after a wipe or a map change. /mt (requires mountableturrets.admin permission) /mt add aa - spawns anti-aerial turret on a monument /mt add mg - spawns machine gun turret on a monument /mt add comp - spawns computer station on a monument, which gets automatically linked to anti-aerial turrets /mt remove - removes turret/computer station from the monument /mt reset - clears all data for a monument Admin Console Commands giveaaturret <player name> - gives anti-aerial turret to specified player givemgturret <player name> - gives machine gun turret to specified player Permissions mountableturrets.admin - allows usage of giveaaturret, givemgturret and /mg commands mountableturrets.aaturret.give - allows players to buy AA turret using /aaturret mountableturrets.aaturret.free - allows players to get AA turret for free using /aaturret (give permission is still needed) mountableturrets.machinegun.give - allows players to buy machine gun turret using /mgturret mountableturrets.machinegun.free - allows players to get machine gun turret for free using /mgturret (give permission is still needed) Localization This plugin has built-in support for the following languages - English Russian Configuration Example of MountableTurrets.json (some parts are shortened) { "PVE Mode (true/false)": false, "[AA Turret] Price (set value to 0 to make it free, use ServerRewards as a key to use RP points)": { "Key": "scrap", "Value": 500 }, "[AA Turret] Item Skin ID (Workshop ID)": 2849176835, "[AA Turret] Item Name": "Anti-Aerial Turret", "[AA Turret] Cooldown between shots (seconds)": 10.0, "[AA Turret] Rocket fuse length (seconds)": 10.0, "[AA Turret] Rocket fuse length (meters)": 450.0, "[AA Turret] Entities that turret is able to lock on to (short prefab name)": [ "minicopter.entity", "scraptransporthelicopter", "hotairballoon" ], "[AA Turret] Target acquiring time (seconds)": 0.6, "[AA Turret] Rocket initial velocity (meters per second)": 30.0, "[AA Turret] Interval between shots in Burst mode (seconds)": 0.4, "[AA Turret] Rocket explosion radius (meters)": 5.0, "[AA Turret] Movement Speed Fast": 3.7, "[AA Turret] Movement Speed Normal": 2.0, "[AA Turret] Movement Speed Slow": 1.0, "[Machine Gun Turret] Price (set value to 0 to make it free, use ServerRewards as a key to use RP points)": { "Key": "ServerRewards", "Value": 250 }, "[Machine Gun Turret] Item Skin ID (Workshop ID)": 2849176974, "[Machine Gun Turret] Item Name": "Machine Gun Turret", "[Machine Gun Turret] Ammo type (short prefab name, must be one of 5.56 Rifle ammo)": "ammo.rifle", "[IR Trap] Stack size": 12, "[IR Trap] Amount per use": 2, "[IR Trap] Cooldown (seconds)": 3.0, "[IR Trap] Initial velocity (meters per seconds)": 20.0, "[IR Trap] Fuse length (seconds)": 10.0, "[IR Trap] Affects SAM Sites (true/false)": true, "[IR Trap] SAM Site blind time (seconds)": 5.0, "[IR Trap] Show IR-Trap hint UI (true/false)": true, "[IR Trap] Deploy positions": { "minicopter.entity": [ { <..> } <..> ] }, "[Misc] Spawn positions on other entities (full prefab name)": { "assets/content/vehicles/modularcar/module_entities/2module_flatbed.prefab": [ { "Type": "MachinegunTurret", "Position": { <..> }, "Rotation": { <..> } } ], "assets/content/vehicles/train/trainwagonb.entity.prefab": [ <..> }, "[Misc] UI Images (leave names intact)": { <...> } } API BaseEntity SpawnAATurret(Vector3 position, Quaternion rotation) // spawns anti-aerial turret BaseEntity SpawnMachinegunTurret(Vector3 position, Quaternion rotation) // spawns machinegun turret void DestroyTurret(BaseEntity turret) // destroys the turret Credits Thanks to Vitek & Nikitos for helping me with this plugin!

In a tense multiplayer event, players are thrust into a violent dispute between two warring gangs, witnessing a high-speed chase and explosive confrontation at Oxum's Gas Station, and then choosing sides or taking all the spoils for themselves, while customization options offer control over NPC settings, loot rooms, and crate contents Description The event begins with a message in chat that there has been a dispute between to warring gangs. One gang has taken members from their rivals hostage. A car chase ensues chase where the rival gang is coming to save or avenge their own! The chase comes to an explosive end at Oxum's Gas Station when the car being pursued crashes into the gas pumps! This is the beginning of the event for your players. Both gangs jump out of their vehicles and a shootout immediately ensues! When a player decides to approach, they will have a few choices. Will they take up arms with the ruthless gang willing to do anything? Will they stand beside the more honorable outlaws? Or will they simply kill both gangs and take all of the loot? The choice, is theirs! If the player decides to kill the first gang, the second gang will give the player access to their loot room, a bunker inside the basement of the auto repair shop, as a sign of gratitude. If the player decides to kill the second gang, then the first gang will give access to their hidden stash in the restroom inside the station, to show their appreciation. If the player decides to just wipe both gangs out, well then they deserve all of the loot! And regardless of what team the player decides to destroy, the chasing vehicle is always left unattended at the end of the event. The player can grab this as a thank you for cleaning up the servers streets! It's a junker but you can take it for parts, drive to Junkyard to scrap it, or just use it to get home quick and take the parts you want from it. The configuration file has many customization options, including NPC settings, their numbers, and you can fully customize the loot rooms, the crates and their loot for the event. Dependencies (optional, not required) True PVE PveMode GUI Announcements Notify Discord Messages AlphaLoot CustomLoot NTeleportation Economics Server Rewards IQEconomic Kits Chat commands (only for administrators) /gsstart - start the event /gsstop - end the event Console commands (RCON only) gsstart - start the event gsstop - end the event Plugin Config en - example of plugin configuration in English ru - example of plugin configuration in Russian Hooks void OnGasStationEventStart() – called when the event starts void OnGasStationEventEnd() – called when the event ends void OnGasStationEventWinner(ulong winnerId) – called at the end of the event, where the winnerId is the player who did more actions to complete the event My Discord: KpucTaJl#8923 Join the Mad Mappers Discord here! Check out more of my work here!

This plugin adds to the game a variety of NPC bosses with different abilities and a very adaptable configuration Description Using this plugin you can add NPC bosses to any point on the map. You can set up any ability with the plugin configuration. If it is necessary, you can add multiple abilities to one boss. Abilities are divided into two categories, ones take place in a certain radius from the NPC, and others are triggered by damaging from an NPC. The map also displays the location of the actual bosses (their name and amount of health). You can give any clothes and weapons for NPCs using the configuration. Custom Map Maps that have a configuration for the appearance of boss on their custom monuments You can also download all these files for all maps here Dark Ages Blue Tears All files for custom maps are stored in the folder oxide/data/BossMonster/CustomMap. You don't have to delete files from there, the plugin will understand by itself which map is currently installed on the server and will download only the necessary file if there is one in this folder. The plugin will tell you about this process in the console during the plugin loading. It will write in the console what file works on the current map, and what ones don’t work If you want to create a custom place for the boss to appear on your custom map or on a map that is not in this list, you have to create the ID of this custom map. After that you need to place an item such as a RAND Switch on your map. It must be placed randomly, where it will not be visible to other players. You will get the identifier, if you add up the three coordinates of the position of this object from RustEdit (x, y and z) and write the resulting value in the parameter of your file (an example file can be taken from ready-made files) - ID As an example, let's take the coordinates (26.896, -456.158, 527.258), then our identifier is 26.896 - 456.158 + 527.258 = 97.996 Then you need to indicate a list of bosses that will appear on your map. You need to copy the configuration data block for each boss. In the database parameters you will specify the name of the boss and a list of positions where it can appear Dependencies (optional, not required) GUI Announcements Notify Discord Messages AlphaLoot CustomLoot Economics Server Rewards IQEconomic PveMode Chat commands (only for administrators) /WorldPos - displays the actual player’s position on the map /SavePos <name> - saves a new position to the configuration file for the boss with the name - name, relative to the nearest monument /SpawnBoss <name> - spawn of the boss with the name - name in the coordinates of the administrator Console commands (RCON only) SpawnBoss <name> – spawn of the boss with the name – name KillBoss <name> – kill all bosses with the name – name Plugin Config en - example of plugin configuration in English ru - example of plugin configuration in Russian Boss Config en - example of plugin configuration in English ru - example of plugin configuration in Russian Custom Map Config en - example of plugin configuration in English ru - example of plugin configuration in Russian Hooks void OnBossSpawn(ScientistNPC boss) - сalled when a boss appears on the map void OnBossKilled(ScientistNPC boss, BasePlayer attacker) - сalled when a player kills a boss API ScientistNPC SpawnBoss(string name, Vector3 pos) - spawns a boss named name in position pos void DestroyBoss(ScientistNPC boss) - destroys the boss My Discord: KpucTaJl#8923 Join the Mad Mappers Discord here! Check out more of my work here!

Take your players to new heights in the game of Rust, and get a few laughs watching people try to fly one for the first time! Introducing Jetpack! A plugin that allows your players to soar around like never before in the game of Rust. Grab this plugin and give your players something to talk about! Many functions have already been implemented like the ability to shoot while piloting a jetpack, and the plugin will continue to expand and grow with the community. You'll find the configuration covers almost anything you can think of, and you'll see a breakdown of the configuration file in the description below. By default you can simply press the middle mouse wheel to equip and remove the jetpack quickly, you can't run around once you've equipped it. You can customize loot crates the jetpack might appear in, and all of the stats from thrust to rotation and all of the other controls. Be sure to check the permission section and feel free to use the command creatively to give jetpacks as an award for completing other tasks on your server using the commands provided. Make sure you have some lowgrade handy, let's take to the skies! Сontrols Space bar - thrust W/S keys - pitch axis A/D keys - yaw axis Chat commands (check config for permissions) /jet - toggle jetpack on & off /givejetpack - give a jetpack to yourself Console commands (admin only) givejetpack - give a jetpack to yourself givejetpack SteamID - give a jetpack to player using their SteamID Plugin config en – example of plugin configuration in English ru – example of plugin configuration in Russian Check out the rest of my work: Adem's Codefling Library You can reach out to me in Discord: Adem's Discord Profile Thanks to Jbird for writing, translation, & support: Jbird's Discord Profile Join the Mad Mappers Discord!

Allow visitors of your server to make use of the premium building skins without having to own them. Compact and minimalistic UI. Fully UI Controlled. ( no commands required ) Only visible when the player has a hammer in their hands. When the UI is open, Hit a toolbelt hotkey so you can instantly swap to a weapon when being attacked. Create custom themes and let players choose the one they prefer. Apply the building skin to a single block or to all blocks of the same grade in the building. Optional keypress check to apply skins, so that by default the hammer retains its normal functionality. Optional background blur. Previews Toolbar will only be visible once the hammer has been selected, So its not cluttering the screen when its not required to be. Selected skin will be colored to make it stand out while the unselected skins are greyed out. Automatic adding of tabs when a skin is colorable to keep things clean and minimalistc. Create your own custom themes or modify existing ones and let players select themselves which one they prefer. Permissions buildingskinapplier.use | Allow players to make use of the plugin. buildingskinapplier.on_upgrade | Update the skin when a part of the structure gets upgraded. buildingskinapplier.hammer_apply | Update skin on hammer hit. buildingskinapplier.hammer_contagious | Update skin on hammer hit for all objects of the same grade.

Defend your home.. well.. defend what's left of it! Welcome to an epic new event where the players will defend their bases against waves of Frankenraiders! They will use any weapons they have available to try to raid your base. Some will come with whatever they can swing at you and your base, some will just try to defend their kin, some have found some heavy weaponry too! I think that one has a rocket launcher?! Description To launch the event first you must find a flare bright enough to attract their attention. You'll be able to find flares bright enough to attract an Easy Frankenraid in Bradley, Elite, Military, and Supply crates. When you've found a flare just toss it on or near the base within Tool Cupboard range. Once you successfully defend an Easy Frankenraiding party, you will be rewarded with a flare bright enough for a Medium party. Then upon defending successfully against a Medium raid, well if you really want to risk your wipe being wiped by a full Frankenraider party, then you will have earned a flare bright enough to attract a Hard Frankenraid! When you complete any difficulty level and are able to defend your base, a chinook will be sent to your location with rewards for your service to the island in clearing out the threat! If your base is destroyed, the event ends, chat notifications are sent, and there you stand in shame. Hopefully you're on a low pop server and not too many people noticed. It's okay champ, happens to the best of us some days! Just keep an eye on the in game UI like the timer and wave information to give yourself the best shot at keeping your base standing! There are various ways to configure this plugin to customize it for your server, for any level and number of players. The creativity is in your hands with the configuration file as well as your communities wants or needs. The loot table, the flare spawns, the different enemy types and their setups, everything is there for you to customize this if you so choose. Dependencies (optional, not required) True PVE GUI Announcements Notify AlphaLoot CustomLoot Base Repair Chat commands /defstop - in game command to end event in your current Tool Cupboard range (be near the event you are trying to end) - only for administrators! /checkfoundations - checks all the foundations of the house for the event (it is necessary to be inside the Cupboard area of the house) ⊘ - you or your friends are not the owner of the foundation ⊝ - the foundation does not match in height/depth ⊛ - the foundation does not match the topology (prohibited topologies: Cliff, Cliffside, Decor, Building, Monument, Clutter, Mountain) ◉ - the foundation is located within a radius of 40 meters from the custom monument Console commands (RCON only) giveflare {skinid} {steamid} - Console command to give a custom flare with a Steam Workshop SkinID ({skinid}) to a player using their SteamID ({steamid}) Plugin Config en - example of plugin configuration in English ru - example of plugin configuration in Russian My Discord: KpucTaJl#8923 Join the Mad Mappers Discord here! Check out more of my work here! Creator of the default configuration – jtedal Help in creating a plugin description – Jbird

A new event includes a lot of game mechanics Description The event starts with a warning in the chat: a submarine will soon be passed near the island. A submarine will appear on the water when the time is up. There are 4 floors in the submarine. 2 floors are over the water and 2 floors are under the water. It is possible to get into the submarine on absolutely any transport. There are 4 outside entrances, 4 underwater entrances, and 2 submarine entrances (added in the Underwater Update). There are about 50 NPCs outside the boat and two upper floors. There are about 120 crates of items, rooms with blue and red doors, locked crates, recyclers, workbenches in the submarine (it is possible to set up in the configuration). There are also 4 cameras on the submarine that you can connect to (Submarine1, Submarine2, Submarine3, Submarine4). The number and location of all NPCs and crates can be changed in the plugin configuration. It is also possible to change the dropdown items in them. It is necessary to blow up the doors on the submarine with explosives to get to the crates (it is possible to set up the amount of damage to the doors in the configuration). When an event appears, a marker will display on the map (configurable in the configuration file). It is possible to set up in the configuration the PVP zone for those who use the TruePVE plugin. A timer with a countdown to the Event end and the number of crates and NPCs will display for all players in the Event zone. The conditions for the completing event are the end of the timer or the end of the loot crates. The submarine will disappear at the end of the event. It is possible to set up an automatic event appear on the map. All timers can be set up in the configuration. It is possible to lower the FPS on the server due to the large number of entities during the submarine appearance or the end of the event! Dependencies Required NpcSpawn Dependencies (optional, not required) True PVE PveMode GUI Announcements Notify Discord Messages AlphaLoot CustomLoot NTeleportation Economics Server Rewards IQEconomic Kits Chat commands (only for administrators) /waterstart - start the event /waterstop - end the event /waterpos - determining the position and rotation coordinates for changing the location of NPCs and crates.It should write in the configuration (Attention! The event must be started, the current position of the administrator in relation to the submarine is read) Console commands (RCON only) waterstart - start the event waterstop - end the event Plugin Config en - example of plugin configuration in English ru - example of plugin configuration in Russian Hooks void OnWaterEventStart(HashSet<BaseEntity> entities, Vector3 position, float radius) – called when the event starts void OnWaterEventEnd() – called when the event ends void OnWaterEventWinner(ulong winnerId) – called at the end of the event, where the winnerId is the player who did more actions to complete the event My Discord: KpucTaJl#8923 Join the Mad Mappers Discord here! Check out more of my work here! The submarine is designed by Jtedal

Features Allows players to store items in portable bags Allows limiting the number of bags players can use at once Allows placing bags into storage containers, with limits Allows placing bags inside other bags, with limits Allows restricting which items can go inside bags Allows players to upgrade bags linearly Allows using Economics and Server Rewards for purchasing bag upgrades Allows players to recycle bags Allows items to be pulled into bags automatically Allows unlimited types of bags to be defined, each with different appearance, capacity and rules Allows players to open and switch bags quickly via a UI Allows players to create custom key binds to open and close bags Allows creating bags that are preloaded with items from Kits Allows bags to be placed in wearable slots, including the backpack slot Allows a visual backpack to be displayed while the player is wearing a bag Quick start Give yourself a bag Grant the bagofholding.givebag permission to an administrator role. For example, run the command o.grant group admin bagofholding.givebag. Give yourself a bag with the command boh.givebag <player> generic.small (replace <player> with your in-game name). By default, this bag has 18 slots, and can hold any type of item, but it cannot hold other bags (unless those other bags are empty). Click on the bag in your inventory and click the "Open Bag" button. This will display the bag container in the loot panel, allowing you to place items into the bag. Upgrade the bag Grant the bagofholding.upgrade.generic.small permission to an appropriate role. For example, run the command o.grant group default bagofholding.upgrade.generic.small. Open the bag. Click the "Upgrade" button. Click the "Purchase upgrade" button (costs 300 scrap by default). This will upgrade the bag capacity to 24 slots, and it will change the bag's appearance. Note: Every bag has a separate permission which determines whether players can upgrade that specific type of bag. If you intend to allow players to upgrade bags, you will have to grant quite a few different permissions. We suggest using a permissions manager UI plugin for this. Enable gather mode Set Gather mode -> Enabled to true in the config. Reload the plugin. Open the bag. Click the "Gather: Off" button so that it changes to "Gather: On". This will show a flame icon on the bag, indicating that it is in gather mode. Drop and pick up an item. You will see the item get pulled into the bag automatically. Add bags to loot tables Note: If you are using a dedicated loot plugin to add bags to loot tables, this built-in feature might not work. For best results, configure your dedicated loot plugin to spawn bags instead. Set Loot spawns -> Enabled to true in the config. For testing, set the spawn chance for one type of bag to 100.0 for the assets/bundled/prefabs/radtown/crate_normal.prefab container prefab. Reload the plugin. Spawn some containers to confirm that they can spawn bags in them. For example, run the command spawn crate_normal in the client F1 console while aiming at the ground, and look for a bag in the container. If none of the loot containers are spawning with a bag in them, then you are probably using a loot plugin which is conflicting, in which case you may need to configure loot spawns in your dedicated loot plugin. Once you have confirmed that this feature is working on your server, configure the spawn chances to your liking. Once you have configured the spawn chances to your liking, you can use the bagofholding.spawnloot command to spawn bags into existing loot containers according to the config. You can also remove all bags from loot containers using the bagofholding.clearloot command if you accidentally added too many. Realistic backpacks If you want to allow backpacks to be usable only in the backpack slot, along with a 3D visual backpack model, proceed with the following steps. Set Wearable bags -> Allow wearing bags in the backpack slot to true in the config. This allows players to equip a bag in the backpack slot. Set Visual backpack -> Display while a bag is worn in the backpack slot to true in the config. This causes the visual backpack model to appear when the player is wearing a bag in the backpack slot. Set Player wearable bag limits -> Enabled to true in the config. This causes the player wearable inventory to have different bag limits than the rest of the player inventory. Set Player wearable bag limits -> Default limits -> Max total bags to 1 in the config. This allows players to wear at most one non-empty bag. Technically, this number could be set higher and it wouldn't matter, as long as you don't permit bags to be worn in other slots, since there is only one backpack slot. Set Player bag limits -> Default limits -> Max total bags to 0 in the config. This prevents players from placing non-empty bags in their main/belt inventory. Reload the plugin. Change bag theme By default, bags use fantasy-themed skins. Alternatively, you may choose leather-themed or tactical-themed skins. You may also choose between colored chevron icons (default) and colored circle icons which are larger and therefore easier to see. Bag skins can be directly changed in the config, but for first time users, this plugin provides multiple commands to help you edit the config in bulk. To change the bag theme, run the command boh.settheme <theme>. For example, boh.settheme tactical_chevrons. This command will update the skin IDs in the config and update existing bags in your server to the appropriate theme. Available themes are: fantasy_chevrons, fantasy_circles,leather_chevrons,leather_circles, tactical_chevrons, tactical_circles. This command works best when using a freshly generated config. If you have significantly altered the config (i.e., changed the number of bags per category), then you may have to use a lower level command such as boh.setskins, or manually update the config. In addition to the skins assigned to the preset themes which include 6 variations (no icon, light blue, green, yellow, orange, blue), there are 5 additional colors available (gray, white, black, red, pink). See the "Alternative bag skins" section for a list of all 400+ skins. Additionally, you can create your own skins and add them to the configuration. Some servers provide multiple themes at once, allowing players to use whichever style they prefer. To do this, you first need to define the alternative themes in the config. To add alternative themes, you can run the command boh.addtheme <theme>. Note: The fantasy_chevrons, leather_chevrons and tactical_chevrons themes are already included in the default config (as of v1.9.0), so you don't need to run this command if those are the only themes you care about, unless you are using a config from a prior version. Once the config is updated, you will then have to provide the alternative skins to your players somehow, such as via kits, vending machines, shop plugins, crafting plugins, loot plugins, etc. The boh.givebag command has an optional parameter to designate which skin to apply, which some servers use for integration with custom shops. In addition to changing bag skins, you may also want to change the skin displayed on the belt icon via UI settings -> Belt button -> Display skin ID in the configuration. For reference, the default generic.small bag skins are 2824115881 (fantasy), 2831029422 (leather), and 2828573095 (tactical). How it works How players obtain bags Bags are simply skinned large halloween loot bags (short name: halloween.lootbag.large, item ID: 479292118). Any plugin that can create skinned items can be used to make bags available on your server. For example, bags can be distributed via kits, vending machines (via Custom Vending Setup), shop plugins, crafting plugins, loot plugins (e.g., Alpha Loot), and more. The plugin also has native support for adding bags to loot containers, and provides the command boh.givebag <player> <profile> <amount> for use by admins or plugins. How players open bags Players can open bags multiple ways. "Open Bag" button: When a player clicks on a bag item, they will see the "Open Bag" button appear next to the "Drop" button. Clicking the "Open Bag" button will open the bag container on the right side of the inventory, the same as opening a storage container. Extra belt button: Players with a bag in their inventory will see a bag button next to their belt. Clicking that button will open the first bag in their inventory (via the bag.open command). Requires "UI settings" -> "Belt button" -> "Enabled": true in the config. This is enabled by default. Subsequent presses of that button will cycle through the remaining bags in the player's inventory. Custom key binds: Players may bind commands such as bag.open, bag.next, and bag.prev to keys for quick access. See the "Commands" section for a complete list of available commands and how they function. Tip: Players can also move items into a bag without even opening it, by simply dragging and dropping items directly onto the bag. Bag limits As a balancing mechanism, you can limit how many bags a given player or container can use at once. Empty bags can be placed almost anywhere, but bags with contents will count toward a limit. When that limit is reached, empty bags in the same container will become locked and unable to receive items. The default configuration of the plugin allows players to use up to 3 bags at a time in their inventory, with 0 bags in their backpack (Backpacks plugin on uMod), and 0 bags in storage containers. To configure bag limits for player inventories, see Player bag limits in the config. To configure bag limits for Backpacks, see Backpack bag limits in the config. To configure bag limits for storage containers, see Default container bag limits and Container bag limits by prefab in the config. If desired, you can assign bag limits according to player permission. Bag upgrades Each bag profile may define an upgrade target, dictating which bag profile it can be upgraded to. While a player is looting a bag, if they have permission to upgrade that bag, they will see an "Upgrade" button. Clicking that button will display the cost, as well as what the bag will be upgraded to, allowing the player to confirm the purchase if they have sufficient funds. Tip: One immersive upgrade technique is to set the upgrade cost to another instance of the same bag, to make it so players have to combine bags together to produce a better bag. Bag recycling Each bag profile may define a set of ingredients that it will recycle into when processed by a recycler. Each bag can recycle into as many ingredients as you want, each with an optional skin ID. Tip: One immersive recycling technique is to configure larger bags to recycle into smaller bags (possibly multiple). This technique can be used to allow players to effectively reverse bag upgrades, as well as to split larger bags into smaller bags that the player can then upgrade independently. Wearable bags To free up main inventory space, you can enable players to carry bags in their wearable inventory slots. To enable, see Wearable bags in the config. Note: Wearing a bag will only display the visual backpack if the visual backpack is also enabled. Visual backpack To increase immersion, you can display a visual backpack while a player is wearing a bag. To enable, see Visual backpack in the config. Gather mode To optimize player looting, players can enable gather mode for each bag. While gather mode is enabled, any item that gets added to the bag's parent container will automatically be moved into the bag if possible. For example, if you have a Food & Medical bag in your inventory, and that bag is in gather mode, picking up a food or medical item (or moving such an item from a container to your inventory) will automatically move that item into the bag if there is space. Notes: Gather mode can be enabled by setting Gather mode -> Enabled to true in the config Bags which have gather mode enabled will display a flame icon to easily identify them Throwing a bag onto the ground will automatically toggle off gather mode Gather mode only moves newly added item stacks, so existing item stacks will be ignored, even when replenished When multiple bags are in gather mode, the plugin will attempt to add items to bags according to their order in the container When nesting bags and enabling gather mode at multiple levels, new items will recursively be moved to child bags until they cannot be moved further Kit bags A kit bag is a type of bag that only allows players to remove items from the bag, but not add items. Kit bags are intended to be used as a mechanism to give players multiple items at once, without requiring that the player initially have the inventory space to hold all the items, since the player only needs to be able to hold the bag itself. Also, for convenience, once a kit bag has been emptied, the bag will automatically delete itself since it is no longer useful at that point (since players cannot place items in it). How to redeem a kit as a bag: If you have already created a kit via the Rust Kits plugin on uMod, you can give that kit to a player as a bag. That means the player will receive a bag item that is filled with the contents of that kit. To give a player a kit as a bag, simply run the command boh.givekitbag <player> kitbag.red.locked <kit>, where <player> should be replaced with a player name or steam ID, and <kit> should be replaced with the name of the kit. You may replace kitbag.red.locked with the name of a different locked kit bag if you want. Note: If running this command as a player (as opposed to in the server console or via another plugin), ensure you first have the bagofholding.givekitbag permission (caution: only grant that permission to trusted administrators). Tip: If you want to allow players to store items in a bag that is redeemed this way, then simply use a bag profile which has the "Allow player item input" config option set to true. How to add a kit bag to a kit: The Rust Kits plugin on uMod supports bags with items in them. If you want to allow players to redeem kits that contain bags with items in them, simply create a bag, add the items you want, then create a kit from your inventory. Note: Players will not be able to see the contents of the bag from the Kits UI, so it will be a mystery to the player until they have redeemed the kit, though the Kits plugin might be updated in the future to allow inspecting bag contents. If you want to add a bag to a kit, but don't want to allow players to use the bag as storage, follow the below steps create a kit bag. Give yourself an unlocked kit bag with the command boh.givebag <player> kitbag.red.unlocked, where <player> should be replaced with your user name or steam ID. Place items in the bag. Ensure you have the bagofholding.upgrade.kitbag.red.unlocked permission. Note: If you gave yourself a different color bag, the permission you must grant will be different. Caution: Only grant that permission to administrators who will be creating kits. Use the "Upgrade" feature to transform the bag into a kitbag.red.locked bag, which makes it so players can no longer add items to the bag. Use the Kits plugin to create or update the kit from your inventory. If you want to edit the bag contents, but don't want to do it from scratch, follow the below steps. Redeem the kit. Ensure you have the bagofholding.upgrade.kitbag.red.locked permission. Note: If this is a different color bag, the permission you must grant will be different. Caution: Only grant that permission to administrators who will be creating kits. Use the "Upgrade" feature to transform the bag into a kitbag.red.unlocked bag. Update the items in the bag. Use the "Upgrade" feature to transform the bag back into a kitbag.red.locked bag, which makes it so players can no longer add items to the bag. Use the Kits plugin to update the kit from your inventory. Permissions Admin permissions bagofholding.manageloot -- Allows running the commands boh.spawnloot and boh.clearloot. bagofholding.stats -- Allows running the command boh.stats. bagofholding.listbags -- Allows running the command boh.listbags. bagofholding.listcontainers -- Allows running the command boh.listcontainers. bagofholding.config -- Allows running the commands boh.setskins, boh.addskins, boh.settheme and boh.addtheme. bagofholding.givebag -- Allows running the command boh.givebag <player> <bag profile> <amount>. bagofholding.givekitbag -- Allows running the command boh.givekitbag <player> <bag profile> <kit name>. Limit permissions Depending on how you have configured the plugin, there will be additional permissions following the pattern bagofholding.limit.<type>.<suffix>, one for each limit permission profile. The plugin comes with the following limit profiles by default. bagofholding.limit.player.unlimited -- Allows the player to store unlimited bags in their inventory. bagofholding.limit.wearable.unlimited -- Allows the player to wear unlimited bags. This permission, and other bagofholding.limit.wearable.* permissions won't exist unless you enable Player wearable bag limits in the config. Otherwise, the wearable container will share bag limits with the rest of the player inventory. bagofholding.limit.backpack.unlimited -- Allows the player to store unlimited bags in their backpack (Backpacks plugin on uMod). bagofholding.limit.container.unlimited -- Allows the player to store unlimited bags in storage containers that they deploy. You can define additional limit profiles in the Player bag limits, Player wearable bag limits, Backpack bag limits, Default container bag limits and Container bag limits by prefab sections of the config. Note: When adding container bag limits by prefab, the permission will look like bagofholding.limit.container.<short_prefab_name>.<suffix>. Upgrade permissions Each bag profile that is configured with a valid upgrade target will generate a permission following the pattern bagofholding.upgrade.<profile>. Granting that permission allows players to upgrade that type of bag. For example, the bagofholding.upgrade.generic.small permission allows players to upgrade generic.small bags to generic.medium bags. We suggest using a permissions manager UI plugin to discover and grant bag upgrade permissions. Commands This plugin provides both chat and console commands using the same syntax. When using a command in chat, prefix it with a forward slash: /. Admin / server commands boh.spawnloot -- Spawns loot in loot containers throughout the map. Intended for first-time setup, since enabling loot spawns in the config will only add bags to loot containers that spawn while the plugin is loaded. boh.clearloot -- Removes bags from all loot containers. Intended for first-time setup in conjunction with the boh.spawnloot command. boh.stats -- Prints an overview of how many bags are present on the server. Note: Some bags may not show up in the results if another plugin has deleted them and backed up their data on disk (for example, bags inside player Backpacks if the player is not connected or has not opened their Backpack during this play session). boh.listbags <filter> -- Prints a table view in console, showing all of the bag profiles defined in the config, matching the keyword filter if provided. Requires the bagofholding.listbags permission. boh.listcontainers -- Prints all container prefabs in the game. Requires the bagofholding.listcontainers permission. boh.setskins <category> <skin1> <skin2> <skin3> <skin4> <skin5> <skin6> <skin7> -- Updates the primary skin of all bag profiles in the specified category. The exact number of skins you supply must match the number of bags in the specified category. For example, if there are 7 bag profiles in the generic category (one for each size), then you can use this command with 7 distinct skins to update the config for all of those bag profiles at once. The first bag profile will be given the first skin, the second bag profile will be given the second skin, and so on. In addition to updating the config for you, this will change all the currently known bags on the server, which have the affected bag profiles, to use the specified skins, saving you the trouble of having to recreate the bags. This command will ensure that the specified skins are made the primary skins of the affected bag profiles. boh.addskins <category> <skin1> <skin2> <skin3> <skin4> <skin5> <skin6> <skin7> -- Adds the specified skins as secondary skins to all bag profiles in the specified category. The first bag profile will be given the first skin, the second profile will be given the second skin, and so on. Similar to the boh.setskins command, this will update the config, but will not update the skins of existing bags on your server. boh.settheme <theme> -- Updates the primary skin of the preset bag categories (bagofholding, generic, armor_clothing, food_medical, items_construction, resources_components, weapons_tools) to the specified theme. Valid themes: fantasy_chevrons, fantasy_circles,leather_chevrons,leather_circles, tactical_chevrons, tactical_circles. Note: If the config has significantly changed (i.e., if any of the preset bag categories no longer have exactly 7 bag profiles), this command will not work, but you can alternatively use boh.setskins or manually update the config. boh.addtheme -- Like boh.settheme, but instead of changing the primary skin of the affected bag profiles, this will only add the specified theme as secondary skins. boh.givebag <player> <bag profile> <amount> <skin index> -- Creates a stack of bags and gives it to the specified player. Requires the bagofholding.givebag permission. If the bag has multiple skins defined, you can specify which one via the skin-index argument. For example, boh.givebag Somebody generic.small 1 3 to give one bag with the 3rd skin applied. The amount and skin index parameters are optional, both defaulting to 1. boh.givekitbag <player> <bag profile> <kit name> -- Creates a bag, populates it with the specified kit (from the Kits plugin on uMod), then gives it to the specified player. Requires the bagofholding.givekitbag permission. Player commands bag.open -- Depending on the context, this command will either open the first unlocked bag in your inventory, open the next bag in your inventory, or close your inventory if no more bags are found. bag.next -- Like bag.open, but will continuously cycle bags rather than closing your inventory when no more bags are found. bag.prev -- Like bag.next, but will start at the end of your inventory, and will cycle bags in reverse order. Configuration The settings and options can be configured in the BagOfHolding file under the config directory. The use of an editor and validator is recommended to avoid formatting issues and syntax errors. General settings Wearable bags -- Determines whether players can place bags in their wearable inventory slots. Disabled by default. Enabling this will incur a very minor performance cost. Allow wearing bags in the backpack slot (true or false) -- Determines whether players can wear bags in the backpack/parachute slot. Default: false. Allow wearing bags in non-backpack slots (true or false) -- Determines whether players can wear bags in non-backpack slots. Default: false. Visual backpack -- Determines whether the visual backpack will be displayed on players while wearing a bag. Enabling this will incur a minor performance cost. Display while a bag is worn in the backpack slot (true or false) -- Determines whether the visual backpack will be enabled while the player is wearing a bag in their backpack slot. Default: false. You should set Wearable bags -> Allow wearing bags in the backpack slot to the same value that you set here. Display while a bag is worn in a non-backpack slot (true or false) -- Determines whether the visual backpack will be enabled while the player is wearing a bag in a non-backpack slot. Default: false. You should set Wearable bags -> Allow wearing bags in non-backpack slots to the same value that you set here. Gather mode Enabled (true or false) -- Determines whether players can toggle gather mode on bags. While gather mode is enabled for a given bag, any item that gets added to the bag's parent container will automatically be moved into the bag if possible. Default: false. Enable stack improvements (true or false) -- Determines whether the plugin will attempt to auto stack bags when dropping them onto each other in the player inventory (as long as the destination bag is not currently open). Default: true. Setting to false will improve performance. Note that dropping a bag with contents onto an empty bag will never stack them; the empty bag must be dropped onto the bag that has contents. Dropped bag item settings Dropped bag item settings -- Determines the behavior of dropped bag items. Enable dropped bag buoyancy (true or false) -- Determines whether dropped bag items will float in water. Default: true. Enable opening dropped bags while at bag limit (true or false) -- Determines whether attempting to pick up a bag will actually open the bag instead, if the player cannot carry the bag due to their current bag limits. Default: true. Auto equip dropped bags while at bag limit (true or false) -- Determines whether attempting to pick up a bag will attempt to equip it in a wearable slot instead, if the player cannot carry the bag in their main inventory due to their current bag limits. Default true. This feature only applies while bags are configured to be wearable. Minimum despawn time (seconds) -- Determines the minimum time (in seconds) before a dropped bag item will despawn. This option also affects the despawn time of dropped backpacks that contain bag items. Note: The despawn time of bags will also take into account the despawn time of items within them. Default: 1800 (30 minutes). UI settings UI settings Belt button -- Determines the display of the button next to the player's belt. By default, the button appears on the right side of the belt. The button will only appear if you have at least one bag in your inventory. Clicking the button will open the first bag in your inventory via the bag.open command. Enabled (true or false) -- Determines whether the belt button is displayed. Default: true. Only show while bags are worn (true or false) -- Determines whether bags must be worn in order to display the belt button. OffsetX -- Determines where the belt button is displayed, relative to the bottom center of the screen. Set to 185.0 to place the button on the right side of the belt. Set to -263.0 to place the button on the left side of the belt. Default: 185.0. Display skin ID -- Determines the skin ID displayed on the belt button. Default: 2824115881 (the fantasy style generic.small bag). Loot interface -- Determines the display of the loot panel while the player has a bag open. Enable back button (true or false) -- Determines whether a back button is displayed when the player is looting a bag that is inside another container. Clicking the back button will switch the loot interface to the bag's parent container. Default: true. Bag selector -- Determines the display of the bag selector. While looting a bag, the bag selector will display an icon for each lootable bag in the bag's parent container, allowing for 1-click access to other bags. The bag selector also displays a vertical progress bar to indicate how full each bag is. The bag selector automatically resizes depending on how many bags need to be displayed. The default settings allow a maximum of 10 bags to be displayed. Enabled (true or false) -- Determines whether the bag selector is displayed. Default: true. Max width -- Determines how much space the bag selector can use. By default, it can take up to 5 inventory slots worth of space, but that may cause the "LOOT" text to overlap the bag selector for players using non-English languages. If your players are seeing overlap, consider reducing this value. Default: 310.0. Min bag size -- Determines the minimum size (height and width) of each bag displayed in the bag selector. When many bags are displayed, each bag icon will be no smaller than this value. Default: 29.0. Max bag size -- Determines the maximum size (height and width) of each bag displayed in the bag selector. When few bags are displayed, each bag icon will be no larger than this value. Default: 58.0. Effects Effects Open effect -- Determines the effect played when a player opens a bag. Only the player that opens the bag will witness this effect, so it will not give away their location. Default: "assets/prefabs/deployable/small stash/effects/small-stash-deploy.prefab". Set to "" to disable the effect. Disabling effects will improve performance. Upgrade effect -- Determines the effect played when a player upgrades a bag. Only the player that upgrades the bag will witness this effect, so it will not give away their location. Default: "assets/prefabs/misc/halloween/lootbag/effects/silver_open.prefab". Set to "" to disable the effect. Disabling effects will improve performance. Loot spawns Loot spawns -- Determines which loot containers bags may spawn in. This feature is disabled by default. As an alternative to using this feature, you might want to use a dedicated loot plugin to spawn bags, by designating that the loot plugin should spawn a large halloween loot bag (short name: halloween.lootbag.large, item ID: 479292118) with an appropriate skin ID from the Bag profiles section of the config. Enabled (true or false) -- Determines whether this plugin will attempt to add bags to loot containers. Default: false. Bag spawn chance percent by prefab -- Determines the probability (0.0 to 100.0 percent) of bags spawning in loot containers, according to the prefab of the loot container. For each type of loot container, you may define the spawn chance for each bag profile. To see which container prefabs this can accept, run the command boh.listcontainers (requires the bagofholding.listcontainers permission). Bag limits Player bag limits -- Determines how many non-empty bags that players can hold in their inventory at once. This applies to the entire player inventory, including the wearable container, unless Player wearable bag limits is enabled, in which case limits for the wearable container is configured separately. Default limits -- These limits apply to all players, except those who have been granted a permission from Bag limits by permission. Max total bags -- See below. Max bags by category name -- See below. Bag limits by permission -- List of bag limits which override the defaults. Permission suffix -- Determines the permission generated, following the pattern bagofholding.limit.player.<suffix>. For example: bagofholding.limit.player.unlimited. You may define unlimited bag limit profiles, but at most one will be assigned to each player. Limit profiles toward the end of the list have highest priority. Max total bags -- See below. Max bags by category name -- See below. Player wearable bag limits -- Determines how many non-empty bags that players can wear. Enabled -- Determines whether wearable limits are separate from Player bag limits. While true, limits defined in this section apply to the wearable container, and limits defined in Player bag limits apply only to the rest of the player inventory. While false, limits defined in this section have no effect. Default limits -- These limits apply to all players, except those who have been granted a permission from Bag limits by permission. Max total bags -- See below. Max bags by category name -- See below. Bag limits by permission -- List of bag limits which override the defaults. Permission suffix -- Determines the permission generated, following the pattern bagofholding.limit.wearable.<suffix>. For example: bagofholding.limit.wearable.unlimited. You may define unlimited bag limit profiles, but at most one will be assigned to each player. Limit profiles toward the end of the list have highest priority. Max total bags -- See below. Max bags by category name -- See below. Vanilla backpack bag limits -- Determines how many non-empty bags that vanilla backpacks can hold (while equipped or while dropped on the ground). Enabled -- Determines whether vanilla backpack bag limits are determined by this section or by Default container bag limits -> Default limits. While true, limits defined in this section apply to vanilla backpacks. While false, limits defined in this section have no effect, and vanilla backpacks will follow the rules defined for default container limits. Default limits -- These limits apply to all backpacks. There is not currently a way to override this for players with permission. Max total bags -- See below. Max bags by category name -- See below. Backpack bag limits -- Determines how many non-empty bags that players can hold in their backpack at once (Backpacks plugin on uMod). Default limits -- These limits apply to all players, except those who have been granted a permission from Bag limits by permission. Max total bags -- See below. Max bags by category name -- See below. Bag limits by permission -- List of bag limits which override the defaults. Permission suffix -- Determines the permission generated, following the pattern bagofholding.limit.backpack.<suffix>. For example: bagofholding.limit.backpack.unlimited. You may define unlimited bag limit profiles, but at most one will be assigned to each player. Limit profiles toward the end of the list have highest priority. Max total bags -- See below. Max bags by category name -- See below. Default container bag limits -- Determines how many non-empty bags can be placed into storage containers. Can be overriden for specific container prefabs via Container bag limits by prefab. Default limits -- These limits apply to all storage containers, except those owned by players who have been granted a permission from Bag limits by permission. Max total bags -- See below. Max bags by category name -- See below. Bag limits by permission -- List of bag limits which override the defaults. Permission suffix -- Determines the permission generated, following the pattern bagofholding.limit.container.<suffix>. For example: bagofholding.limit.container.unlimited. You may define unlimited bag limit profiles, but at most one will be assigned to each player. Limit profiles toward the end of the list have highest priority. Max total bags -- See below. Max bags by category name -- See below. Container bag limits by prefab -- Determines how many non-empty bags can be placed into storage containers, by container prefab, superseding Default container bag limits. See below for an example. [full_prefab_path] -- For each prefab you want to define limits, you will need to define a new subsection with the full prefab path, then declare the bag limit definition under that section. Default limits -- These limits apply to all storage containers with this prefab, except for those owned by players who have been granted a permission from Bag limits by permission. Max total bags -- See below. Max bags by category name -- See below. Bag limits by permission -- List of bag limits which override the defaults for this prefab. Permission suffix -- Determines the permission generated, following the pattern bagofholding.limit.container.<short_prefab_name>.<suffix>. For example: bagofholding.limit.container.locker.deployed.unlimited. You may define unlimited bag limit profiles, but at most one will be assigned to each player. Limit profiles toward the end of the list have highest priority. Max total bags -- See below. Max bags by category name -- See below. Every bag limit profile has the following options. Max total bags -- Determines how many total non-empty bags (of any category) are allowed. Max bags by category name -- Determines how many non-empty bags of each category are allowed. This references the optional Category name property of each bag profile. For example, if you set this to { "resources_components": 2 }, players will be able to hold at most 2 Resources & Components bags. Example Container bag limits by prefab: "Container bag limits by prefab": { "assets/prefabs/deployable/locker/locker.deployed.prefab": { "Default limits": { "Max total bags": 0, "Max bags by category name": {} }, "Bag limits by permission": [ { "Permission suffix": "unlimited", "Max total bags": -1, "Max bags by category name": {} } ] } }, Bag content rulesets Bag content rulesets -- This section allows you to determine which items can be placed inside bags. It also allows you to define limits for bags inside bags. Each bag profile can refer to a content ruleset that you define in this section, to determine what is allowed in that type of bag. This design allows you to define a ruleset once, and reference it in many bag profiles. Name -- The name of the ruleset. Once you have defined this ruleset, you can assign it a specific bag profile by going to the Bag profiles section of the config and setting the Contents ruleset option to this ruleset name. Allowed item categories -- Determines which categories of items are allowed to be placed into bags that use this ruleset. Allowed values: All, Ammunition, Attire, Common, Component, Construction, Electrical, Favourite, Food, Fun, Items, Medical, Misc, Resources, Search, Tool, Traps, Weapon. Any item within allowed categories may be forcibly disallowed by specifying its short name in Disallowed item short names, or by specifying its skin ID in Disallowed skin IDs. Disallowed item categories -- Determines which categories of items are disallowed from being placed into bags that use this ruleset. This option is useful if you want to allow most categories, with explicit denial of specific categories. Note: For this option to work, you'll also need to set Allowed item categories to ["All"]. Any item disallowed this way can be forcibly allowed by specifying its short name in Allowed item short names, or by specifying its skin ID in Allowed skin IDs. Allowed item short names -- Determines which items are allowed to be placed into bags that use this ruleset, in addition to the categories specified in Allowed item categories. Any item allowed this way can be forcibly allowed by specifying its skin ID in Disallowed skin IDs. Disallowed item short names -- Determines which item short names are disallowed from being placed into bags that use this ruleset. Any item disallowed this way can be forcibly allowed if its skin ID is specified in Allowed skin IDs. Allowed skin IDs -- Determines which skin IDs are allowed to be placed into bags that use this ruleset. By default, all skin IDs are allowed, as long as the item is allowed via Allowed item categories or Allowed item short names. This option is useful for allowing specific skins of specific items that are not otherwise allowed. For example, if you want a specific bag to only be able to hold other bags (and no other items), simply set this option to the list of bag skin IDs, and leave all of the other options blank. Disallowed skin IDs -- Determines which skin IDs are disallowed from being placed into bags that use this ruleset. This option is useful for disallowing specific skins of specific items that are otherwise allowed via Allowed item categories or Allowed item short names. Bag limits -- Determines how many non-empty bags can fit inside this bag. Max total bags -- See the section on bag limits. Max bags by category name -- See the section on bag limits. Order of precedence: Disallowed skin IDs > Allowed skin IDs > Disallowed item short names > Allowed item short names > Disallowed item categories > Allowed item categories. Bag profiles Bag profiles -- This section defines every type of bag. For an item to function as a bag, it must be a large halloween loot bag (short name: halloween.lootbag.large, item ID: 479292118) with a skin ID from this section. Name -- The short name of the bag. This must be unique. The bag profile name is used by various features of the plugin, including bag limits, bag upgrades, upgrade permissions, loot spawns, the bagofholding.givebag command, developer hooks, and the developer API. Skin IDs -- Determines the skin IDs associated with this bag profile. Any halloween.lootbag.large item that has one of these skin IDs will be considered a bag controlled by this plugin and will use this profile. You can associate as many skin IDs per bag profile as you want. By default, most bag profiles will have three skins in the config, for fantasy, leather and tactical themes, in that order. Defining multiple skin IDs allows you to provide multiple themes of bags to players, letting them choose which they prefer, as long as you provide players with a means to get the alternative skins. The first skin ID is considered the primary skin ID, and will be used when creating a bag for loot spawns, when giving a bag via the boh.givebag command (unless the skin index parameter is supplied), and when other plugins create bags via API methods. When a bag is upgraded, if the target bag profile has multiple skin IDs defined, the new skin ID will be selected according to the order in the list of skin IDs. For example, if the bag's current profile lists three skin IDs, and the current skin is second, then the upgraded bag will use the second skin ID in the target profile. If there is no corresponding skin in the same position in the target profile (e.g., 3rd skin on current profile, but the target has only 2 skins), then the first skin will be selected. Capacity -- Determines how many container slots this bag will have. Maximum: 48. Display name -- Determines the display name of the bag item. This shows at the top of the screen when a bag item is selected in your inventory. Category name -- Determines the bag category. Other sections of the config will refer to this name to define bag limits. This should not be confused with item categories, which are used to define content rulesets. Contents ruleset -- Determines which items are allowed inside this bag. This must refer to the name of a ruleset defined in the Bag content rulesets section of the config. Allow player item input (true or false) -- Determines whether players can place items into this bag. Setting to false is useful if you want to provide a player with a bag full of items, as a sort of temporary container. This feature is intended primarily for "kit bags". Upgrade -- Determines which bag profile this bag can be upgraded to, as well as the items required to purchase the upgrade. To -- The name of the target bag profile. Cost -- The cost to purchase the upgrade. Item short name -- The short name of the currency item. Default: "scrap". Item skin ID -- The skin ID of the currency item. Set to 0 to accept any skin. Default: 0. Amount -- The amount of currency required to purchase the upgrade. Use Economics (true or false) -- Set to true to require Economics currency instead of item currency. Default: false. Use Server Rewards (true or false) -- Set to true to require Server Rewards currency instead of item currency. Default: false. Recyclable -- Determines whether the bag can be recycled, as well as which items it will recycle into. Enabled (true or false) -- Determines whether the bag can be recycled. Default: false. Setting to false for every bag will improve performance by disabling recycling hooks. Ingredients -- List of items that will be produced by recycling the bag. Item short name -- The short name of the ingredient item. Default: "scrap". Item skin ID -- The skin ID of the ingredient item. Default: 0. Amount -- The amount of the ingredient item to produce. Item display name -- The display name of the ingredient item. Localization The default messages are in the BagOfHolding file under the lang/en directory. To add support for another language, create a new language folder (e.g. de for German) if not already created, copy the default language file to the new folder and then customize the messages. Frequently asked questions (FAQ) Q: How do I configure this plugin with Alpha Loot? The built-in Loot spawns feature of this plugin is compatible with popular loot plugins such as Better Loot and Alpha Loot. Alpha Loot users also have the option of spawning bags directly via the Alpha Loot plugin. To do so, use the Alpha Loot Editor to add skinned large halloween loot bags to the loot table (short name: halloween.lootbag.large, item ID: 479292118). Tutorial: https://www.youtube.com/watch?v=54A77rQ0Ld8. Caution: Make sure that the bag skin IDs you configure to spawn via Alpha Loot are assigned to bag profiles in the Bag of Holding config. If you configure a particular skin ID in the loot table that does not correspond to a bag profile, then those bags will function as just normal halloween loot bags. Q: How do I make players spawn with bags? One way is via the Auto Kits feature of the Rust Kits plugin on uMod. Other plugins that allow you to manage default loadouts for players should also work, as long as they support skinned items. Q: Can bags be placed inside other bags? Yes, but by default, only the bagofholding bag profile can contain other bags, and it cannot contain other bagofholding bags. You can fine tune this behavior in the configuration. Q: Can this plugin replace Backpack plugins? Yes, for the majority of use cases. If you are using a Backpack plugin for the sole purpose of allowing players to carry more items (with backpacks dropping on death), then you can simply switch to using bags instead. The main difference is that Backpacks allow players to spawn with additional storage, which players cannot lose, whereas players must acquire bags to use additional storage, and players can lose or trade that storage capacity. If you are currently allowing players to keep their Backpack items on death, bags cannot replace that use case, but bags can enhance that use case since you can configure certain bags to be allowed in Backpacks to effectively increase the Backpack storage capacity. Q: Is this plugin compatible with Backpack plugins? Yes, this plugin has native support for the Backpacks plugin on uMod. By default, only empty bags can be placed inside Backpacks, but you can configure that behavior under the Backpack bag limits. Q: Can bags have more than 7 upgrade stages? Yes, you can have as many upgrade stages as you want. By default, each bag category has 7 stages (one for each row of capacity), but it's possible to have 48 bag stages per bag category (one for each slot of capacity). The simplest way to add more stages is to create additional bag profiles that reuse the existing skins but have different capacity. For example, you can define "Small Bag (13)" with 13 capacity and "Small Bag (14)" with 14 capacity, both with skin ID 2824115881. Q: How can I change bag icons? See the Default bags section below for instructions on changing the bag icons to other presets created by our development team. If you want to create your own bag icons, simply upload them to the Steam workshop as you would any Rust skin, then assign the corresponding workshop/skin ID to a bag profile in the Bag Profiles section of the config. Q: Can I configure bag upgrades to require multiple items? No. Currently, bag upgrades can only be configured to require a single type of item. Q: Where is this plugin's data file? This plugin doesn't use nor need a data file in its current design. This plugin utilizes a vanilla Rust capability to store items inside other items, similar to how attachments are placed inside weapons. Plugin compatibility / troubleshooting During initial development of this plugin, many plugin compatibility issues were identified and fixed. Some themes of compatibility issues were systematically eliminated, never to be seen again. However, some conflicts may remain undiscovered. If you encounter a new compatibility issue, please report it to the maintainers of both plugins so that we can work out a solution. This section also provides tips on how you can mitigate various plugin conflicts. Hook conflict with OnItemSplit The simplest way to mitigate this issue is by disabling stacking of the halloween.lootbag.large item. You can also avoid this issue by ensuring each bag profile uses a unique skin ID. Hook conflict with CanStackItem The simplest way to mitigate this issue is by disabling stacking of the halloween.lootbag.large item. Tips for maintainers of other plugins: Don't allow stacking when the item being moved is not empty Don't allow stacking two items whose containers have different capacity Hook conflict with CanCombineDroppedItem The simplest way to mitigate this issue is by disabling stacking of the halloween.lootbag.large item. Hook conflict with CanMoveItem This can happen in two possible situations: When quick-looting an item from a bag into your inventory. If this is when you see the conflict, you will have to contact us to troubleshoot further. When dropping a bag onto another bag. If this is when you see the conflict, the simplest way to mitigate this issue is by disabling stacking of the halloween.lootbag.large item. You can also mitigate this issue by setting Enable stack improvements to false in the config. Hook conflict with CanBeRecycled or OnItemRecycle The simplest way to mitigate this issue is by disabling recycling on all bag profiles. The belt icon overlaps with other plugin icons To mitigate this issue, you can either disable the belt icon or reposition it in the config. Opening a bag spawns loot There are two likely possibilities. The bag had a skin ID that is not configured in the plugin. One way this can happen is if you use another plugin to acquire bags, and the skin ID you configured in that plugin isn't assigned to any bag profiles in the Bag of Holding config. If this is the case, please reconfigure either plugin so that they refer to the same skin ID. You have a loot plugin which is using the OnItemAction hook to override the behavior of opening halloween.lootbag.large items. There is little that you can do to mitigate this. Please suggest to the maintainer of the loot plugin that they add a check to ignore halloween loot bags that are skinned. Opening a bag inside a special container just closes the container This probably means that the plugin that controls the special container immediately deleted the container when it was closed. In this case, the plugin that manages that container will need to implement changes to allow that container to persist after closed. Pressing the back button inside a bag just closes the bag This probably means that the bag has been placed inside a special container which the plugin doesn't know how to open. It could be due to a miss in this plugin, but more likely, that container is a special type of container controlled by another plugin (such as a Backpack or Bank). In this case, we will have to develop a solution to enable compatibility. Quick Sort UI overlaps bag selector UI The simplest way to mitigate this issue is by reducing the max bag size to 6 rows (36 slots). Alternatively, you can update the Quick Sort plugin's configuration to reposition or resize the UI. We are also planning to introduce an option to reposition the bag selector to the right side of the loot panel in a future update. Weapons/deployables placed in bags eventually become unusable This may happen if you are using an incompatible item cleaner or entity cleaner plugin. Most likely, the cleaner plugin doesn't know to account for situations where items are deeply nested. It should be easy for the cleaner plugin's maintainer to fix this issue. After attending an event, items inside bags are missing or changed This can happen if the plugin which manages the event temporarily replaces the player's items and restores the items when the player leaves the event. This issue usually manifests as items losing their skins and contents (e.g., weapons losing attachments, water jugs losing water). To resolve, the maintainer of the event plugin will need to update that plugin to recursively save items to infinite depth. If the developer needs help, they can look at the code of other plugins such as Backpacks, Kits, and Restore Upon Death. After placing a bag inside a special container, items inside the bag are missing or changed This may happen if the plugin which manages the special container tries to save the items in a custom way, such as via a data file. This issue usually manifests as items losing their skins and losing contents (e.g., weapons losing attachments, water jugs losing water). To resolve, the maintainer of the container plugin (e.g., Bank, Backpacks, Extra Pockets feature of Skill Tree) will need to update that plugin to recursively save items to infinite depth. If the developer needs help, they can look at the code of other plugins such as Backpacks, Kits, and Restore Upon Death. Default bags The default configuration provides many bag profiles, detailed below. See this workshop collection to find hundreds of bag skins created specifically for this plugin. Armor & Clothing Bags Name Skin ID Capacity Display Name Upgrades to Upgrade cost Recycle output armor_clothing.xxsmall 2824111863 6 XXSmall Armor & Clothing Bag armor_clothing.xsmall 100 Scrap 100 Scrap armor_clothing.xsmall 2824114542 12 XSmall Armor & Clothing Bag armor_clothing.small 200 Scrap 200 Scrap armor_clothing.small 2824116781 18 Small Armor & Clothing Bag armor_clothing.medium 300 Scrap 300 Scrap armor_clothing.medium 2824118678 24 Medium Armor & Clothing Bag armor_clothing.large 400 Scrap 400 Scrap armor_clothing.large 2824120619 30 Large Armor & Clothing Bag armor_clothing.xlarge 500 Scrap 500 Scrap armor_clothing.xlarge 2824122747 36 XLarge Armor & Clothing Bag armor_clothing.xxlarge 600 Scrap 600 Scrap armor_clothing.xxlarge 2824124690 42 XXLarge Armor & Clothing Bag generic.xxlarge 900 Scrap 900 Scrap Food & Medical Bags Name Skin ID Capacity Display Name Upgrades to Upgrade cost Recycle output food_medical.xxsmall 2824111462 6 XXSmall Food & Medical Bag food_medical.xsmall 100 Scrap 100 Scrap food_medical.xsmall 2824114220 12 XSmall Food & Medical Bag food_medical.small 200 Scrap 200 Scrap food_medical.small 2824116431 18 Small Food & Medical Bag food_medical.medium 300 Scrap 300 Scrap food_medical.medium 2824118433 24 Medium Food & Medical Bag food_medical.large 400 Scrap 400 Scrap food_medical.large 2824120423 30 Large Food & Medical Bag food_medical.xlarge 500 Scrap 500 Scrap food_medical.xlarge 2824122439 36 XLarge Food & Medical Bag food_medical.xxlarge 600 Scrap 600 Scrap food_medical.xxlarge 2824124459 42 XXLarge Food & Medical Bag generic.xxlarge 900 Scrap 900 Scrap Items & Construction Bags Name Skin ID Capacity Display Name Upgrades to Upgrade cost Recycle output items_construction.xxsmall 2824113019 6 XXSmall Items & Construction Bag items_construction.xsmall 100 Scrap 100 Scrap items_construction.xsmall 2824115483 12 XSmall Items & Construction Bag items_construction.small 200 Scrap 200 Scrap items_construction.small 2824117546 18 Small Items & Construction Bag items_construction.medium 300 Scrap 300 Scrap items_construction.medium 2824119338 24 Medium Items & Construction Bag items_construction.large 400 Scrap 400 Scrap items_construction.large 2824121607 30 Large Items & Construction Bag items_construction.xlarge 500 Scrap 500 Scrap items_construction.xlarge 2824123520 36 XLarge Items & Construction Bag items_construction.xxlarge 600 Scrap 600 Scrap items_construction.xxlarge 2824125425 42 XXLarge Items & Construction Bag generic.xxlarge 900 Scrap 900 Scrap Resources & Components Bags Name Skin ID Capacity Display Name Upgrades to Upgrade cost Recycle output resources_components.xxsmall 2824112139 6 XXSmall Resources & Components Bag resources_components.xsmall 100 Scrap 100 Scrap resources_components.xsmall 2824114807 12 XSmall Resources & Components Bag resources_components.small 200 Scrap 200 Scrap resources_components.small 2824117061 18 Small Resources & Components Bag resources_components.medium 300 Scrap 300 Scrap resources_components.medium 2824118878 24 Medium Resources & Components Bag resources_components.large 400 Scrap 400 Scrap resources_components.large 2824121055 30 Large Resources & Components Bag resources_components.xlarge 500 Scrap 500 Scrap resources_components.xlarge 2824123001 36 XLarge Resources & Components Bag resources_components.xxlarge 600 Scrap 600 Scrap resources_components.xxlarge 2824124960 42 XXLarge Resources & Components Bag generic.xxlarge 900 Scrap 900 Scrap Weapons & Tools Bags Name Skin ID Capacity Display Name Upgrades to Upgrade cost Recycle output weapons_tools.xxsmall 2824110902 6 XXSmall Weapons & Tools Bag weapons_tools.xsmall 100 Scrap 100 Scrap weapons_tools.xsmall 2824113791 12 XSmall Weapons & Tools Bag weapons_tools.small 200 Scrap 200 Scrap weapons_tools.small 2824116147 18 Small Weapons & Tools Bag weapons_tools.medium 300 Scrap 300 Scrap weapons_tools.medium 2824118115 24 Medium Weapons & Tools Bag weapons_tools.large 400 Scrap 400 Scrap weapons_tools.large 2824120210 30 Large Weapons & Tools Bag weapons_tools.xlarge 500 Scrap 500 Scrap weapons_tools.xlarge 2824122197 36 XLarge Weapons & Tools Bag weapons_tools.xxlarge 600 Scrap 600 Scrap weapons_tools.xxlarge 2824124162 42 XXLarge Weapons & Tools Bag generic.xxlarge 900 Scrap 900 Scrap Generic Bags Name Skin ID Capacity Display Name Upgrades to Upgrade cost Recycle output generic.xxsmall 2824110403 6 XXSmall Bag generic.xsmall 100 Scrap 100 Scrap generic.xsmall 2824113497 12 XSmall Bag generic.small 200 Scrap 200 Scrap generic.small 2824115881 18 Small Bag generic.medium 300 Scrap 300 Scrap generic.medium 2824117824 24 Medium Bag generic.large 400 Scrap 400 Scrap generic.large 2824119889 30 Large Bag generic.xlarge 500 Scrap 500 Scrap generic.xlarge 2824121905 36 XLarge Bag generic.xxlarge 600 Scrap 600 Scrap generic.xxlarge 2824123811 42 XXLarge Bag bagofholding 3000 Scrap 1500 Scrap Bag Of Holding The Bag of Holding is the ultimate bag. It can hold all items, including 6 other bags. Name Skin ID Capacity Display Name Recycle output bagofholding 2824136143 48 Bag of Holding 1500 Scrap Kit bags All kits bags accept all items and have 42 capacity. Kit bags also upgrade in a circular fashion, making it easy for admins to edit them. Name Skin ID Display Name Upgrades to kitbag.red.unlocked 2830974120 Kit Bag (Editable) kitbag.red.locked kitbag.red.locked 2830952942 Kit Bag kitbag.red.unlocked kitbag.orange.unlocked 2830974662 Kit Bag (Editable) kitbag.orange.locked kitbag.orange.locked 2830963984 Kit Bag kitbag.orange.unlocked kitbag.yellow.unlocked 2830975150 Kit Bag (Editable) kitbag.yellow.locked kitbag.yellow.locked 2830964495 Kit Bag kitbag.yellow.unlocked kitbag.green.unlocked 2830975690 Kit Bag (Editable) kitbag.green.locked kitbag.green.locked 2830965006 Kit Bag kitbag.green.unlocked kitbag.cyan.unlocked 2830976173 Kit Bag (Editable) kitbag.cyan.locked kitbag.cyan.locked 2830965451 Kit Bag kitbag.cyan.unlocked kitbag.blue.unlocked 2830976481 Kit Bag (Editable) kitbag.blue.locked kitbag.blue.locked 2830965789 Kit Bag kitbag.blue.unlocked Alternative bag skins By default, the bag profiles in the config use the fantasy style skins. If you want to change them to the leather or tactical style skins, you can use the boh.setskins command to edit the config in bulk. For example, to change the generic bag set to use tactical style skins, run the command boh.setskins generic 2828559961 2828562701 2828573095 2828576548 2828579661 2828582369 2828585532. Fantasy bag skins As of v1.9.0, you can apply the fantasy theme by running the command boh.settheme fantasy_chevrons. The old way is to run all of the following commands. boh.setskins bagofholding 2824136143 boh.setskins generic 2824110403 2824113497 2824115881 2824117824 2824119889 2824121905 2824123811 boh.setskins armor_clothing 2824111863 2824114542 2824116781 2824118678 2824120619 2824122747 2824124690 boh.setskins food_medical 2824111462 2824114220 2824116431 2824118433 2824120423 2824122439 2824124459 boh.setskins items_construction 2824113019 2824115483 2824117546 2824119338 2824121607 2824123520 2824125425 boh.setskins resources_components 2824112139 2824114807 2824117061 2824118878 2824121055 2824123001 2824124960 boh.setskins weapons_tools 2824110902 2824113791 2824116147 2824118115 2824120210 2824122197 2824124162 Additionally, you should set UI settings -> Belt button -> Display skin ID to one of the fantasy skins such as 2824115881. Here are all the fantasy skin sequences, in case you want to use other icons or colors. Fantasy plain: 2824110403 2824113497 2824115881 2824117824 2824119889 2824121905 2824123811 Fantasy gray chevrons: 2828128662 2828134240 2828137909 2828146246 2828148357 2828150051 2828152784 Fantasy white chevrons: 2828128323 2828133931 2828137681 2828146038 2828148160 2828149845 2828152530 Fantasy black chevrons: 2828128041 2828133673 2828137257 2828145823 2828148006 2828149681 2828152306 Fantasy red chevrons: 2828127703 2828133308 2828136874 2828145607 2828147808 2828149504 2828152062 Fantasy yellow chevrons: 2824113019 2824115483 2824117546 2824119338 2824121607 2824123520 2824125425 Fantasy pink chevrons: 2824112653 2824115134 2824117246 2824119088 2824121332 2824123291 2824125171 Fantasy orange chevrons: 2824112139 2824114807 2824117061 2824118878 2824121055 2824123001 2824124960 Fantasy light blue chevrons: 2824111863 2824114542 2824116781 2824118678 2824120619 2824122747 2824124690 Fantasy green chevrons: 2824111462 2824114220 2824116431 2824118433 2824120423 2824122439 2824124459 Fantasy blue chevrons: 2824110902 2824113791 2824116147 2824118115 2824120210 2824122197 2824124162 Fantasy gray circles: 2828493103 2828497364 2828501735 2828506499 2828509849 2828514060 2828517736 Fantasy white circles: 2828493673 2828498179 2828502089 2828506819 2828510161 2828514392 2828518167 Fantasy black circles: 2828494015 2828498546 2828502435 2828507169 2828510478 2828514709 2828518812 Fantasy red circles: 2828494496 2828498987 2828502735 2828507528 2828510830 2828515098 2828515098 Fantasy yellow circles: 2828494894 2828499337 2828503050 2828507851 2828511170 2828515395 2828519489 Fantasy pink circles: 2828495354 2828499673 2828503432 2828508323 2828511498 2828515725 2828519798 Fantasy orange circles: 2828495777 2828500070 2828503778 2828508555 2828511912 2828516131 2828520212 Fantasy light blue circles: 2828496161 2828500606 2828504060 2828508821 2828512403 2828516540 2828520492 Fantasy green circles: 2828496570 2828500962 2828504356 2828509103 2828512690 2828516933 2828520819 Fantasy blue circles: 2828496949 2828501318 2828504627 2828509404 2828513595 2828517346 2828521099 Leather bag skins As of v1.9.0, you can apply the leather theme by running the command boh.settheme leather_chevrons. The old way is to run all of the following commands. boh.setskins bagofholding 2860178102 boh.setskins generic 2831018252 2831025047 2831029422 2831036209 2831041769 2831047418 2831052354 boh.setskins armor_clothing 2831016990 2831023499 2831028259 2831032725 2831040190 2831046214 2831050372 boh.setskins food_medical 2831017392 2831023974 2831028588 2831033068 2831040759 2831046638 2831050826 boh.setskins items_construction 2831015836 2831021553 2831027189 2831031578 2831038734 2831044485 2831049142 boh.setskins resources_components 2831016651 2831023019 2831027874 2831032305 2831039657 2831045812 2831049942 boh.setskins weapons_tools 2831017759 2831024390 2831028922 2831033383 2831041231 2831047014 2831051442 Additionally, you should set UI settings -> Belt button -> Display skin ID to one of the leather skins such as 2831029422. Here are all the leather style skin sequences, in case you want to use other icons or colors. Leather plain: 2831018252 2831025047 2831029422 2831036209 2831041769 2831047418 2831052354 Leather gray chevrons: 2831013773 2831019060 2831025741 2831029969 2831036925 2831042295 2831047827 Leather white chevrons: 2831014482 2831019741 2831026169 2831030357 2831037360 2831042761 2831048137 Leather black chevrons: 2831015051 2831020041 2831026487 2831030777 2831037873 2831043219 2831048450 Leather red chevrons: 2831015444 2831020436 2831026854 2831031160 2831038330 2831043696 2831048702 Leather yellow chevrons: 2831015836 2831021553 2831027189 2831031578 2831038734 2831044485 2831049142 Leather pink chevrons: 2831016234 2831022032 2831027551 2831031924 2831039240 2831045338 2831049495 Leather orange chevrons: 2831016651 2831023019 2831027874 2831032305 2831039657 2831045812 2831049942 Leather light blue chevrons: 2831016990 2831023499 2831028259 2831032725 2831040190 2831046214 2831050372 Leather green chevrons: 2831017392 2831023974 2831028588 2831033068 2831040759 2831046638 2831050826 Leather blue chevrons: 2831017759 2831024390 2831028922 2831033383 2831041231 2831047014 2831051442 Leather gray circles: 2831053189 2831057140 2831060554 2831063925 2831066897 2831070017 2831082280 Leather white circles: 2831053670 2831057586 2831060848 2831064201 2831067178 2831071006 2831082963 Leather black circles: 2831054069 2831057911 2831061109 2831064444 2831067379 2831072147 2831084280 Leather red circles: 2831054490 2831058281 2831061382 2831064726 2831067561 2831073121 2831084887 Leather yellow circles: 2831054841 2831058559 2831061614 2831065014 2831067781 2831073592 2831085402 Leather pink circles: 2831055215 2831058892 2831061919 2831065349 2831068032 2831073925 2831085778 Leather orange circles: 2831055582 2831059194 2831062274 2831065681 2831068304 2831074420 2831087653 Leather light blue circles: 2831055919 2831059491 2831062555 2831066018 2831068615 2831076575 2831088591 Leather green circles: 2831056306 2831059795 2831062808 2831066320 2831068905 2831078713 2831088956 Leather blue circles: 2831056740 2831060200 2831063168 2831066588 2831069218 2831079950 2831089185 Tactical bag skins As of v1.9.0, you can apply the tactical theme by running the command boh.settheme tactical_chevrons. The old way is to run all of the following commands. boh.setskins bagofholding 2828612528 boh.setskins generic 2828559961 2828562701 2828573095 2828576548 2828579661 2828582369 2828585532 boh.setskins armor_clothing 2828558763 2828562098 2828571752 2828575986 2828579117 2828581616 2828584535 boh.setskins food_medical 2828559062 2828562247 2828572006 2828576133 2828579288 2828581907 2828584822 boh.setskins items_construction 2828557975 2828561492 2828570571 2828574809 2828578159 2828580887 2828583748 boh.setskins resources_components 2828558453 2828561930 2828571212 2828575734 2828578707 2828581409 2828584212 boh.setskins weapons_tools 2828559313 2828562454 2828572778 2828576369 2828579499 2828582142 2828585357 Additionally, you should set UI settings -> Belt button -> Display skin ID to one of the tactical skins such as 2828573095. Here are all the tactical style skin sequences, in case you want to use other icons or colors. Tactical plain: 2828559961 2828562701 2828573095 2828576548 2828579661 2828582369 2828585532 Tactical gray chevrons: 2828556434 2828560310 2828563014 2828573659 2828577253 2828580012 2828582671 Tactical white chevrons: 2828557125 2828560646 2828563283 2828573927 2828577583 2828580260 2828582975 Tactical black chevrons: 2828557433 2828560923 2828563544 2828574322 2828577810 2828580491 2828583268 Tactical red chevrons: 2828557692 2828561221 2828570104 2828574605 2828578000 2828580701 2828583514 Tactical yellow chevrons: 2828557975 2828561492 2828570571 2828574809 2828578159 2828580887 2828583748 Tactical pink chevrons: 2828558240 2828561757 2828570867 2828575078 2828578530 2828581157 2828583990 Tactical orange chevrons: 2828558453 2828561930 2828571212 2828575734 2828578707 2828581409 2828584212 Tactical light blue chevrons: 2828558763 2828562098 2828571752 2828575986 2828579117 2828581616 2828584535 Tactical green chevrons: 2828559062 2828562247 2828572006 2828576133 2828579288 2828581907 2828584822 Tactical blue chevrons: 2828559313 2828562454 2828572778 2828576369 2828579499 2828582142 2828585357 Tactical gray circles: 2828590059 2828592435 2828596053 2828598607 2828600574 2828602840 2828605402 Tactical white circles: 2828590364 2828592713 2828596309 2828598848 2828600805 2828603043 2828605787 Tactical black circles: 2828590658 2828592930 2828596615 2828599070 2828601043 2828603298 2828605999 Tactical red circles: 2828590870 2828593147 2828596818 2828599291 2828601240 2828603494 2828606193 Tactical yellow circles: 2828591083 2828593355 2828597034 2828599512 2828601444 2828603677 2828606367 Tactical pink circles: 2828591226 2828593626 2828597285 2828599643 2828601590 2828603900 2828606490 Tactical orange circles: 2828591389 2828594143 2828597493 2828599829 2828601859 2828604283 2828606662 Tactical light blue circles: 2828591603 2828594846 2828597739 2828600017 2828602079 2828604553 2828606893 Tactical green circles: 2828591817 2828595022 2828598019 2828600169 2828602304 2828604782 2828607054 Tactical blue circles: 2828592115 2828595430 2828598248 2828600324 2828602571 2828605041 2828607208 Developer API API_GetApi Dictionary<string, object> API_GetApi() Returns a dictionary where each key is a delegate for an API method. The purpose of this API is for high-performance scenarios where you don't want the overhead of calling the Bag of Holding via Oxide. Instead, your plugin should call Bag of Holding once (when Bag of Holding loads), cache the API, and invoke specific API methods via delegates whenever needed. Example: // Get the API. Ideally you should cache this. You should also re-cache this when Bag of Holding reloads. var api = BagOfHolding.Call("API_GetApi") as Dictionary<string, object>; // Get the API function you want. Ideally you should cache this too. The names are the same as documented below, but without the "API_" prefix. var isBagFunction = api["IsBag"] as Func<Item, bool>; // Call the API function. This call doesn't go through Oxide, so it saves CPU cycles, and allows you to avoid heap allocations when passing value types (e.g., when passing numbers). var isBag = isBagFunction(item); API_IsBag bool API_IsBag(Item item) Returns true if the item is a bag, else returns false. API_IsLootingBag bool API_IsLootingBag(BasePlayer player) Returns true if the player is looting a bag, else returns false. Note: If you call this immediately after the OnLootEntity Oxide hook is called, this will return false, because the plugin has to inspect the ItemContainers that the player is looting (basePlayer.inventory.loot.containers) which are populated after the OnLootEntity hook call has finished (that is where the Oxide hook is placed, and the plugin follows that pattern when explicitly calling OnLootEntity). Therefore, if you wish to detect whether a player has just opened a bag via the OnLootEntity hook, you should run your logic on the next frame (e.g., using NextTick). You may avoid calling this API entirely by simply verifying that the basePlayer.inventory.loot.containers list has only one container, and that it has a parentItem. If both of those criteria are met, the player is looting some sort of item, not necessary from this plugin, but that should be close enough. Note that this logic still needs to be in NextTick for the aforementioned reason. API_GetBagProfileName string API_GetBagProfileName(Item item) Returns the profile name of the bag (not the display name), else returns null if the item is not a bag. If you want the display name, simply read item.name. API_OpenBag bool API_OpenBag(BasePlayer player, Item item) Attempts to make the player open the bag Returns true if the item is a valid lootable bag (not a locked bag), and if not blocked by a plugin via the OnBagOpen hook Returns false if the item was not a valid lootable bag, or if blocked by a plugin via the OnBagOpen hook API_CreateBag Item API_CreateBag(string profileName, int amount = 1) Creates a bag using the specified profile name, with specified stack amount Returns the bag Item if successful Returns null if the specified profile name or stack amount is invalid Note: Bags can also be created using ItemManager.CreateByName("halloween.lootbag.large", amount, skinId) if the skin ID is known API_CreateKitBag Item API_CreateKitBag(string profileName, string kitName, BasePlayer initiator = null) Creates a bag using the specified profile name, and populates it with the specified kit Returns the bag Item if successful Returns null if the specified profile name or kit name is invalid If any kit items do not fit in the bag, they will be given to the BasePlayer initiator if provided, else deleted. API_ChangeBagProfile bool API_ChangeBagProfile(Item item, string profileName, BasePlayer initiator = null) Updates the bag item to the specified profile Returns true if the item is a valid bag, and if the specified profile name is valid Returns false if the item is not a valid bag, or if specified profile name is invalid If the target profile has less capacity than the current profile... Overflowing items will attempt to be compacted into the bag by moving them to earlier slots If compaction fails, the remaining items will be given to the BasePlayer initiator if provided If the BasePlayer initiator is not provided, the bag capacity will be increased to fit the overflowing items Caution: If the item is a stack of bags, it will change the profile for all of the bags in the stack Caution: Changing the profile of a bag that is already inside a container may cause the container to exceed configured bag limits API_UpgradeBag bool API_UpgradeBag(Item item, BasePlayer initiator = null) Updates the bag item to the profile designated as the upgrade target in the config Returns true if the item is a valid bag, and if the bag profile has a valid upgrade target in the config Returns false if the item is not a valid bag, or if the bag profile does not have a valid upgrade target in the config If the target profile has less capacity than the current profile... Overflowing items will attempt to be compacted into the bag by moving them to earlier slots If compaction fails, the remaining items will be given to the BasePlayer initiator if provided If the BasePlayer initiator is not provided, the bag capacity will be increased to fit the overflowing items Caution: If the item is a stack of bags, it will upgrade all of the bags in the stack Caution: Upgrading a bag that is already inside a container may cause the container to exceed configured bag limits Developer hooks OnBagOpen object OnBagOpen(Item item, BasePlayer player) Called when a player attempts to open a bag Returning false will prevent the bag from being opened Returning null will result in the default behavior OnBagOpened void OnBagOpened(Item item, BasePlayer player) Called after a player has started looting a bag No return behavior OnBagClosed void OnBagClosed(Item item, BasePlayer player) Called after a player has stopped looting a bag No return behavior OnBagUpgrade object OnBagUpgrade(Item item, string newProfileName, BasePlayer initiator) Called when a player or a plugin attempts to upgrade a bag Returning false will prevent the bag from being upgraded Returning null will result in the default behavior Note: The BasePlayer argument will be null if the upgrade was not initiated by a player. OnBagUpgraded void OnBagUpgraded(Item item, string newProfileName, BasePlayer initiator) Called after a bag has been upgraded to the profile designated in the config No return behavior Note: The BasePlayer argument will be null if the upgrade was not initiated by a player OnBagProfileChanged void OnBagProfileChanged(Item item, string newProfileName) Called after a bag's profile has been changed No return behavior

Features Allows players to deploy ziplines from a distance using a crossbow Allows bidirectional ziplines Allows adjusting zipline movement speed, optionally based on incline Optionally requires cable to deploy ziplines Extensive configuration options to restrict zipline deployment Integrates with Economics and Server Rewards to allow buying the Zipline Tool Integrates with No Escape to prevent deploying ziplines while Raid blocked or Combat blocked Integrates with Remover Tool to provide an alternate way to pick up ziplines How it works To deploy a zipline, a player must first obtain a Zipline Tool and some Zipline Cable. By default, the Zipline Tool is a crossbow with a custom skin, and Zipline Cable is rope with a custom skin. Once acquired, the player must shoot the crossbow where they want to start the zipline, then shoot again where they want to end the zipline (no arrows needed). Once the zipline has been deployed, players can ride it just like the vanilla ziplines, by looking up at the top of the start point and interacting with the "Use Zipline" prompt. Since both the Zipline Tool and Zipline Cable are items, there are many ways you can provide them to players, including via kits, vending machines, and loot tables. The plugin also allows players to purchase them directly with chat commands. Permissions This plugin uses the permission system. To assign a permission, use oxide.grant <user or group> <name or steam id> <permission>. To remove a permission, use oxide.revoke <user or group> <name or steam id> <permission>. Admin permissions deployablezipline.protect -- Allows the player to run the zipline protect command to toggle protection for any ziplines they deploy. Protected ziplines do not decay, and can only be picked up by players with this permission. Purchase permissions deployablezipline.buy.tool - Allows buying the Zipline Tool with the zipline buy command. deployablezipline.buy.cable - Allows buying Zipline Cable with the zipline buycable <amount> command. Tool usage permissions Depending on how you have configured the plugin, there will be additional permissions like deployablezipline.profile.<suffix>, one for each profile. The plugin comes with the following profiles by default. Note: Players must have permission to a profile in order to use the Zipline Tool. deployablezipline.profile.balanced 4 ziplines max 100m max zipline length 10 uses per Zipline Tool, but can be repaired Allows up to 45° decline and 15° incline Disallows monuments deployablezipline.profile.fun 6 ziplines max 200m max zipline length Unlimited uses per Zipline Tool Allows up to 45° decline and 45° incline Allows monuments deployablezipline.profile.unrestricted Unlimited ziplines 10000m max zipline length Unlimited uses per Zipline Tool No angle or location restrictions Speed permissions The speed that players move along a deployed zipline can be configured according to the permissions of the player riding the zipline (not the player who deployed it). Each speed profile will have a permission like deployablezipline.speed.<suffix>. You can make as many speed profiles as you want in the configuration. The plugin comes with the following speed profiles by default. deployablezipline.speed.slow 0.25x min uphill speed 0.5x max horizontal speed 0.75x max downhill speed deployablezipline.speed.balanced 0.5x min uphill speed 1x max horizontal speed 1.5x max downhill speed deployablezipline.speed.fast 0.75x min uphill speed 1.5x max horizontal speed 2.25x max downhill speed deployablezipline.speed.ridiculous 5x max speed deployablezipline.speed.ludicrous 10x max speed Commands This plugin provides both chat and console commands using the same syntax. When using a command in chat, prefix it with a forward slash: /. zipline buy -- Purchases a Zipline Tool. Requires the deployablezipline.buy.tool permission. By default, it costs 100 scrap. zipline buycable <amount> -- Purchases Zipline Cable. Requires the deployablezipline.buy.cable permission. By default, it costs 1 scrap. zipline toggle -- Enables or disables bidirectional mode for ziplines you deploy after running this command. Alternatively, you can press MMB (middle mouse button) while wielding a Zipline Tool. To use this command, you must have permission to a Zipline Tool profile that allows bidirectional ziplines. zipline protect -- Enables or disables protection of ziplines you deploy after running this command. Requires the deployablezipline.protect permission. A protected zipline does not decay, and can only be picked up by players who have the deployablezipline.protect permission. Configuration The settings and options can be configured in the DeployableZipline file under the config directory. The use of an editor and validator is recommended to avoid formatting issues and syntax errors. Zipline tool Zipline Tool -- Determines which item is considered the Zipline Tool. This item can also be used to pick up ziplines when Pickup restrictions > Require hammer or zipline tool to pick up zipline is set to true. Players may purchase this tool with the zipline buy command if they have the deployablezipline.buy.tool permission. Item short name -- The short name of the Zipline Tool item. Must be an equippable item. Default: "crossbow". Item skin ID -- The skin ID of the Zipline Tool item. Default: 2793006815. Purchase info Cost -- Determines the cost to purchase the Zipline Tool. Item short name -- The short name of the currency item. Default: "scrap". Item skin ID -- The skin ID of the currency item. Set to 0 to require an unskinned currency item. Default: 0. Amount -- The amount of currency required to purchase the Zipline Tool. Default: 100. Use Economics (true or false) -- Set to true to require Economics currency instead of item currency. Default: false. Use Server Rewards (true or false) -- Set to true to require Server Rewards currency instead of item currency. Default: false. Attachment item short names -- Determines which attachments will be added to the Zipline Tool when purchased. Only applies to weapons that can have attachments. Default: ["weapon.mod.holosight", "weapon.mod.lasersight"]. Zipline cable Zipline Cable -- Determines which item is considered Zipline Cable. Note: You can independently configure the condition loss of the Zipline Tool if you want to consume the tool itself. Item short name -- The short name of the item. Default: "rope". Item skin ID -- The skin ID of the cable item. Default: 2793158547. Cost -- Determines the cost to purchase Zipline Cable. Item short name -- The short name of the currency item. Default: "scrap". Item skin ID -- The skin ID of the currency item. Set to 0 to require an unskinned currency item. Default: 0. Amount -- The amount of currency required to purchase Zipline Cable. Default: 1. Use Economics (true or false) -- Set to true to require Economics currency instead of item currency. Default: false. Use Server Rewards (true or false) -- Set to true to require Server Rewards currency instead of item currency. Default: false. Pickup restrictions Pickup restrictions -- Determines under which circumstances players may pick up ziplines. Require hammer or zipline tool to pick up zipline (true or false) -- Set to true to require the player to be holding a hammer or the Zipline Tool to pick up a zipline. This only applies to ends of the zipline that use the spear item, since the Tesla Coil end already requires a hammer to pick up. Default: true. Allow pickup while building blocked at other end (true or false) -- Set to true to allow players to pick up a zipline from one end, while they are building blocked at the other end of the zipline. Default: true. Note: Regardless of this option, players may not pick up a zipline from an end where they are building blocked. Effects Effects -- Determines the effects that are played when using the Zipline Tool, or when trying to pick up a zipline. Tool impact (player only) -- Plays when the player hits a surface with the Zipline Tool. Only the Zipline Tool wielder will witness the effect. This provides feedback to the player so they can see where they hit. Tool failed (player only) -- Plays when the player tries to use the Zipline Tool but experiences an error. Only the Zipline Tool wielder will witness the effect. The wielder may experience an error for many reasons, such as being Building Blocked, or due to having insufficient Zipline Cable. Tool used -- Plays when the player successfully places either end of zipline using the Zipline Tool. Other players will witness the effect. Deploy succeeded -- Plays when the player successfully deploys a zipline using the Zipline Tool. Plays on both ends of the zipline. Other players will witness the effect. Pickup failed (player only) -- Plays when the player fails to pick up a zipline due to being Building Blocked. Only the Zipline Tool wielder will witness the effect. Zipline Tool permission profiles Zipline Tool permission profiles - Zipline Tool profiles allow you to define complex rulesets depending on a user's Oxide permissions. You may define unlimited profiles, but at most one will be assigned to each player. Profiles toward the end of the list have highest priority. Permission suffix -- Determines the permission that you must grant to assign the profile to a player or group. For example, set this to "fun" to produce the permission deployablezipline.profile.fun. Allow tool while building blocked (true or false) -- Determines whether the player may use the Zipline Tool while they are standing in a location where they are Building Blocked. Allow bidirectional ziplines (true or false) -- Determines whether the player is allowed to place bidirectional ziplines. A bidirectional zipline can be mounted from either end. The player can press MMB (Mouse3) to enable/disable bidirectional mode. Zipline min length -- Determines the minimum zipline length that the player can deploy. Zipline max length -- Determines the maximum zipline length that the player can deploy. Zipline max decline angle -- Determines the maximum downward angle of ziplines that the player can deploy. Set to 90.0 to allow the player to deploy ziplines that go straight downward. Set to 0 to only allow ziplines to go across or upward. Zipline max incline angle -- Determines the maximum upward angle of ziplines that the player can deploy. Set to 90.0 to allow the player to deploy ziplines that go straight upward. Set to 0 to only allow ziplines to go across or downward. Zipline max elevation increase -- Determines the maximum delta between the zipline start position and end position. Set to 0 to only allow ziplines to go across or downward. Tool condition loss percent per zipline deployed -- Determines how much condition the Zipline Tool will lose when the player deploys a zipline. Set to 0 to allow unlimited uses. Set to 100 to allow only one use per Zipline Tool. The Zipline Tool will be destroyed when reaching 0 condition. Tool cooldown seconds -- Determines how long the player must wait after deploying a zipline with the Zipline Tool before they can deploy another one. Max ziplines at once -- Determines the maximum number of ziplines that the player may have in the map at once. Cable cost -- Determines how much Zipline Cable will be consumed when deploying a zipline. Cost per meter -- Determines how much Zipline Cable is required per meter. Set to 0 to not require any Zipline Cable. Set to a fraction such as 0.5 to allow each unit of Cable to cover multiple meters. Refund amount per meter on pickup -- Determines how much Zipline Cable is refunded when the player's ziplines are picked up. Set this to the same value as Cost per meter to allow players to recover all their Zipline Cable when picking up a zipline. Set to less than Cost per meter to effectively impose a penalty by refunding less than what was spent. Start point ruleset -- Determines the locations at which the player can place a zipline start point. Allow while building blocked (true or false) -- Determines whether the player can remotely place this end of the zipline at a location where they are Building Blocked, regardless of whether they are standing in a Building Blocked location. Min height above terrain -- Determines how close to terrain the player can deploy this end of the zipline. Set to 0 to allow placing a zipline at terrain level. Max deploy distance -- Determines the maximum distance away from the player that they can place this end of the zipline. Allowed layers -- (Advanced) Determines the Rust object layers to which the player can attach this end of the zipline. The player will not be able to attach a zipline to objects on other layers. Allowed values: Default, TransparentFX, Ignore_Raycast, Reserved1, Water, UI, Reserved2, Reserved3, Deployed, Ragdoll, Invisible, AI, Player_Movement, Vehicle_Detailed, Game_Trace, Vehicle_World, World, Player_Server, Trigger, Player_Model_Rendering, Physics_Projectile, Construction, Construction_Socket, Terrain, Transparent, Clutter, Debris, Vehicle_Large, Prevent_Movement, Prevent_Building, Tree, Unused2. Disallowed topology -- (Advanced) Determines the types of Terrain Topology to which the player cannot attach this end of the zipline. Set to [] to allow all types of Terrain Topology. Allowed values: Field, Cliff, Summit, Beachside, Beach, Forest, Forestside, Ocean, Oceanside, Decor, Monument, Road, Roadside, Swamp, River, Riverside, Lake, Lakeside, Offshore, Rail, Railside, Building, Cliffside, Mountain, Clutter, Alt, Tier0, Tier1, Tier2, Mainland, Hilltop. End point ruleset -- Determines the locations at which the player can place the zipline end point. Same options as Start point ruleset. Zipline decay settings -- Determines how quickly deployed ziplines decay while outside of Tool Cupboard range. Note: Only one end of the zipline must be within Tool Cupboard range to protect it from decay. Also, instead of taking damage, the zipline will simply disappear when the decay time has elapsed. Enabled (true or false) -- Determines whether decay is enabled. Default: true. Decay minutes -- Determines how long a zipline is protected from decay after being deployed, or after nearby Tool Cupboards are removed. Default: 60. No Escape integration -- Determines whether the player can use the Zipline Tool while Raid Blocked or Combat Blocked, as determined by the No Escape plugin. Allow tool while raid blocked (true or false) -- Set to false to prevent the player from using the Zipline Tool while they are Raid Blocked. Allow tool while combat blocked (true or false) -- Set to false to prevent the player from using the Zipline Tool while they are Combat Blocked. Speed permission profiles Speed permission profiles -- Speed profiles allow you to configure how quickly players move along ziplines, depending on the Oxide permissions of the player riding it. You may define unlimited speed profiles, but at most one will be assigned to each player. Speed profiles toward the end of the list have highest priority. Permission suffix -- Determines the permission that you must grant to assign the speed profile to a player or group. For example, set this to "balanced" to produce the permission deployablezipline.speed.balanced. Move speed -- Determines the max speed that applies when the player is not holding the forward key. Bonus move speed -- Determines the additional max speed that applies when the player is holding the forward key. This value is added on top of Move speed to determine the total max speed. Acceleration time (seconds) -- Determines how many seconds it will take the player to reach max speed after mounting the zipline. Downhill speed bonus -- Determines how much to increase speed while going downhill. Percent increase per angle degree -- Example: While this is set to 1.0, going downhill at a 45° angle will increase max speed to 145%. Max speed percent -- Example: while Percent increase per angle degree is set to 1.0, and while this is set to 130.0, going downhill at a 45° angle would increase speed to only 130% instead of to 145%. Uphill speed penalty -- Determines how much to decrease speed while going uphill. Percent decrease per angle degree -- Example: While this is set to 1.0, going uphill at a 45° angle will decrease max speed to 55%. Min speed percent -- Example: While Percent decrease per angle degree is set to 1.0, and while this is set to 70.0, going uphill at a 45° angle would decrease speed to only 70% instead of 55%. Localization The default messages are in the DeployableZipline file under the lang/en directory. To add support for another language, create a new language folder (e.g. de for German) if not already created, copy the default language file to the new folder and then customize the messages.

A new event that takes place at the Supermarket monument, made for beginners on your server Description The event begins with a message in the chat that soon a merchant who sells valuable cargo will arrive at a Supermarket on your island. The merchant and their guards with trained dogs appear around the supermarket. Players then have the opportunity to rob the Merchant in order to get all the Supermarket loot for themselves. As soon as the players begin to attack the Merchant, an armored helicopter arrives there with additional security and a Debt Collector. The Debt Collector enters the Supermarket and begins the process of collecting his loot and the Merchant for evacuation. If the player manages to kill all the guards outside the supermarket before the end of this process, then he can enter and loot. There are several more guards, the Merchant and the Debt Collector waiting for the player. The Merchant and the Debt Collector need to be eliminated to get the most valuable loot that they wanted to evacuate. There are also several loot crates inside the Supermarket to be looted. If the Merchant and or the Debt Collector survive, they will fly away in the armored helicopter and the player will not receive the juicy loot they were dealing. In the plugin configuration, it is possible to configure all timers, the guards outside the supermarket, inside the Supermarket, Debt Collector guards, and guard dogs patrolling outside the Supermarket. The Merchant and Debt Collector can also be configured as well. A list of all the loot crates inside the supermarket, map marker, event icons on the players screen, and more are all able to be adjusted in the config file. Dependencies (optional, not required) True PVE PveMode GUI Announcements Notify Discord Messages AlphaLoot CustomLoot NTeleportation Economics Server Rewards IQEconomic XPerience Kits Better Npc Monument Owner Chat commands (only for administrators) /supermarketstart - start the event /supermarketstop - end the event Console commands (RCON only) supermarketstart - start the event supermarketstop - end the event Plugin Config en - example of plugin configuration in English ru - example of plugin configuration in Russian Hooks void OnSupermarketEventStart(Vector3 pos, float radius) – called when the event starts void OnSupermarketEventEnd() – called when the event ends void OnSupermarketEventWinner(ulong winnerId) – called at the end of the event, where the winnerId is the player who did more actions to complete the event My Discord: kpuctajl Join the Mad Mappers Discord here! Check out more of my work here!

The plugin allows players to visit a cold atmospheric Space void of gravity and oxygen, and visit an International Space Station! A Space Station appears high in the sky, and is surrounded by Meteorites, Spaceships, and Balloons. There is no gravity in Space, the temperature is very low and there is no oxygen. You can get to Space by a Spaceship or by a Balloon which also spawn near roads or in loot tables. The Space Station is guarded by customizable NPCs and a Space Bradley. Outer Space Meteorites, Crates, NPCs, Balloons and Spaceships will spawn in Outer Space near the Space Station, the number of each can be configured and customized. In order to survive in Outer Space, the player will need a Spacesuit. A Spacesuit can be customized to be any piece of clothing. In the config you can customize items that will perform the functions of the Spacesuit in whole or in part. To make space dark for players at any time of the day, use the NightVision plugin Space Station The Space Station consists of several compartments that are separated from each other by doors. Optionally, the doors can be locked and they will need to be raided. Inside the station there are crates with loot, NPCs, turrets, and fire turrets. At the end of the corridor there are two doors that open with blue cards and one door that opens with red. The spawn of the space station can be disabled. All objects on the space station are configured in the Data file of this station Spaceship The plugin includes spaceships that can spawn near roads, in Space, or can be added to loot tables. The ship has separate settings for flying in the normal atmosphere and in zero gravity in Space. It can shoot torpedoes, which will help the player in capturing the space station. There are two seats in each spaceship. Shuttle Control Guide: Balloon A balloon is an ordinary balloon with which you can ride into outer space. The balloon can spawn near roads, in Space, or can be added to loot tables. Also, this function can be applied to all balloons on the server. If the balloon is in zero gravity, it can be used as an escape capsule! If necessary, the player can enter, press a button, and be taken out of Space into the normal atmosphere. Dependencies Required NpcSpawn Chat commands (only for administrators) /spacestart – launches the event in a random configuration /spacestart <eventPresetName> – launches the event in the <eventPresetName> configuration /spacestop – stops the event /spawnshuttle – spawn the shuttle in your position /spawnaerostat – spawn the aerostat in your position /spacepoint – creates a custom spawn point of the event in your position (after that, you need to enable custom spawn points in the config) Console commands (RCON only) spacestart – launches the event in a random configuration spacestart <eventPresetName> – launches the event in the <eventPresetName> configuration spacestop – stops the event givepurplecard <userId> <amount> – gives a space card to a player giveshuttle <userId> <amount> – gives a shuttle to a player giveaerostat <userId> <amount> – gives a shuttle to a player givespacesuit <space_suit_preset> <userId> <amount> – gives <space_suit_preset> to a player Config plugin_en – example of plugin configuration in English station_en – example of station configuration in English plugin_ru – example of plugin configuration in Russian station_ru – example of station configuration in Russian Dependencies (optional, not required) True PVE PveMode GUI Announcements Notify DiscordMessages AlphaLoot CustomLoot Economics Server Rewards IQEconomic Hooks void OnSpaceEventStop() void OnSpaceEventStart() API bool IsPositionInSpace(Vector3 position) float GetMinSpaceAltitude() bool IsEventActive() My Discord: adem9554 Join the Mad Mappers Discord here! Check out more of my work here!

The Trucks Pack More than 100+ trucks! Lights and snowy versions, unique appearance! (Prefab count: 4202) This pack includes a .prefab and a .map file for easy configuration!