Mighty3z's Wishlist

Turn player engagement into a clear, visual reward journey with configurable catalogues, secure claims, and administrator-controlled delivery.
At a glance
Create independent reward types with their own points, catalogue, commands, permission, language, and visual theme. Let players browse paginated rewards, see locked or claimed states, and claim eligible rewards from an in-game UI. Deliver items, server commands, permission grants, and group grants through one reviewed reward definition. Keep point ownership compatible with integrations such as Vote System while retaining administrator control. Recover safely from reloads and partial delivery without replaying completed actions. How it helps
Custom Rewards gives server owners one reusable reward layer instead of a separate UI and claim implementation for every event. Each reward type can represent voting, playtime, seasonal progress, VIP benefits, or another server-owned points source.
Key features
Multiple reward catalogues, each stored in its own JSON file. Configurable show commands and dynamic customrewards.<type>.use access. Common, Rare, Epic, and Legendary presentation with configurable colours. Per-page browsing with visible available, locked, and claimed states. Server-side eligibility checks repeated when a reward is claimed. Item, command, permission, and group actions. Owner-scoped point APIs for integrations. Durable claim progress and administrator-visible reconciliation when an external action has an uncertain result. Safe migration of supported legacy player data. Player workflow
An administrator enables a reviewed reward type and grants its use permission. The player runs one of that type's configured chat commands. The UI displays the current catalogue and the player's claim state. The player changes page if needed and selects an eligible reward. The server validates points, prerequisites, and claim state again before delivery. The visible screen distinguishes rewards that are available, already claimed, or unavailable. Administrators decide which commands display each catalogue and which groups can access it.
How it works
Each file in oxide/data/CustomRewards_rewards/ defines one reward type. Its filename is the exact type used by permissions and integrations. Player balances and claim progress are stored separately so an interrupted delivery can resume without repeating confirmed actions.
customrewards_give VoteSystem 76561198000000000 5
The example grants five owner points to the VoteSystem reward type. Run administrator commands from the server console or with the administrative permission.
Requirements and compatibility
Rust server using Oxide or Carbon. The standalone CustomRewards.cs file from this product. No required plugin dependency. Optional integrations must use the documented compatibility APIs and the same reward-type name. Setup
Back up existing oxide/data/CustomRewards_* files. Install CustomRewards.cs in the framework plugin directory. Let the plugin create oxide/data/CustomRewards_rewards/. Copy and rename the supplied example configuration for each reward type you need. Review every item name, server command, permission change, group change, image URL, and eligibility rule. Set Enabled to true only after that review. Grant customrewards.<type>.use and test the configured show command with a non-administrator account. Commands and permissions
CommandPurposeAuthorization
Reward-type show commandsOpen the configured catalogue UIAdministrator or customrewards.<type>.use
customrewards_give <type> <player> <quantity>Add points to one playercustomrewards.admin
customrewards_wipe_owner <type> <owner>Remove one owner's contribution from a balancecustomrewards.admin
customrewards_wipe_all <type>Clear all balances for one reward typecustomrewards.admin
customrewards_changepageInternal player paging actionPublic, arguments validated by the server
customrewards_claimInternal player claim actionPublic, eligibility rechecked by the server
The historical CustomRewards.Admin and CustomRewards.<Type>.Use forms remain accepted for existing installations.
Configuration highlights
New reward types are disabled by default. Start with a small catalogue and a test-only permission:
{ "Enabled": false, "Commands for show UI": ["vote_rewards"], "UI Settings": { "Max Reward By Page": 5, "Show Description": true }, "Rewards Settings": { "Rewards List": [ { "Rarity (Common - Rare - Epic - Legendary)": "Common", "Quantity": 100, "Item Shortname (optional)": "wood", "Server command (optional)": [], "Grant Permissions :": [], "Grant Groups :": {}, "Needed Permissions :": {}, "Needed Groups :": {} } ] } }
Only %steamid% is accepted as a command placeholder. Keep reward configuration restricted to trusted administrators because configured commands and access changes are privileged actions.
Practical tutorials
Example: create a voting catalogue
Create VoteSystem.json in oxide/data/CustomRewards_rewards/. Set a safe show command such as vote_rewards. Add one low-value test reward and leave the type disabled. Reload Custom Rewards and resolve every validation error. Grant customrewards.votesystem.use to a test group. Enable the type, add test points, open the UI, and claim the reward. Add the remaining catalogue only after the complete test succeeds. Example: integrate another points source
Use the owner-points API with a stable owner name. Keep the reward type identical in both plugins, check that it is enabled, and open the UI through the structured UI method so a failure can be reported without exposing an incomplete screen.
Troubleshooting
The show command is unknown: confirm the reward type is enabled and its command is unique. The UI says access is denied: grant customrewards.<type>.use or test with an administrator. A catalogue does not load: review the first validation error for invalid actions, empty rewards, unsafe placeholders, or contradictory access rules. A claim is pending review: inspect the administrator diagnostic before retrying; do not edit player data to bypass an uncertain external action. Images do not appear: verify direct HTTPS image URLs and keep custom URLs under administrator control. FAQ
Can two reward types use different themes?
Yes. Each reward-type file owns its catalogue, UI settings, colours, commands, and access permission.
Can a reward combine actions?
Yes. One reward can contain an item plus reviewed commands, permission grants, or group grants. Each action is tracked separately during delivery.
Does Custom Rewards require Vote System?
No. Vote System is an optional points source. Custom Rewards can run with administrator grants or another compatible integration.
Support
Use the Codefling support section with the plugin version, framework, reward-type name, the first relevant error, and a redacted configuration excerpt. Never include API tokens or private player data.

XSkinMenu - beautiful menu of skins for your server.
- Optimization of the interface for different monitor resolutions.
-  Storing player data in - oxide/data/XDataSystem/XSkinMenu
- There is a lang ru/en/uk/es.
- Sound effects when interacting with the menu.
- Setting up item categories.
- Setting skins for each item.
- Blacklist of skins. You cannot change the skin of an item if it has a skin from the black list. [ For example: fire gloves, fire ax ]
- The ability to change skins for items in inventory, when crafting, when removing a skin and on installed items/constructions.
- The ability to change the skin of items/constructions installed by a friend.
- The ability to change the skin on the active item. [ The item the player is holding ]
- Automatic change of skins after entering the player's inventory. [ You can customize skins once and run with them ]
- Ability to change skins for items after the player respawns.
- Ability to display selected skins on the main page.
- The player can customize the menu/skins.
- Custom menu/skins customization by permishenes.
- Console commands for easy setting of items and skins.
- Setting up UI layers for easy interaction with the menu.
- Convenient removal of skins through the UI. [ Both admin and player ]
- Logs for loading/reloading skins in the server console. [ Can be disabled in config ]
- Setting default skins.
When a player enters the server and he is not in the data, the skins specified in the config will be automatically selected for him. You can force the same skins for all players. For example skins of your project. To prevent the player from choosing a different skin, simply do not give permission for it. - Automatic reload of images after wipe. [ To fix a common problem with dark squares in images after a wipe. ]
- The ability to customize Admin/Vip skins. Access to them is by permission only.
[  They are not available to ordinary players. If the player picks up an item with a skin that they don't have access to, the item will simply reset its skin. ]
- The ability to move item skins from regular to VIP, from VIP to regular, etc. in the UI.
- The ability to add/remove collections of skins from the Steam workshop.
- Button to enable/disable UI admin functionality. [ For comfort. ]
- UI button for easy transition from the  XSkinMenu menu to the XBuildingSkinMenu menu. [ And vice versa. ]
- Display item/skin pages. [ Can be disabled in the config. ]
- The ability to use skins with a spray can.
-  The ability to enable/disable sound effects in the menu.
- The ability to change item skins when picked up by the player.
- The ability to select UI configuration:
Default menu. Comfort menu. Comfort menu. [ + ] - Skin kits. [ Default and personal. ]
- Default kits are customized in the config. Personal kits are created by the player himself. [ Sets can be completely disabled. ]
- Ability to delete personal kits.
- The ability to see all the skins of the kit.
- Three ways to apply skin kits:
Only change the skins in the inventory. Only install skins in the menu. Change the skins in the inventory + Install skins in the menu. - Ability to zoom in on skins. [ It's easy to see the skin. ]
- Displaying the name of skins.
- Skin search. [ Name or ID ]
- Ability to add a skin/collection via UI.
- Item redirection. [ Item -> DLC, DLC -> DLC, DLC -> Item ]
- Ability to allow players to use skins from their Steam inventory if those skins are on the Admin/VIP list.
 
 
 
Permissions
xskinmenu.use - access to the menu. xskinmenu.setting - access to settings. xskinmenu.craft - access to changing the skin when crafting. xskinmenu.entity - access to change the skin of installed items/constructions. xskinmenu.item - access to change the skin on the active item. xskinmenu.inventory - access to change skins in the inventory. [ When the player selects a skin from the menu. ] xskinmenu.give - access to automatically change skins for items that enter the player inventory by any means. xskinmenu.pickup - access to automatically change skins on items picked up by the player. xskinmenu.skinchange - access to skin selection/removal of selected skins. [ On the menu. ] xskinmenu.spraycan - access to the use of skins through a spray can. xskinmenu.playeradd - access to add skin/collection via UI. xskinmenu.defaultkits - access to default skin kits. xskinmenu.customkits - access to personal skin kits. xskinmenu.kitN - number of personal sets. [ Settings in config. ] xskinmenu.adminskins - access to Admin skins. xskinmenu.vipskins - access to VIP skins. xskinmenu.admin - access to admin functionality. Commands
/skin - open the skins menu. /skinkit - open the skin kits menu. /skinentity - change the skin of an installed item/construction. [ The player must approach the object and write a command. ] /skinitem - change the skin on the active item. [ The player must hold the object in his hands and write the command. ] skinimage_reload - reload all images. skinimage_stop - stop loading/reloading images. xskin2 add2 000000 ... - add several(maximum 15) skins, without specifying a shortname. xskin2 remove2 000000 ... - remove several(maximum 15) skins, without specifying a shortname. [ Automatic shortnames detection. ] xskin add <item shortname> <skinID> - add a new skin to the list of item skins. xskin remove <item shortname> <skinID> - remove a skin from the list of skins of an item. xskin list <item shortname> - see a list of item skins. xskin clearlist <item shortname> - clear the list of item skins. xskin_c addcollection 000000 - add a collection of skins from the steam workshop. xskin_c removecollection 000000 - remove a collection of skins from the steam workshop. [ There is a check for repetition and emptiness of lists ] API
private void AddToBlacklist(ulong skinID, string pluginName) - to add the skin to the blacklist. private void AddToBlacklist(List<ulong> skinIDs, string pluginName) - to add a list of skins to the blacklist. Config
{ "Steam settings": { "Steam API Key": "" }, "General settings": { "Generate/Check and add new skins accepted by developers or made for twitch drops": true, "Generate/Check and add new skins added by developers [ For example, a skin for hazmatsuit ]": false, "Propagate blacklisted skins to repair bench": true, "Forbid changing the skin of an item that is not in the config": false, "Change skins to items after player respawns": true, "Enable default skin kits": true, "Enable personal skin kits": true, "1.1 Reset Admin skins from items if they are used by a player without permission": true, "1.2 Do not reset Admin skin if the player has it in the Steam inventory": true, "2.1 Reset Vip skins from items if they are used by a player without permission": true, "2.2 Do not reset Vip skin if the player has it in the Steam inventory": true, "List of commands to open the menu - 1": [ "skin" ], "List of commands to open the menu - 2": [ "skinkit" ], "List of commands to open the menu - 3": [ "skinentity" ], "List of commands to open the menu - 4": [ "skinitem" ], "Blacklist of skins that cannot be changed. [ For example: fire gloves, fire hatchet ]": [ 1742796979, 841106268 ], "List Admin skins": { "rifle.ak": [ 2428514763, 2431899986, 2802928155, 2551895055, 2957212973, 2976404884 ], "smg.mp5": [ 2468526014, 2966579723, 2590028692, 2354313222, 2558124512, 2432107615, 2351278756 ], "metal.facemask": [ 2976455803, 2972755707, 2960187815, 2963852242, 2462021937, 1658894467, 1539950759 ] }, "List Vip skins": { "hatchet": [ 2940068053, 2891473448, 1567848320, 1414450116, 1306286667, 1277610054, 1679923378 ], "pickaxe": [ 2940068876, 1672711156, 1624825406, 2637131316, 2837147224, 2775081117 ], "box.wooden.large": [ 1686318599, 1651859603, 1566044873, 1547157690, 1882223552, 2068573115, 2388451898 ] } }, "Default player settings": { "Change item skin in inventory after selecting skin in menu": true, "Change item skin in inventory after removing skin in menu": true, "Change skin on installed items/constructions [ /skinentity ]": true, "Allow friends to change the skin on items/constructions you installed [ /skinentity ]": true, "Change item skin when it is placed in the inventory by any means": true, "Change item skin only when pickup": false, "Do not reset item skin for which no skin is selected when it enters the inventory": false, "Change item skin when crafting": true, "Use skins with a spray can": true, "Enable sound effects in the menu [ Clicks ]": true, "[ True - Comfort menu | False - Default menu ]": false }, "Default skin kits setting": { "Blackout": { "metal.facemask": 2105454370, "metal.plate.torso": 2105505757, "hoodie": 2080975449, "pants": 2080977144, "shoes.boots": 2090776132, "coffeecan.helmet": 2120618167, "roadsign.jacket": 2120615642, "roadsign.kilt": 2120628865, "roadsign.gloves": 2530894213, "burlap.gloves": 2090790324, "jacket": 2137516645, "rifle.l96": 2473291137, "rifle.ak": 2128372674, "rifle.lr300": 2151920583, "rifle.bolt": 2363806432, "rifle.semiauto": 2267956984, "smg.mp5": 2887642987, "smg.thompson": 2393671891, "smg.2": 2879438786, "crossbow": 2178956071, "bow.hunting": 2192571819 }, "Whiteout": { "metal.facemask": 2432948498, "metal.plate.torso": 2432947351, "hoodie": 2416648557, "pants": 2416647256, "shoes.boots": 2752873720, "coffeecan.helmet": 2503956851, "roadsign.jacket": 2503955663, "roadsign.kilt": 2469019097, "roadsign.gloves": 2469031994 }, "Forest Raiders": { "metal.facemask": 2551475709, "metal.plate.torso": 2551474093, "hoodie": 2563940111, "pants": 2563935722, "shoes.boots": 2575506021, "coffeecan.helmet": 2570227850, "roadsign.jacket": 2570233552, "roadsign.kilt": 2570237224, "roadsign.gloves": 2575539874 }, "Desert Raiders": { "metal.facemask": 2475428991, "metal.plate.torso": 2475407123, "hoodie": 2503910428, "pants": 2503903214, "shoes.boots": 2510093391, "coffeecan.helmet": 2496517898, "roadsign.jacket": 2496520042, "roadsign.kilt": 2496523983, "roadsign.gloves": 2510097681, "rifle.ak": 2525948777, "smg.thompson": 2537687634, "rifle.semiauto": 2522121227 } }, "Permissions settings. Maximum number of personal skin kits": { "xskinmenu.kit12": 12, "xskinmenu.kit9": 9, "xskinmenu.kit6": 6, "xskinmenu.kit3": 3 }, "GUI settings": { "Layer UI - [ Overlay - above inventory | Hud - under inventory (to view installed skins without closing the menu) ]": "Overlay", "Refresh UI page after skin selection": true, "Refresh UI page after skin removal": true, "Display selected skins on homepage": false, "Display button to reset, all selected skins": true, "Display pages": true, "Display the button - Comfort menu [ + ]": true, "Close the menu by tapping on an empty area of the screen": false, "Icon - Kits": "assets/icons/clothing.png", "Icon - XBuildingSkinMenu": "assets/icons/construction.png", "Icon - Zoom": "assets/icons/add.png", "Material_background_0": "assets/icons/greyout.mat", "Color_background_0": "0 0 0 0", "Color_background_1": "0.517 0.521 0.509 0.95", "Color_background_2": "0.217 0.221 0.209 0.95", "Color_background_3": "0.1 0.1 0.1 0.975", "Color_background_4": "0.257 0.261 0.249 1", "Active category color": "0.53 0.77 0.35 0.8", "Inactive category color": "0 0 0 0", "Category button color": "0.517 0.521 0.509 0.5", "Settings buttons color": "0.517 0.521 0.509 0.5", "Button color (icons)": "1 1 1 0.75", "Item/skin block color": "0.517 0.521 0.509 0.5", "Selected skin block color": "0.53 0.77 0.35 0.8", "Active next/reset button color": "0.35 0.45 0.25 1", "Color of inactive next/reset button": "0.35 0.45 0.25 0.4", "Next/reset active button text color": "0.75 0.95 0.41 1", "Text color of inactive next/reset button": "0.75 0.95 0.41 0.4", "Active back button color": "0.65 0.29 0.24 1", "Back button color": "0.65 0.29 0.24 0.4", "Active back button text color": "0.92 0.79 0.76 1", "Back button text color": "0.92 0.79 0.76 0.4" }, "Menu settings": { "Enabled parameter icon": "assets/icons/check.png", "Disabled parameter icon": "assets/icons/close.png", "Enabled parameter color": "0.53 0.77 0.35 0.8", "Disabled parameter color": "1 0.4 0.35 0.8" }, "Category settings - [ Item shortname | Default item skin ]": { "weapon": { "gun.water": 0, "pistol.revolver": 0, "pistol.semiauto": 0, "pistol.python": 0, "pistol.eoka": 0, "shotgun.waterpipe": 0, "shotgun.double": 0, "shotgun.pump": 0, "bow.hunting": 0, "crossbow": 0, "grenade.f1": 0, "smg.2": 0, "smg.thompson": 0, "smg.mp5": 0, "rifle.ak": 0, "rifle.lr300": 0, "lmg.m249": 0, "rocket.launcher": 0, "rifle.semiauto": 0, "rifle.m39": 0, "rifle.bolt": 0, "rifle.l96": 0, "longsword": 0, "salvaged.sword": 0, "mace": 0, "knife.combat": 0, "bone.club": 0, "knife.bone": 0 }, "construction": { "wall.frame.garagedoor": 0, "door.double.hinged.toptier": 0, "door.double.hinged.metal": 0, "door.double.hinged.wood": 0, "door.hinged.toptier": 0, "door.hinged.metal": 0, "door.hinged.wood": 0, "barricade.concrete": 0, "barricade.sandbags": 0 }, "item": { "locker": 0, "vending.machine": 0, "fridge": 0, "furnace": 0, "table": 0, "chair": 0, "box.wooden.large": 0, "box.wooden": 0, "rug.bear": 0, "rug": 0, "sleepingbag": 0, "water.purifier": 0, "target.reactive": 0, "sled": 0, "discofloor": 0, "paddlingpool": 0, "innertube": 0, "boogieboard": 0, "beachtowel": 0, "beachparasol": 0, "beachchair": 0, "skull.trophy": 0, "skullspikes": 0, "skylantern": 0 }, "attire": { "metal.facemask": 0, "coffeecan.helmet": 0, "riot.helmet": 0, "bucket.helmet": 0, "deer.skull.mask": 0, "twitch.headset": 0, "sunglasses": 0, "mask.balaclava": 0, "burlap.headwrap": 0, "hat.miner": 0, "hat.beenie": 0, "hat.boonie": 0, "hat.cap": 0, "mask.bandana": 0, "metal.plate.torso": 0, "roadsign.jacket": 0, "roadsign.kilt": 0, "roadsign.gloves": 0, "burlap.gloves": 0, "attire.hide.poncho": 0, "jacket.snow": 0, "jacket": 0, "tshirt.long": 0, "hazmatsuit": 0, "hoodie": 0, "shirt.collared": 0, "tshirt": 0, "burlap.shirt": 0, "attire.hide.vest": 0, "shirt.tanktop": 0, "attire.hide.helterneck": 0, "pants": 0, "burlap.trousers": 0, "pants.shorts": 0, "attire.hide.pants": 0, "attire.hide.skirt": 0, "shoes.boots": 0, "burlap.shoes": 0, "attire.hide.boots": 0 }, "tool": { "fun.guitar": 0, "jackhammer": 0, "icepick.salvaged": 0, "pickaxe": 0, "stone.pickaxe": 0, "rock": 0, "hatchet": 0, "stonehatchet": 0, "explosive.satchel": 0, "hammer": 0, "torch": 0 }, "transport": { "snowmobile": 0 } } }

VIP Status is a powerful plugin that shows custom status messages for VIP players (3 different groups) on your Rust server.
With the user-friendly configuration options, you can customise the colours, icons and text of the VIP status message of all 3 VIP groups to suit your individual needs.
Plus, the plugin comes with a fully customizable language file, so you can translate the status message and other plugin texts into your preferred language.
But that's not all:
VIP Status is designed to be stable and reliable.
Unlike other plugins that use countdown timers to display the remaining time of a VIP status, VIP Status simply shows the expiration date and checks it against the player's permissions file at fixed intervals.
This approach ensures that the plugin operates smoothly without causing any lags or performance issues. Many other plugins that constantly perform countdown calculations can be processor-intensive and lead to performance drops. That's why we opt for static end times, eliminating the need for resource-heavy calculations every minute.
If you want to enhance the VIP experience on your Rust server and offer your players a premium status that stands out, VIP Status is the plugin for you.
Try it out today and see how it can elevate your server to the next level!
 
Please note that VIP Status requires the Free TimedPermissions plugin to function, as it relies on TimedPermissions to set and track the VIP expiration time.
If a player is a member of the VIP group but not listed in the TimedPermission file, the VIP status is now displayed without an expiry date. vip groups now possible for a maximum of 3 groups with different settings (pictures, colour etc.) as well as long file for all 3 groups Toggle the visibility of your VIP status.
Added new configuration option to display a custom status when the player does not belong to any group, as an example: no vip
 
Commands:
/vip -  List of Commands /vt - Toggle the visibility of your VIP status. /vi - Shows how long you have left on your VIP status  
Config:
{ "VIPGroups": [ { "Color": "0.66 0.66 0.66 0.8", "IconColor": "1.5 0.8 0.0 0.9", "ImageUrl": "https://i.ibb.co/hmC7s0y/vip1.png", "SubTextColor": "1 1 1 0.7", "TextColor": "1.5 0.8 0.0 0.8", "VipStatusId": "vip1" ///name of the vip group 1 }, { "Color": "0.30 0.66 0.66 0.8", "IconColor": "1.5 0.8 0.0 0.9", "ImageUrl": "https://i.ibb.co/yN18d6h/vip2.png", "SubTextColor": "1 1 1 0.7", "TextColor": "1.5 0.8 0.0 0.8", "VipStatusId": "vip2" ///name of the vip group 2 }, { "Color": "1.0 0.0 0.0 0.4", "IconColor": "1.5 0.0 0.0 0.9", "ImageUrl": "https://i.ibb.co/py0GJpj/vip3.png", "SubTextColor": "1 1 1 0.7", "TextColor": "1.5 0.8 0.0 0.8", "VipStatusId": "vip3" ///name of the vip group 3 } ], "ShowCustomStatusWhenNoGroup": false, ///set true to display a custom status when the player does not belong to any group. "NoGroupConfig": { "Color": "1.0 0.0 0.0 0.4", "TextColor": "1.5 0.8 0.0 0.8", "SubTextColor": "1 1 1 0.7", "IconColor": "1.5 0.8 0.0 0.8", "ImageUrl": "https://i.ibb.co/hmC7s0y/vip1.png" } }  
Lang:
{ "VIPStatusText_group1": "GROUP1", ///visible name of the vip group 1 "UntilText_group1": "until {0}", ///subtext for Group 1 with expire time "NoExpireText_group1": "Unlimited", ///subtext for Group 1 without an expiry date. "VIPStatusText_group2": "GROUP2", ///visible name of the vip group 2 "UntilText_group2": "until {0}", ///subtext for Group 2 with expire time "NoExpireText_group2": "Unlimited",///subtext for Group 2 without an expiry date. "VIPStatusText_group3": "GROUP3", ///visible name of the vip group 3 "UntilText_group3": "until {0}",///subtext for Group 3 with expire time "NoExpireText_group3": "Unlimited", ///subtext for Group 3 without an expiry date. "VIPStatusOn": "VIP status display turned on.", "VIPStatusOff": "VIP status display turned off.", "VIPStatusExpiration": "{0} expires on: {1}", "VIPStatusUnlimited": "{0} has unlimited VIP status.", "MessageCommandsListTitle": "List of Commands:", "MessageCommandVT": "/vt - Toggle the visibility of your VIP status.", "MessageCommandVIPInfo": "/vi - Shows how long you have left on your VIP status.", "NoGroupStatus": "No VIPs" /// text for the custom status when the player does not belong to any group. }  

Your players have a great opportunity to spend time completing different missions to get rewards! The list of possibilities is  incredible: In-game Events. Fights with players. Farming, Raidings, Crafting or taking action in Custom Events(The list of supported plugins will be below), and much more!

 
 
Description:
Welcome  to a world of unforgettable adventures that BattlePass can provide your users! This plugin has 30 levels that will entertain players in different ways. Let us plunge you deeper into the great atmosphere we have prepared for you!
 
How does it work?
You will get XP for accomplishing different goals, such as destroying the helicopter, raiding, and killing players, bots, or animals. Leveling up is also possible in a more peaceful way, too. For example, you can craft items, open boxes, and farm barrels and collect farm resources. Also, don’t forget that you can easily change parameters in the config file. Feel free to change the amount of XP awarded for missions.
 
What is the specialty of our BattlePass?
Support for custom events. The plugin interface looks like it was made by the game developers. Better performance. Detailed configuration of all actions in the config. The plugin has a system of permissions that will allow your server to receive additional earnings. You can configure players' access to rewards. You can also add different multipliers of getting EXP for different privileges. The reward system supports custom items and teams. Level 1 can have multiple rewards. You can change all the texts in the Lang file.  
Dependencies (optional, not required)
Arctic Base Event Satellite Dish Event Junkyard Event Plant Event Air Event Harbor Event Water Event Boss Monster Plugin Config
en  - example of plugin configuration in English ru  - example of plugin configuration in Russian
  My Discord:  CASHR#6906
Join the Mad Mappers Discord   here!
Check out more of my work  here!

NPC traders & shops Build a trader where you stand — the whole shop, in-game Walk to a spot, type one command, and a named NPC vendor is standing there wearing your outfit. Everything after that — every lot, price, skin, stock counter and wipe limit — is edited by looking at him and clicking. No JSON, no reloads, no restart. Pin him to a monument and he finds the same corner on every new map.
17 Fields per lot 3 Economy plugins supported 99 Lots per single purchase 1 Required dependency — zero on Carbon ✓ The whole shop is built in-game — add, reorder, copy and delete lots by clicking ✓ Traders pinned to monuments — the same vendor at the same spot after every wipe ✓ Stock that refills on a timer — and survives a restart at the count it was on ✓ Sell items, currency or commands — kits and ranks are just another lot ✓ On the map like a vending machine — players see the vendor and what he sells   Video See it in action     01 — The trader A vendor that belongs to your map Not a wooden box with a UI on it — a standing NPC with a name, an outfit and a place in the world.
Spawned where you stand, dressed like you One command drops a trader at your feet, facing where you face, wearing a copy of your clothes and holding whatever is in your hands. Change your own outfit later and one button re-copies it onto him — another button hands the set back to you. Pinned to a monument, not to coordinates Spawn him inside Bandit Camp, Outpost or any monument and his position is stored relative to it. Next wipe, on a completely different map, he stands in exactly the same corner of that monument — no repositioning, no re-spawning. Visible on the map, with his stock Toggle the vending marker and the trader shows up on the map under his display name, with his item-for-item lots listed on the map screen — exactly like a vending machine, so players know where to go and what for. Locked to a group, if you want Give a trader a permission and only that group can open him — with your own refusal message instead of the default one. A VIP-only black market is one field. Bulletproof, literally Traders can't be shot, damaged, targeted by NPCs or destroyed, and they aren't written into the map save — so they never duplicate, never leave corpses and never end up as debris in your save file.   02 — Lots and pricing Any price for anything A lot is three item slots — what's sold, what it costs, and an optional second cost. Each slot can be a real item, a skinned item, or your server currency.
Two-item prices Charge 500 metal and 20 scrap for one lot. Turn the second slot off with a single value when you don't need it. Currency in either direction Flip a slot to money and the lot is priced in ServerRewards, Economics or IQEconomic. Flip the sale slot to money instead and the trader buys from players — a scrap-to-cash buyback counter, same editor, no second plugin. Skins, custom names, custom icons Every slot takes a skin ID, so a skinned item is a different product with a different price. Override the display name, point the icon at any image URL, and attach a description of up to 2500 characters that players open with an info button. Buy in bulk without spam-clicking A per-lot multiplier from 1 to 99 with plus, minus and a typed field. It clamps itself to what the player can actually afford, what's left in stock and what their wipe limit allows, so the number on screen is always a purchase that will go through. Oversized results are split into proper stacks. Permission discounts Map any permission to a percentage. Discounted players see an OFF badge on the price and pay less on both price slots; stacked groups resolve to the single best discount. Copy a lot, or a whole shop Copy one lot or every lot at once, walk to another trader and paste. Reorder with arrows, delete with one click, and hit preview to see the shop exactly as a player will before you close it.   03 — Stock and limits Scarcity you can schedule An unlimited shop is a vending machine with extra steps. Two independent systems keep a trader from flooding your wipe.
Stock that ticks back up Per lot: a maximum stock, a refill interval in seconds and how much comes back each interval. Sell out and the button turns grey with OUT OF STOCK until it recovers. Ten rockets an hour, and the first player there gets them. Per-player wipe limits A separate cap on how many of a lot each player may buy for the whole wipe, counted per skin. One VIP kit per person per wipe, enforced without a second plugin and reset automatically on the next map. Counts survive a reboot Remaining stock, refill timers and everyone's wipe counters are written on every server save and on unload. A restart doesn't hand out a fresh batch of rockets.   04 — Beyond items Sell anything a command can do Kits, ranks, teleports, cars, raid bases — if another plugin exposes a command, it's a lot.
Run it now, or wrap it as a gift Put a command on a lot and choose: fire it the moment the purchase clears, or hand the player a wrapped present they can save, carry and unwrap whenever they want — the command runs on unwrap. Give it a name and an icon and it looks like a real product in their inventory. %steamid% is substituted for you. A command on the trader himself Fire a command every time a player opens a given trader — a greeting in chat, a quest check, a log line. Also keyed by Steam ID. Item search that finds things The item picker searches display names and shortnames as you type and shows icons, so filling a shop doesn't mean keeping a shortname list open on your second monitor.   Reliability Built to be left alone ✓ Oxide and Carbon — on Carbon the built-in image database is used and no extra plugin is needed at all ✓ Nothing is written into the map save — traders are recreated from config on boot, so they can't duplicate or survive as junk entities ✓ Clean unload — every trader is removed, open interfaces are closed for all players and stock is saved first ✓ One editor at a time — while an admin has a shop open it's locked for everyone else, so two people can't overwrite each other's lots ✓ A missing monument disables its trader with a console warning instead of dropping him into the ocean ✓ Optional 1-second buy cooldown against double-clicks and click macros   Commands Three admin commands, none for players All three require the npcshop.admin permission. Players never type anything — they walk up to the trader and press use. Command names are configurable.
/settrader Spawn a trader at your position, in your clothes /remtrader Look at a trader and delete him /newtraderpos Look at a trader to select him, walk to the new spot, then /newtraderpos update. cancel aborts, and /newtraderpos <display name> moves a trader by name from anywhere npcshop.admin Spawn, edit, move and remove traders npcshop.vip 15% discount by default — rename it, change the number, or add as many discount tiers as you like   Hooks & API For plugin developers void OnNPCShopItemBuy(BasePlayer player, Item saleItem, Item priceItem, Item additionalPriceItem) Fired after a successful item-for-item purchase, with the final amounts already multiplied and discounted. additionalPriceItem is null when the lot has no second price. Currency purchases don't raise it — track those through your economy plugin.   Questions Before you buy What do I need installed? On Oxide, ImageLibrary — it's free and the plugin tells you in console if it's missing. On Carbon, nothing. MonumentFinder is optional and only needed for monument-pinned traders. An economy plugin (ServerRewards, Economics or IQEconomic) is optional and only needed for money prices; the right one is detected automatically. Do my traders survive a wipe? Yes. Traders, lots and prices live in the config, so they come back on the new map. Monument-pinned ones land in the right place automatically; free-standing ones keep their world coordinates and may need one /newtraderpos if the terrain changed. Stock counters and per-player wipe limits reset on a new map, which is the point of them. Can players sell things to the trader? Yes, in both forms. Item-for-item barter is what a lot does by default, and setting the sale slot to money turns the lot into a buyback: the player hands over items and gets currency. Can I sell a kit, a rank or a teleport? Anything that has a command. Either it runs immediately on purchase, or the player receives a named, custom-iconed present that runs it when unwrapped — which also makes the purchase tradeable between players. How many traders and lots can I have? No limit on either. The shop interface scrolls, and lots are reordered with arrow buttons. Why don't all my lots show on the map marker? The marker is a real vending-machine listing, and Rust's own format can only express one item for one item. Lots priced in currency, or with a second price item, are hidden from the marker — they work normally in the shop itself. Can I run different shops for different groups? Yes. Each trader takes its own permission and its own refusal message, so a VIP trader can stand next to the public one and simply refuse everyone else. Do I ever have to edit the config file? Only for server-wide settings: discount tiers, the currency icon, the buy cooldown, and a trader's access permission or greeting command. Everything about the goods themselves — lots, prices, skins, names, icons, stock, limits, descriptions — is done in-game.