SoftArmy's Wishlist

Transform your Rust server's storage experience with intelligent automation, overflow chains, and PvP-safe raid protection.
 
🎯 Why SmartSorter?
For Players:
 
Stop manually sorting hundreds of items after raids, monuments and roams Never lose loot to overflowing boxes again Create custom filter categories for your skinned gear sets Set up once, automate forever  
For Server Owners:
 
Reduce player frustration and improve retention Performance-optimized for high-pop servers PvP-friendly with raid/combat blocking Admin-defined custom item categories for skinned items Zero dependencies - works out of the box  
🌟 What Makes It Unique?
🤖 Drop Box Automation
Mark any container as a "Drop Box" - toss items in and watch them automatically route to nearby filtered containers. No manual sorting needed.
🔗 Sorting Chains (Overflow System)
Link unlimited containers together. When one fills up, items automatically overflow to the next in the chain. Perfect for massive loot rooms.
🧩Custom Item Categories
Admins define custom categories for skinned items like "Raid Gear", "VIP Kits", or "Event Loot". Players filter containers by these categories just like vanilla ones. Category definitions persist across wipes while templates let players reapply setups instantly.
🛡️ Raid & Combat Protection
Full integration with RaidBlock, NoEscape, and CombatBlock - prevent sorting abuse during raids with granular control over what gets disabled. Essential for PvP servers.
🎯 Defense Auto-Fill
One-click filling of turrets, SAM sites, flame turrets, and shotgun traps. Set your preferred ammo/fuel amounts once and forget it.
📋 Smart Template System
Save filter configurations as templates, load them onto any container, and share setups across your base in seconds.
 
 
⚡ Core Features
Automatic Sorting
🎯 Drop Box system for hands-free organization 🔍 Category and item-specific filters (granular control) ✳️Custom item categories for skinned items (admin-defined) 📦 Works with 50+ container types ⚙️ Intelligent handling of furnaces, refineries, recyclers, and vending machines 🔄 Smart routing with sorting chains Manual Control Tools
📡 Send Near - Distribute inventory to nearby filtered containers within radius 📥 Send to Box - Fill the specific container you're looting 🚚 Dump All - Empty your entire inventory instantly 🎒 Loot All - Grab everything from a container (supports backpacks!) 📊 In-Container Sort - Organize by name or category with one click 🪄 Inventory and backpack Sorting
  Sorting Chains (Overflow System)
🔗 Link unlimited containers for automatic overflow routing 👁️ Visual chain inspection with in-game colored lines and spheres 🛡️ Cycle detection prevents infinite loops 👤 Per-player chain ownership 🎨 Configurable visualization duration and appearance Custom Item Categories
🏷 Admins create categories via /sscustomcat (e.g. "Custom Currency", "Custom Fuel", "Event Items") 🎨 Add specific skinned items by skin ID and display name 🔘 Players access custom categories through the "Custom" button in the filter panel 🔀 Toggle entire categories or individual items on/off 💡 Custom button reflects active state (green when filtering, gray when inactive) 💾 Category definitions stored in config and persist across wipes 📋 Per-container selections included in template save/load Defense Management
🔫 Auto-fill Auto Turrets, SAM Sites, Flame Turrets, Shotgun Traps ⚙️ Customizable ammo/fuel amounts per defense type 📡 Radius-based batch filling 🔧 Automatic weapon mounting for turrets 💾 Per-player preferences saved Raid & Combat Protection
🛡️ Integrates with RaidBlock, NoEscape, and CombatBlock 🎚️ Granular control - disable specific features during raids/combat 💬 Optional chat notifications when actions are blocked ✅ Essential for PvP servers - prevents sorting abuse Template System
💾 Save filter configurations by name 📋 Load templates onto any container instantly 🔄 Share setups between boxes 👤 Per-player template ownership with admin override 🗑️ Easy template management (delete, rename) Player Preferences
🎛️ Toggle auto-opening of filter panels (/ssautofilters) 📏 Minimize UI to compact button mode ⚙️ Per-player defense ammo/fuel settings 💾 Settings persist across sessions Visual Interface
🎨 Dynamic context-aware UI (changes based on container type) 📖 Built-in help system with full-color image guides 🎨 Fully customizable layouts, colors, and button positions 📱 Responsive design adapts to 1-column or 2-column layout 🖼️ ImageLibrary support for item icons 🔧 Technical Specifications
Supported Containers (50+)
Storage boxes, large boxes, coffins, barrels, fridges, lockers, tool cupboards, vending machines, furnaces (all types), refineries, recyclers, BBQs, campfires, lanterns, mannequins, drop boxes, wall cabinets, beehives, chicken coops, composters, cauldrons, stashes, and all defense entities.
Performance Optimized
⚡ Configurable processing intervals 🔢 Batch processing limits (MaxDirtyBoxesPerTick) 🚀 Optimization mode for high-population servers 💾 Efficient memory pooling throughout 🧹 Automatic cleanup of deleted container data Framework Compatible
✅ Full support for uMod/Oxide ✅ Native Carbon framework support ✅ No external dependencies required ✅ Works out of the box Safety Features
🔒 Wall-check system (prevent looting through walls) 🏗️ Building privilege requirement 📝 Configurable item blacklist/whitelist 🗑️ Automatic cleanup of old container data (configurable grace period) 🔐 Permission-based access control ⚙️ Configuration Highlights
1000+ Customization Options
🎨 UI Customization: Every color, position, size, and text label 🎛️ Button Layouts: 4 preset layouts (Default, DropBox, Awaiting, HasChain) ⏱️ Timing: Sort delays, cooldowns, debounce intervals 📏 Distances: Default radius, visualization settings 🎯 Category Overrides: Reclassify any item into any category ☣️Custom Items: Define skinned item categories with skin ID and display name 🔧 Furnace/Refinery: Custom fuel and smeltable item lists  



🆘 Support & Updates
📖 Documentation: Built-in visual help system 🔄 Active Development: Regular updates and improvements 🐛 Bug Reports: Fast response on CodeFling 💡 Feature Requests: Always welcome 📦 What's Included
✅ Plugin file (.cs) ✅ Default configuration ✅ Built-in help system with images ✅ Full permissions setup ✅ 50+ container support ✅ Custom item categories system ✅ Raid/combat block integration ✅ Template system ✅ Performance optimization ✅ Extensive customization options 🎯 Perfect For:
🏰 Large Base Builders - Automate loot rooms with chains ⚔️ PvP Servers - Raid block integration prevents abuse 👥 High-Pop Servers - Performance optimized 🎮 Casual Servers - Quality of life improvement 🏆 Modded Servers - Works with custom items  
PLAYER COMMANDS
/ss or /smartsorter Opens the visual help guide UI
/sshelp Opens the visual help guide UI (same as /ss)
/sscommands Shows a list of all available chat commands
/sstoggle Shows or hides the SmartSorter UI completely
/ssremovechains Removes ALL sorting chains you own
/ssautofilters [on|off] Toggles whether the filters panel auto-opens when looting filtered containers
/ssrefresh Refreshes the UI if it gets stuck or doesn't display properly
/ssshowchains Visually displays your sorting chains for 15 seconds using colored lines and spheres
/ssdefense Opens the defense configuration panel to set ammo/fuel amounts for turrets and traps
 
ADMIN COMMANDS
/sscustomcat Opens the custom item category admin UI
/ssdebug on|off Enables or disables debug logging in console
/ssreloadconfig Reloads the configuration file from disk
/ssclearfilters <containerID> Clears all filters on a specific container by NetworkID
/ssconfig [setting] [value] Opens the config UI, or sets a specific config value

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
smartsorter.use - Required for all features
smartsorter.admin - Admin commands and config access
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
DEPENDENCIES
None required. Optional ImageLibrary support for enhanced item icons.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
Give your players the gift of time. Install Smart Sorter today.
 
 

 
 

Video :
 
   Features : - Randomized loot respawn intervals, configurable for each monument. Example:
{ "Monuments": { "ferry terminal": { "Allowed Groups": [ "red", "blue", "green", "crate", "barrel", "elite", "diesel", "loot_barrel" ], "Respawn Max Time": 600, "Respawn Min Time": 300 }, "fishing village": { "Allowed Groups": [ "red", "blue", "green", "crate", "barrel", "elite", "diesel", "loot_barrel" ], "Respawn Max Time": 600, "Respawn Min Time": 300 } } }
- Default respawn time is set between 30-60 minutes but can be fully adjusted through the configuration.
 
- Automatically removes monuments that no longer exist after a server wipe, keeping the configuration clean and up-to-date.
Supported Crates [ Not only the containers shown below , almost every container in the game is now supported! ]:
Supported Monuments :

All Game Monuments
   Additional Settings : { "General": { "Enable When Player Dont Finish Looting Containers Will Drop Loot On Ground": true } }

Complete tier 3 package for the Raidable Bases plugin. Core plugin sold separately.
 
PLUGIN SOLD SEPARATELY
This package includes everything you need to avoid the hassle of having to setup the plugin from scratch.
Time is money, and not having to spend hours or days setting everything up is a game changer.
All bases can be viewed in the gallery at the top of this page.
This is the perfect package with a massive 50 base collection surely to wow your players!
Included:
10 bases (copypaste files) for every difficulty which are now unique to tier 1 and tier 2 difficulty loot tables for each difficulty base loot tables for every profile profiles for each difficulty the configuration file all bases are unique to tier 1 and 2 easy to understand instructions Free version note:
The free version can use this tier package, but it only supports one difficulty (Normal) and one Base Loot file. Remove all Base Loot files except the one you want all bases to use. You must also bypass the protection that prevents paid files from loading with the free version, which exists to stop paid users from accidentally erasing paid-only options by installing the free version over them. To bypass it intentionally, edit the config and rename the "Buyable Events" section on line 283 to "blah" or anything else. After that, the package will load with the free version. The paid version does not have these limitations and supports Easy, Medium, Hard, Expert, Nightmare, and custom difficulties. The tier package is still useful with the free version as it includes preconfigured files, copypaste files and works well for servers that manually enable and disable profiles to rotate through harder bases as the wipe progresses.
Paid plugin sold separately.
Instructions (available in zip file)
 

Create fully automated raidable bases with NPCs in Rust.
Raidable Bases supports maintained, scheduled, buyable and manually spawned events, with separate options for each difficulty.
📄Compatibility notes
server.pve true is not supported; please use TruePVE or another compatible PVE plugin that calls the necessary hooks required by Raidable Bases. Raidable Bases does not currently use Harmony patches. I could implement such patches, but it's often better to use a supported hook when it exists instead. Raidable Bases is not compatible with Raid Windows in Softcore mode after the Tool Cupboard is destroyed or after raidwindow_fresh_tc_seconds elapses. This will be supported when the appropriate hooks exist for this behavior. 📄Raidable Bases & Boats Loot Editor by @beee 😎
This is the easiest way to create and manage Raidable Bases loot tables. It provides a visual editor for item selection, amounts, probability, skins and other loot fields, making it the best starting point for most server owners.
https://codefling.com/tools/raidable-bases-boats-loot-editor/ ⚙️Built with performance in mind
Raidable Bases manages a lot of work behind the scenes, so performance is treated as a core part of development. Pasting and cleanup are batched, recurring work is shared through central schedulers, temporary collections are pooled, and spawn searches are spread across frames to reduce noticeable spikes.
These systems help provide a smoother experience across a wide range of server sizes. Performance will continue to be reviewed and improved anywhere measurable gains can be made.
📄There are just a few steps
Get bases spawning within minutes
An experienced administrator may finish in a few minutes. A novice should allow roughly 30 minutes, while a complete beginner may need 60 to 120 minutes. Fine-tuning depends on how large you want the project to become. Once the initial setup is complete, maintaining the plugin is fairly simple, and growing your base catalog becomes an art form of its own. Server owners regularly report that players love the variety, which makes building that collection rewarding for everyone involved.
Step 1 - Add your bases
You can obtain bases by:
Downloading them from Fortify. Purchasing a Raidable Bases package. Purchasing compatible CopyPaste files from another creator. Creating your own bases. Place the CopyPaste JSON files in:
Oxide — oxide/data/copypaste/ Carbon — carbon/data/copypaste/ Step 2 - Set up profiles
Profiles serve a specific purpose: they extend the main configuration file. For clarity, they should always be referred to as profiles.
Profiles are located in:
Oxide — oxide/data/RaidableBases/Profiles/ Carbon — carbon/data/RaidableBases/Profiles/ Bases can be added manually or with the command:
rb.config add "Easy Bases" raideasy1 raideasy2 raideasy3 rb.config add "Medium Bases" raidmed1 raidmed2 raidmed3 The named profile can contain any number of CopyPaste bases that share its options. Quotes around the profile name are required, and it is best practice to use them even when the name has no spaces. Use straight double quotes only; curly quotes will not work correctly.
Step 3 - Enable automatic events
For public automated events, enable Maintained Events or Scheduled Events in the main configuration and choose how many events you would like active.
The main configuration file is located in:
Oxide — oxide/config/RaidableBases.json Carbon — carbon/configs/RaidableBases.json Edit the configuration file.
Maintained Events: keeps the configured number of raids available. Max Maintained Events: Set this to the amount of events that you want to always have spawned. Max Amount Allowed To Automatically Spawn Per Difficulty: Set this to the amount of events that you want to spawn per difficulty. Scheduled Events: spawns raids according to a timer. Max Scheduled Events: Set this to the amount of events that you want spawned on a timed basis. Max To Spawn At Once: Set this to the amount of events that can spawn at once from Max Scheduled Events. Set to 0 to use the full amount from Max Scheduled Events. Step 4 - Save your files then use the commands:
Oxide: o.reload RaidableBases Carbon: c.reload RaidableBases Shortcuts: rb.reloadconfig rb.reloadprofiles Once grid initialization completes, automatic events can begin spawning. The included Default_Loot table is enough to get started and can be replaced whenever you are ready. Ultimately, the Default_Loot table should be discarded once your other loot tables are configured.
📁File locations
Main configuration
Oxide: oxide/config/RaidableBases.json Carbon: carbon/configs/RaidableBases.json Profiles
Oxide: oxide/data/RaidableBases/Profiles/ Carbon: carbon/data/RaidableBases/Profiles/ CopyPaste bases
Oxide: oxide/data/copypaste/ Carbon: carbon/data/copypaste/ Loot and data
Oxide: oxide/data/RaidableBases/ Carbon: carbon/data/RaidableBases/ The main configuration controls server-wide behavior. Profiles contain options for specific difficulties, while loot tables and CopyPaste files provide the content used by each event.
🗺️Map terrain and spawn locations
Raidable Bases depends on the map having enough flat, unobstructed terrain for automated events. Most procedural maps provide plenty of locations, while custom or heavily modified maps may need additional flat terrain, islands, or custom spawn points.
The grid scans the map when the plugin initializes and reports the number of potential spawn locations. A low location count usually means the map offers fewer suitable areas or the current settings narrow the available terrain. Spawns Database files are useful for sky bases, underwater bases, custom maps and any setup that needs exact locations. You can disable using the grid by providing a valid spawn file for each raid type (buyable, maintained, scheduled and manual). You may view the grid by typing /rb grid in-game to view detailed drawings of all locations on the grid.
X - Green - Potential spawn point, generally in clusters X - Red - Currently in use C - Cyan - Construction detected nearby TC - Yellow - TC detected nearby W - Blue - Water depth is too high - Refreshes on ocean level change Green clusters have the highest chance of being picked as a spawn point, constantly changing depending on player activity and remaining a safe distance away.
📄Profiles and difficulties
A profile is where options can be found that pertain to specific difficulties. Any number of CopyPaste bases can share the same profile, so a large base rotation can be managed while the difficulty is adjusted in one place.
Profiles can control loot, NPCs, PVP or PVE behavior, protection radius, damage, doors, locks, water placement, height, rewards, building options and much more. Dynamic difficulties
rb.difficulty add "Sky" rb.difficulty remove "Sky" Adding a difficulty creates the matching configuration and language entries. Profiles and loot tables can then be assigned to it. Removing a difficulty removes its active configuration entries without deleting the related files.
📄Event types
Maintained — Keeps up to the configured number of public raids available. Another can spawn after one despawns. Scheduled — Spawns public raids between the configured minimum and maximum interval. Buyable — Lets players purchase a raid through the configured buy command, subject to availability, costs and cooldowns. Manual — Lets an administrator spawn a selected raid at a chosen location. Each event type can use the automatic grid or its own Spawns Database file.
🔧Loot tables
Loot can come from a base-specific table, difficulty table, weekday table and the default table. The plugin combines the available sources according to the profile and loot settings until it has enough usable entries.
Default loot
Default_Loot.json contains a small demonstration loot list. It is enough to show how the plugin works, but most servers should replace it with loot tables in the Base_Loot and/or Difficulty_Loot folders. Loot table editor
For most servers, the Loot Table Editor by @beee 😎 is the quickest way to build and manage these files. Thanks, beee!
https://codefling.com/tools/raidable-bases-boats-loot-editor/ Important loot fields
shortname — Rust item shortname. amount — Maximum amount created for the entry. amountMin — Minimum amount created for the entry. probability — Spawn chance from 0.0 to 1.0, where 1.0 is 100%. stacksize — Optional stack-size override. Use -1 to use the item's normal Rust stack size. skin — Optional skin ID. Editable item lists
The rb.populate all command creates a file for each difficulty inside the Editable_Lists folder. Each file contains every available Rust item, allowing you to remove unwanted entries and configure the amounts for items you would like to spawn. Any items with an amount set to 0 will be inactive, so you do not have to remove any entry.
A list containing hundreds of items may look intimidating at first, but deleting unwanted entries or configuring from a preset list is usually much faster than adding every item manually. The command also includes items already present in your Difficulty_Loot files. This makes it useful when you want to rebuild a list and reevaluate which items should be available later. Files inside Editable_Lists are for editing only. Their contents need to be copied into an active loot file before the plugin will use them.
To use Editable_Lists/Easy.json for Easy raids, copy its contents into Difficulty_Loot/Easy.json. To use Editable_Lists/Expert.json for a profile named Expert Bases, copy its contents into Base_Loot/Expert Bases.json. Item amounts and probability
An item will not spawn when both amount and amountMin are set to 0. You may remove these entries or leave them in the file for later use.
When amountMin is 0, probability determines whether the item spawns. If the item fails its probability check, another item will not automatically replace it unless additional eligible entries are available. Tool Cupboard loot
Items moved into the Tool Cupboard may combine into larger stacks. The visible stack count can therefore be lower than the amount that was originally generated. Loot priority
Loot is loaded from the data files inside:
Oxide: oxide/data/RaidableBases/ Carbon: carbon/data/RaidableBases/ The Profiles folder is not a loot source. It contains the options used by each profile and difficulty. Please do not place any file in the Profiles folder that is not a profile, the hamsters will cry.
Base Loot
If a file inside Base_Loot has the same name as a profile, the bases assigned to that profile can use that loot table. For example: Base_Loot/Expert Bases.json applies to the profile named: Expert Bases Enable Always Spawn Base Loot Table in the profile when items from that table should always be included. Difficulty Loot
Files inside Difficulty_Loot are selected according to the difficulty assigned to the profile. For example: Difficulty_Loot/Hard.json is used by profiles assigned to the Hard difficulty. Day of Week Loot
When Use Day Of Week Loot is enabled, the plugin selects the loot table matching the current day. Default Loot
Default_Loot.json acts as the fallback table. It is used when the other available loot tables do not provide enough eligible items to satisfy Amount Of Items To Spawn. Generally, this file should be discarded once Base Loot and Difficulty Loot tables have been created. 🤖NPCs
Profiles include NPC options for scientists, murderers and sleepers. You can keep the defaults or tailor their amount, health, accuracy, kits, movement and loot to suit each difficulty.
Valid Kits entries take priority over the matching manual loadout lists. NPCs spawned inside bases remain stationary, while outdoor NPCs can roam and engage players around the event. More NPCs naturally create more work, so busy servers may prefer to increase counts gradually. ⚔️PVP, PVE, ownership and raid options
Raid behavior is controlled by a combination of profile options and server-wide configuration. Together, these determine whether a raid is PVP or PVE and can control ownership, team or clan access, building, teleporting, cupboard access, damage across the dome, PVP delay, completion requirements and rewards.
Ownership and participation
Public raids can lock to the first attacker, while purchased raids can remain associated with their buyer. Players may become participants by damaging the base, killing NPCs, looting or using other supported raiding methods. PVP delay
PVP delay can keep a player temporarily vulnerable after leaving a PVP raid. This discourages zone hopping across the event boundary to gain an unfair advantage on a PVE server, where normal protection would otherwise resume immediately after leaving. 🛒Buyable raids and shop plugins
Buyable raids use the configured buy command, commonly /buyraid. A purchase can still be declined by cooldowns, ownership options, event limits, permissions, availability or the inability to find a suitable location.
Using a shop plugin (support is not guaranteed)
The shop should provide the buyraid command for free or at zero cost, while Raidable Bases handles the actual payment and any refund. This allows the plugin to safely return the payment when the raid cannot be created. Shop plugins that cannot sell the command at zero cost are not supported. buyraid 0 <steamid> The player placeholder depends on the shop plugin. Prices are configured in Raidable Bases and should remain zero in the external shop. ⚙️ Options that benefit from an explanation (the majority have names that are meant to be self-explanatory to save time)
The complete configuration already lists every available option. This section only covers settings that are easier to understand with a little context.
Advanced Protection Radius — Controls the event area used by domes, markers, damage checks, ejection, NPC ranges and nearby spawn checks. Configurable per event type: Buyable Events, Maintained Events, Manual Events, and Scheduled Events. Amount Of Items To Spawn — Sets the target amount of generated loot, limited by available entries from your loot tables and container space in each base. Divide Loot Into All Containers — Spreads generated loot across the raid's available containers. This does not serve much purpose when disabled, it is advised to keep it set to true. Create Dome Around Event Using Spheres — Creates the visible event boundary. Set to 0 to disable it. Spawn Silently — Hides the normal announcement, dome and map marker for the profile. Height Adjustment Applied To This Paste — Adds the same vertical offset whenever a base using this profile is pasted. Forced Height — Uses a fixed world height for controlled sky or special-event setups. Allow Players To Raid With Items Up To What Workbench Level? — Limits raiding items according to their workbench level. Water Settings — Controls floating, surface, underwater and seabed placement. Workbench-level option
-1 — No workbench-level limit, future-proof where level 3 may be increased to 4 in a later Rust update. 0 — Allows raiding items that require no workbench. 1 — Allows items up to Workbench Level 1. 2 — Allows items up to Workbench Level 2. 3 — Allows items up to Workbench Level 3. The plugin checks the available workbench information for weapons, ammunition, attack entities and projectiles. A player is notified when the item being used exceeds the profile's allowed level.
⌨️Commands and permissions
Many command names are configurable. The examples below use their common defaults.
/buyraid — Open or use the buyable raid system. /rb — View player-facing raid information and available subcommands. rbe [base] [difficulty] — Spawn a manual event using the configured event command. rb.config add "<profile>" <bases...> — Add CopyPaste bases that share the selected profile options. Straight quotes around the profile name are required. rb.config list — List configured bases. rb.config remove <base> — Remove a configured base. rb.config maintained — Toggle Maintained Events. rb.config scheduled — Toggle Scheduled Events. rb.reloadconfig — Reload the main configuration. rb.reloadprofiles — Reload profiles. rb.reloadtables — Reload loot tables. rb.populate all — Create editable item reference lists. rb.difficulty add "name" — Create a new difficulty and its matching configuration entries. rb.difficulty remove "name" — Remove a difficulty from the active configuration without deleting its files. Players do not require permissions by default. Administrative permissions are best limited to trusted administrators, moderators and staff only.
raidablebases.allow — Allows player to use the available ADMIN commands. This is NOT recommended as players can use the commands 'buyraid' and 'rb' already. raidablebases.canbypass  — Bypass dome restrictions. Noclip or vanish will bypass many features too, so you can assist players without interfering. raidablebases.blockbypass — Bypass Owning More Than One Raid settings for Clans/Friends/Teams raidablebases.mapteleport — Teleporting to map marker now simply requires this permission and to be enabled in config raidablebases.ddraw — Allows support for direct draw to players. raidablebases.config — Allows access to rb.config command in-game (server console does not require this permission) raidablebases.banned — Bans the user from entering any raids - accidentally banned yourself? Use /rb unban raidablebases.durabilitybypass — Bypass `Block Plugins Which Prevent Item Durability Loss` raidablebases.notitle — Exclude users from ranked title rewards raidablebases.buyraid — Optionally require this permission with `Use Permission (raidablebases.buyraid)` (not required by default) See other permissions using Permissions Manager (click the link to visit the page on Codefling) 🧾RBE DEBUG 
The RBE DEBUG command displays information related to the configuration, profiles, map and spawn checks. Using it before requesting support usually makes the cause much easier to identify.
Too much information displayed at once? Not a problem, it is constantly recording data but the solution is very simple. Run RBE DEBUG once to enable it, then run it again to disable it and clear the previously recorded data. Next, attempt to spawn the raid using /buyraid or /rbevent Run RBE DEBUG again to view any newly recorded information. Do this promptly, as it will immediately continue to record. When you are finished, toggle it off by typing the command again. It will continue to output debug until it is turned off. Helpful information to include
Raidable Bases and CopyPaste versions. The base filename, profile, difficulty and event type. The command used and relevant console output. Whether the same file works when pasted directly with CopyPaste. Map seed, size and whether the map is procedural or custom when the issue involves placement. Debug contains all relevant information to events, good or bad. Use this information to determine what is happening and how to resolve the issue on your own. 📄Facepunch Terms of Service
Raidable Bases includes safeguards designed to help servers remain compliant with Facepunch policies for paid DLC items and restricted cosmetic content. These safeguards may remove restricted deployables or loot and prevent unauthorized pickup.
Server-owner responsibility
Changes that disable or bypass these safeguards can place a server outside Facepunch policy. Custom loot tables, imported workshop skins, CopyPaste files and third-party content should be reviewed before use. 🧰Tools and further reference
Community-made Facepunch content checker by ninco90: https://app.rustspain.com/facepunch/checkitems Loot Table Editor: https://codefling.com/tools/raidable-bases-boats-loot-editor/ 🧩Developer API
Signatures reflect Raidable Bases 3.1.5
The following hooks receive this argument set: OnRaidableBaseStarted, OnRaidableBaseEnded, OnRaidableBasePrivilegeDestroyed, OnRaidableBaseDespawn, OnRaidableBaseDespawned and one overload of OnRaidableBaseCompleted and OnRaidableAwardOwner. Please note that unused args will be removed in a future update.
object[] raidData = { Vector3 location, int level, bool allowPVP, string id, float unused1, float unused2, float loadTime, ulong ownerId, BasePlayer owner, List<BasePlayer> raiders, List<BasePlayer> intruders, List<BaseEntity> entities, string baseName, DateTime spawnDateTime, DateTime despawnDateTime, float protectionRadius, int lootRemaining }; OnPlayerPvpDelayStart, OnPlayerPvpDelayReset and OnPlayerPvpDelayExpired receive this argument set.
object[] delayData = { BasePlayer player, ulong userid, int level, Vector3 location, bool allowPVP, string id, ulong ownerId, string baseName, DateTime spawnDateTime, DateTime despawnDateTime, int lootRemaining }; Event hooks
Purchase, ownership, backpack, and other special hooks
Callable API methods

XDQuest: A comprehensive and customizable quest system for your RUST server!
XDQuest is a powerful and flexible plugin that introduces a comprehensive and dynamic quest system into your game world.
With 31 different types of missions available for players, the possibilities are almost limitless.
Players receive various rewards for completing missions, adding even more incentive to accomplish tasks.
At the moment, this is the largest and only quest system available!
XDQuest is your key to creating endless adventures in the world of RUST.
List of features:
(The description briefly outlines the functionality and includes screenshots.)

Interactive website for creating quests:
XDQuest-Creater - On my website, you can easily and quickly create quests. Forget about manually editing JSON files — my user-friendly interface will make the quest creation process simple and enjoyable!
The plugin offers four types of rewards:
Items Blueprints Custom items Commands It integrates perfectly with various economic systems, and also supports Skill Tree and ZLevels.

List of missions
Mission setup
Reward setup Detailed instructions and settings on the website:
XDQuest-Creater - My website features clear and informative instructions that will help you configure the plugin and master all types of missions.
You will gain access to it immediately after purchasing the plugin.

Discover the simplest and most effective way to configure using my guide!
Beautiful and modern UI:
The stylish and intuitive interface makes using XDQuest simple and enjoyable.
There is a mini-quest list that allows your players to remotely track the progress of their missions.

UI
UI
Mini quest list
Example of UI customization
(Rusty Wasteland PvE)
Capabilities and NPC settings:
NPCs have their own voice-overs; currently, they can respond to the user on 4 triggers:
1.Greetings
2.Farewells
3.Task acceptance
4.Task completion You can also upload and use your own sounds for any of these 4 triggers, and the website will assist you with this as well. Dress your NPC however you like and create a unique appearance for them. There is an option to change the location of the NPC. Your NPC resides in a unique dwelling created in accordance with their character and backstory. Available types of missions:
Currently, there are 24 different types of tasks available:
(The types of missions are constantly being updated)
(16 pre-set quests included)
Command:
Chat commands: /quest.saveposition - saves a custom position (available only to administrators). /quest.saveposition.outpost - saves a custom position within the bounds of a peaceful town (available only to administrators). /quest.tphouse - teleport to a building (available only to administrators). Console commands: xdquest.stat - publishes statistics. xdquest.player.reset [steamid64] - Clears all of a player's missions and everything associated with them. Configuration:

Discord  -  DezLife
Website editor  -  xdquest.skyplugins.ru