Jump to content
Community collections
Collections curated by the community
Explore curated groups of files assembled by the community to help you discover tools and resources that work well together.
View Collections
$14.99
TC Upgrades provides an efficient and optimized way to enhance your base directly from the Tool Cupboard. With this plugin, you can easily change building grades, switch building skins, repair structures or deployables, and even set up wallpapers on your base, streamlining your base management process. ⭐ Key Features Multi-TC Support Authorization List on Tool Cupboard Upgrade Building Grades Change Building Skins Repair Structures and Deployables Apply Wallpapers Shows Required Upgrade materials NEW! Change Doors skins from tc directly Detailed Permissions VIP Features User-Friendly UI  🎉Game hosting perfected, that's Physgun Join the thousands of server owners using Physgun to take their game server communities to the top. 🎬 Video Showcase 📜 Permissions TCUpgrades.admin- Shows a UI Change button when in admin mode (command: /tcuadmin) TCUpgrades.authlist - Shows Authorization list button  on TC TCUpgrades.upgrade -  Shows upgrade button  on TC TCUpgrades.repair - Shows repair button  on TC TCUpgrades.skin - Shows skin button  on TC TCUpgrades.wallpaper -  Shows wallpaper button  on TC TCUpgrades.upgrade.nocost - Allows player to use no resources when upgrading TCUpgrades.repair.nocost -  Allows player to use no resources when repairing TCUpgrades.reskin.nocost - Allows player to use no resources when reskining TCUpgrades.wallpaper.nocost -  Allows player to use no resources when setting wallpaper TCUpgrades.default - Allows player to use (wood, stone, metal, hqm & deploy)   TCUpgrades.wood  TCUpgrades.stone TCUpgrades.metal TCUpgrades.hqm TCUpgrades.deploy TCUpgrades.TCSkin - Allows player to use Tool Cupboard skins TCUpgrades.WallandGates - Allows player to External Gate skins TCUpgrades.DoorSkins - Allows player to place door skins ⚙️ Configurations 🗃️ Language EN 💬 Support          
4.8
Upgrade the tier-1 monuments on your server with custom-built Blue Keycard Puzzle Rooms for both the Supermarket and Oxum’s Gas Station! Naturally, these starter monuments only offer basic green card setups or loose loot. This plug-and-play configuration transforms their doors into fully operational blue card puzzle rooms, giving your players a thrilling progression step and a reason to fight over these unused spaces. Perfect for adding depth to low-tier areas without cluttering your map with completely custom monuments! Features Seamless Integration: Designed to perfectly fit the existing vanilla doors inside and outside the Supermarket and Gas Station. Progressive Gameplay: Upgrades these standard areas into blue keycard puzzle destinations requiring an active fuse/card setup. Customized Loot Tables: Packed with various loot crates (such as military crates, tech crates, and toolbox) to make completing the puzzle highly rewarding. Optimized Performance: Uses native monument assets and zero-friction entity placement to ensure zero impact on server performance or FPS drops. Plug & Play: Easy installation via standard monument plugins. The loot will be based on your own loot table! Im using my 2x table in the videos that can be found here: Link Supermarket Blue Room Configuration: Actives the locked back-room doors, turning the storage area into a high-tier loot closet. Gas Station Office/Restroom Puzzle: Restores functionality to the office space, turning the tiled backrooms into a secure crate cache. Video of the config:   
5.0
sale
This is a custom package designed by us, featuring 210 unique bases and a specialized loot setup for five different difficulty levels, ranging from Easy to Nightmare. Note:  The building skins in the package showcase images may differ from the spawned bases or use the default building skin. This MEGA PACK is an upgraded version of the FullWiped-110 Bases + Loot Pack we previously offered. If you've already purchased the FullWiped-110 Bases + Loot Pack, you only need to buy the expansion pack, which includes 100 new bases ranging from Easy to Hard. Get it here:  https://codefling.com/bases/raidable-bases-pack-100-bases-expanded-package-from-easy-to-hard Warning: The Raidable Bases plugin requires the Copy Paste plugin to function. You must install both for this bases pack to work. 🔗Raidable Bases (Paid): https://codefling.com/plugins/raidable-bases 🔗Copy Paste (Free): https://umod.org/plugins/copy-paste This Raidable Bases Pack & Loot Tables package includes: 🏡70 Easy Bases            +🗡️Base_Loot Tables   (Easy "Vanilla" and "Enhanced" tables included) 🏡60 Medium Bases       +🗡️Base_Loot Tables   (Medium "Vanilla" and "Enhanced" tables included) 🏡60 Hard Bases            +🗡️Base_Loot Tables   (Hard   "Vanilla" and "Enhanced" tables included) 🏡10 Expert Bases          +🗡️Base_Loot Tables   (Expert "Vanilla" and "Enhanced" tables included) 🏡10 Nightmare Bases   +🗡️Base_Loot Tables   (Nightmare "Vanilla" and "Enhanced" tables included) Beware:   Our loot table package includes only the 5-tier loot tables within the Base_loot folder, ranging from easy to nightmare. It does not include the loot tables from the Difficulty_Loot or Weekday_Loot folders.   VANILLA AND ENHANCED LOOT TABLES FOR RAIDABLE BASES This package includes 10 different base loot table files, ensuring a well-structured and advanced configuration for every difficulty level, from Easy to Nightmare. - 5 loot files for the Vanilla setup (Easy, Medium, Hard, Expert, Nightmare), offering a balanced loot experience with some junk items, staying close to a 1x rate. - 5 loot files for the Enhanced setup (Easy, Medium, Hard, Expert, Nightmare), designed for modded servers with 2x, 3x, or higher gather rates, featuring cleaner loot tables with minimal junk and more valuable rewards. 📁Installation Path: All loot table files are intended for the 📁/oxide/data/RaidableBases/Base_Loot directory. ⚠️Setup Requirement: You must choose and install only one loot table setup at a time—either Vanilla or Enhanced. If you want to switch, you can replace the current files with the other set, but both cannot be active simultaneously. For those exclusively seeking the loot table, we offer it as a standalone product:  https://codefling.com/customizations/raidable-bases-loot-tables-pack (Note: If you've purchased our Raidable Bases Mega Pack & Loot Tables (210 Bases)  package, there is no need to buy this separately.) WARNING: TWO DIFFERENT INSTALLATION METHODS (PLEASE READ BOTH AND APPLY ONLY THE ONE THAT FITS YOUR NEEDS) ⚙️INSTALLATION GUIDE 1: (If you do not have a custom configuration and are not a professional in server configurations, choose this option. However, if you already have your own configuration and profile settings and do not wish to use the optional configs we provide—in other words, if you only need the bases and loot tables—use the second installation guide instead.) ▶  Step 1: Place the Config File From the extracted ZIP files, locate the config folder and find the RaidableBases.json file. Move it to the following directory: 📁/serverfiles/oxide/config ▶  Step 2: Place the Bases From the extracted ZIP files, locate the copypaste folder and move it to the following directory: 📁/serverfiles/oxide/data ▶  Step 3: Place the Base_Loot Tables From the extracted ZIP files, locate the Base_Loot folder and move it to the following directory: 📁/serverfiles/oxide/data/RaidableBases Important: If there are any existing JSON files inside this folder that are not part of our loot tables, delete them to ensure proper functionality. Choose between Vanilla or Enhanced loot tables based on your preference. If the folder is named "Base_Loot (Enhanced loot)", remove the text in parentheses so that the correct folder name is simply: "Base_Loot"   (Otherwise, the loot tables will not work properly.) ▶  Step 4: Place the Profiles Folder From the extracted ZIP files, locate the profiles folder and move it to the following directory: 📁/serverfiles/oxide/data/RaidableBases Why Are Profiles Important? The profiles folder contains crucial settings that allow you to: ✔️ Enable/disable the dome ✔️ Enable/disable NPCs ✔️ Adjust the number of lootable items These are just a few examples—there are dozens of important settings that directly affect how raid bases function. The config file alone is not enough—these files play a major role in customizing your raid bases. ⚡ I strongly recommend reviewing each difficulty setting (Easy to Nightmare) inside the profiles folder and adjusting them based on your needs. ▶  Step 5: Restart the plugin via RCON: o.reload RaidableBases ⚙️INSTALLATION GUIDE 2: (Use this installation method if you do not want to use our configurations and instead prefer to use your own config files and your own 📁/oxide/data/RaidableBases/Profiles configurations.) In this case, you only need to add the bases. To do this, use the following commands in RCON: ▶  Step 1:   You can add bases one by one or in bulk. After executing the commands in RCON, the bases will be registered inside the Profiles configuration. If you do not want to deal with these adjustments, it is recommended to use Installation Guide 1 instead. A- Example RCON commands:   rb.config add "Easy Bases" fullwipedeasy1 rb.config add "Hard Bases" fullwipedhard1 B- Commands to Integrate Raid Bases in Bulk via RCON: rb.config add "Easy Bases" fullwipedeasy1 fullwipedeasy2 fullwipedeasy3 fullwipedeasy4 fullwipedeasy5 fullwipedeasy6 fullwipedeasy7 fullwipedeasy8 fullwipedeasy9 fullwipedeasy10 fullwipedeasy11 fullwipedeasy12 fullwipedeasy13 fullwipedeasy14 fullwipedeasy15 fullwipedeasy16 fullwipedeasy17 fullwipedeasy18 fullwipedeasy19 fullwipedeasy20 fullwipedeasy21 fullwipedeasy22 fullwipedeasy23 fullwipedeasy24 fullwipedeasy25 fullwipedeasy26 fullwipedeasy27 fullwipedeasy28 fullwipedeasy29 fullwipedeasy30 fullwipedeasy31 fullwipedeasy32 fullwipedeasy33 fullwipedeasy34 fullwipedeasy35 fullwipedeasy36 fullwipedeasy37 fullwipedeasy38 fullwipedeasy39 fullwipedeasy40 fullwipedeasy41 fullwipedeasy42 fullwipedeasy43 fullwipedeasy44 fullwipedeasy45 fullwipedeasy46 fullwipedeasy47 fullwipedeasy48 fullwipedeasy49 fullwipedeasy50 fullwipedeasy51 fullwipedeasy52 fullwipedeasy53 fullwipedeasy54 fullwipedeasy55 fullwipedeasy56 fullwipedeasy57 fullwipedeasy58 fullwipedeasy59 fullwipedeasy60 fullwipedeasy61 fullwipedeasy62 fullwipedeasy63 fullwipedeasy64 fullwipedeasy65 fullwipedeasy66 fullwipedeasy67 fullwipedeasy68 fullwipedeasy69 fullwipedeasy70 rb.config add "Medium Bases" fullwipedmed1 fullwipedmed2 fullwipedmed3 fullwipedmed4 fullwipedmed5 fullwipedmed6 fullwipedmed7 fullwipedmed8 fullwipedmed9 fullwipedmed10 fullwipedmed11 fullwipedmed12 fullwipedmed13 fullwipedmed14 fullwipedmed15 fullwipedmed16 fullwipedmed17 fullwipedmed18 fullwipedmed19 fullwipedmed20 fullwipedmed21 fullwipedmed22 fullwipedmed23 fullwipedmed24 fullwipedmed25 fullwipedmed26 fullwipedmed27 fullwipedmed28 fullwipedmed29 fullwipedmed30 fullwipedmed31 fullwipedmed32 fullwipedmed33 fullwipedmed34 fullwipedmed35 fullwipedmed36 fullwipedmed37 fullwipedmed38 fullwipedmed39 fullwipedmed40 fullwipedmed41 fullwipedmed42 fullwipedmed43 fullwipedmed44 fullwipedmed45 fullwipedmed46 fullwipedmed47 fullwipedmed48 fullwipedmed49 fullwipedmed50 fullwipedmed51 fullwipedmed52 fullwipedmed53 fullwipedmed54 fullwipedmed55 fullwipedmed56 fullwipedmed57 fullwipedmed58 fullwipedmed59 fullwipedmed60 rb.config add "Hard Bases" fullwipedhard1 fullwipedhard2 fullwipedhard3 fullwipedhard4 fullwipedhard5 fullwipedhard6 fullwipedhard7 fullwipedhard8 fullwipedhard9 fullwipedhard10 fullwipedhard11 fullwipedhard12 fullwipedhard13 fullwipedhard14 fullwipedhard15 fullwipedhard16 fullwipedhard17 fullwipedhard18 fullwipedhard19 fullwipedhard20 fullwipedhard21 fullwipedhard22 fullwipedhard23 fullwipedhard24 fullwipedhard25 fullwipedhard26 fullwipedhard27 fullwipedhard28 fullwipedhard29 fullwipedhard30 fullwipedhard31 fullwipedhard32 fullwipedhard33 fullwipedhard34 fullwipedhard35 fullwipedhard36 fullwipedhard37 fullwipedhard38 fullwipedhard39 fullwipedhard40 fullwipedhard41 fullwipedhard42 fullwipedhard43 fullwipedhard44 fullwipedhard45 fullwipedhard46 fullwipedhard47 fullwipedhard48 fullwipedhard49 fullwipedhard50 fullwipedhard51 fullwipedhard52 fullwipedhard53 fullwipedhard54 fullwipedhard55 fullwipedhard56 fullwipedhard57 fullwipedhard58 fullwipedhard59 fullwipedhard60 rb.config add "Expert Bases" fullwipedexp1 fullwipedexp2 fullwipedexp3 fullwipedexp4 fullwipedexp5 fullwipedexp6 fullwipedexp7 fullwipedexp8 fullwipedexp9 fullwipedexp10 rb.config add "Nightmare Bases" fullwipednight1 fullwipednight2 fullwipednight3 fullwipednight4 fullwipednight5 fullwipednight6 fullwipednight7 fullwipednight8 fullwipednight9 fullwipednight10 ▶  Step 2: Place the Base_Loot Tables From the extracted ZIP files, locate the Base_Loot folder and move it to the following directory: 📁/serverfiles/oxide/data/RaidableBases Important: If there are any existing JSON files inside this folder that are not part of our loot tables, delete them to ensure proper functionality. Choose between Vanilla or Enhanced loot tables based on your preference. If the folder is named "Base_Loot (Enhanced loot)", remove the text in parentheses so that the correct folder name is simply: "Base_Loot"   (Otherwise, the loot tables will not work properly.) ▶  Step 3: Restart the plugin via RCON: o.reload RaidableBases EXTRA IMPORTANT INFORMATIONS: We do not use a dome, NPCs, or arena walls around raid bases on our servers, and in the ZIP file we provided, these features are also disabled by default. If you want to enable them, you will need to adjust the settings accordingly. For example, to enable the dome, follow the steps below: Navigate to: 📁/oxide/data/RaidableBases/Profiles Open the files inside the Profiles folder with a text editor. Locate the following settings: (This is already set to false because it is required for markers to appear on the map.) "Spawn Silently (No Notification, No Dome, No Map Marker)": false, "Create Dome Around Event Using Spheres (0 = disabled, recommended = 5)": 0, Change the value from 0 to 5 as shown below: "Create Dome Around Event Using Spheres (0 = disabled, recommended = 5)": 5, Additionally, the loot amount for bases varies depending on the difficulty level (easy, medium, hard, expert, and nightmare). You can adjust this setting in the same Profiles location according to your needs: "Amount Of Items To Spawn": 210, For example, in medium bases, this value is set to 210, which determines the total number of items that will appear in crates, furnaces, and the cupboard. Our current configuration is specifically adjusted to prevent players from feeling overwhelmed by massive buildings right after a wipe. We have configured Maintained Events accordingly to ensure a balanced experience. In our setup: - Timed events and purchasable events are disabled. - After a wipe, easy bases will start spawning 30 minutes later. - Nightmare bases will begin spawning 48 hours (2 days) later. Imagine starting the game with just a torch in hand and immediately encountering a nightmare base on the shore. You’d likely quit the game right away—this setting is crucial for us to avoid such scenarios. Configuration Example: 📁/serverfiles/oxide/config "Maintained Events": {   "Always Maintain Max Events": true,   "Max Maintained Events": 30,   "Enable X Hours After Wipe (0 = immediately)": {     "Easy": 0.5,     "Medium": 1.0,     "Hard": 3.0,     "Expert": 24.0,     "Nightmare": 48.0        All of our bases from Easy to Nightmare are equipped with turret protection. If you do not want turrets to spawn in your raidable bases on your server, you can use the following method. Go to the file path /data/RaidableBases/Profiles, open the JSON files inside with a text editor, and apply the following:   "Kill These Prefabs After Paste": [     "assets/prefabs/npc/autoturret/autoturret_deployed.prefab",     "autoturret_deployed" ], If you are satisfied with this package, you can support us by leaving a 5-star review on the site where you purchased it. Your feedback motivates us to continue improving and providing even better configurations for dedicated server owners like you. Thank you!  ❤️    
3.7
sale
🥇Ready to level up your server's raiding experience? 🏆This premium pack contains 300 unique, handcrafted raidable bases divided into 5 distinct difficulty tiers (Easy, Medium, Hard, Expert, and Nightmare). Every base was built manually in-game, saved with CopyPaste, and tested on a live server. Everything is 100% Plug & Play — no setup or editing required! 🏆What Makes This Pack Unique: 300 Custom Bases: Includes 100 Easy, 100 Medium, 40 Hard, 30 Expert, and 30 Nightmare bases. 2 Complete Loot Table Sets: Choose between Difficulty_Loot (higher amounts for modded/high-rate servers) or Difficulty_Loot2 (lower amounts for vanilla-style servers). Fully Defended & Clever Layouts: Built with auto turrets, shotgun traps, flame turrets, SAM sites, land mines, and tesla coils. Some bases feature hidden traps crafted with EditTool so raiders can't easily spot every defense. Visual Variety & Heavy Challenge: Higher tiers utilize mostly Metal and HQM building grades along with custom skinned blocks and deployables. Plug & Play Setup: Pre-configured profiles and main plugin settings included. Just copy, paste, and reload! Important! - In case that you are buying this pack to update your server, contact me, and after buying the pack I can rename the bases special for you, and will send the updated profiles so you won't lose any time. 🎈How to Install (Step-by-Step):   Setting this up on your server takes less than 2 minutes: Base Files: Extract all .json files from all subfolders (copypaste/Easy/, Medium/, etc.) and place them directly into oxide/data/copypaste/. (Do not copy subfolders, only the files inside them!) Loot Tables: Pick ONE of the loot folders (Difficulty_Loot/ for higher rewards or Difficulty_Loot2/ for lower rewards). Copy all 5 .json files into oxide/data/RaidableBases/Loot/. (Do not copy both!) Profiles: Copy all files from Profiles/ into oxide/data/RaidableBases/Profiles/. Plugin Config (Optional): If you want to use the included custom config, copy config/RaidableBases.json into oxide/config/. (Note: This will overwrite your existing config!) Reload: Run o.reload RaidableBases in your server console. Requirements: This pack requires an Oxide/uMod Rust server with the paid RaidableBases plugin (by nivex) and the CopyPaste plugin installed. IMPORTANT: Remove Stone Walls (Enclosures): By default, the plugin spawns a giant stone wall around bases. To remove it: Open oxide/config/RaidableBases/Profiles/Easy.json Find "Spawns Enclosure": true and change it to false. Run command: rb.reload in console. In Case that you feel that it's too much loot: Open oxide/config/RaidableBases/Profiles/Easy.json or any tother Difficulty "Amount Of Items To Spawn": 45, A tip from me, I would rather put a little bit more loot in the profiles, so the players wil have a better gameplay. Change the  Amount Of Items to a lower number. Modifying Base Despawn Timers: If you want to change how long a base stays on the map before disappearing, find these lines under "Raid Management" in config:  "Minutes Until Despawn After Looting (min: 1)": 15, "Minutes Until Despawn After Inactive (0 = disabled)": 45 Controlling Automatically Maintained Events: It's spawning 6 bases at every 30 mins - 1h 30 mins, randomly. Easy & Medium got higher chances to spawn. Takes 30 seconds per base to spawn so it's not going to make the server to lag. "Always Maintain Max Events": true, "Max Maintained Events": 6 Auto-Cooking & Sorting (Furnace & Base Sorting): If you want to know how the pack automatically moves resources or food into the right containers when a base spawns, look for these options under "Raid Management" in config: "Move Cookables Into Ovens": true, "Move Food Into BBQ Or Fridge": true, "Move Resources Into Tool Cupboard": true, "Move Items Into Lockers": true Turning Lights and Furnaces On Automatically: "Turn Lights On At Night": true, "Turn Lights On Indefinitely": true, "Furnace Starting Fuel": 1000 Automatic Chat Announcements: If you want the entire server to know when a new raid has appeared on the map, look for "Event Messages" in config: "Announce Buy Base Messages": false, "Show Opened Message For PVE Bases": true, "Show Opened Message For PVP Bases": true Manual Base Registration (Console Commands) If you already have existing bases and do not want to overwrite your profiles, run these commands in your server console (F1 or RCON) to add all 300 bases manually, then run o.reload RaidableBases:  (Important! - In case that you are buying this pack to update your server, contact me, and after buying the pack I can rename the bases special for you, and will send the updated profiles so you won't lose any time.) rb.config add "Easy Bases" easy1 easy2 easy3 easy4 easy5 easy6 easy7 easy8 easy9 easy10 rb.config add "Easy Bases" easy11 easy12 easy13 easy14 easy15 easy16 easy17 easy18 easy19 easy20 rb.config add "Easy Bases" easy21 easy22 easy23 easy24 easy25 easy26 easy27 easy28 easy29 easy30 rb.config add "Easy Bases" easy31 easy32 easy33 easy34 easy35 easy36 easy37 easy38 easy39 easy40 rb.config add "Easy Bases" easy41 easy42 easy43 easy44 easy45 easy46 easy47 easy48 easy49 easy50 rb.config add "Easy Bases" easy51 easy52 easy53 easy54 easy55 easy56 easy57 easy58 easy59 easy60 rb.config add "Easy Bases" easy61 easy62 easy63 easy64 easy65 easy66 easy67 easy68 easy69 easy70 rb.config add "Easy Bases" easy71 easy72 easy73 easy74 easy75 easy76 easy77 easy78 easy79 easy80 rb.config add "Easy Bases" easy81 easy82 easy83 easy84 easy85 easy86 easy87 easy88 easy89 easy90 rb.config add "Easy Bases" easy91 easy92 easy93 easy94 easy95 easy96 easy97 easy98 easy99 easy100 rb.config add "Medium Bases" medium1 medium2 medium3 medium4 medium5 medium6 medium7 medium8 medium9 medium10 rb.config add "Medium Bases" medium11 medium12 medium13 medium14 medium15 medium16 medium17 medium18 medium19 medium20 rb.config add "Medium Bases" medium21 medium22 medium23 medium24 medium25 medium26 medium27 medium28 medium29 medium30 rb.config add "Medium Bases" medium31 medium32 medium33 medium34 medium35 medium36 medium37 medium38 medium39 medium40 rb.config add "Medium Bases" medium41 medium42 medium43 medium44 medium45 medium46 medium47 medium48 medium49 medium50 rb.config add "Medium Bases" medium51 medium52 medium53 medium54 medium55 medium56 medium57 medium58 medium59 medium60 rb.config add "Medium Bases" medium61 medium62 medium63 medium64 medium65 medium66 medium67 medium68 medium69 medium70 rb.config add "Medium Bases" medium71 medium72 medium73 medium74 medium75 medium76 medium77 medium78 medium79 medium80 rb.config add "Medium Bases" medium81 medium82 medium83 medium84 medium85 medium86 medium87 medium88 medium89 medium90 rb.config add "Medium Bases" medium91 medium92 medium93 medium94 medium95 medium96 medium97 medium98 medium99 medium100 rb.config add "Hard Bases" hard1 hard2 hard3 hard4 hard5 hard6 hard7 hard8 hard9 hard10 rb.config add "Hard Bases" hard11 hard12 hard13 hard14 hard15 hard16 hard17 hard18 hard19 hard20 rb.config add "Hard Bases" hard21 hard22 hard23 hard24 hard25 hard26 hard27 hard28 hard29 hard30 rb.config add "Hard Bases" hard31 hard32 hard33 hard34 hard35 hard36 hard37 hard38 hard39 hard40 rb.config add "Expert Bases" expert1 expert2 expert3 expert4 expert5 expert6 expert7 expert8 expert9 expert10 rb.config add "Expert Bases" expert11 expert12 expert13 expert14 expert15 expert16 expert17 expert18 expert19 expert20 rb.config add "Expert Bases" expert21 expert22 expert23 expert24 expert25 expert26 expert27 expert28 expert29 expert30 rb.config add "Nightmare Bases" nightmare1 nightmare2 nightmare3 nightmare4 nightmare5 nightmare6 nightmare7 nightmare8 nightmare9 nightmare10 rb.config add "Nightmare Bases" nightmare11 nightmare12 nightmare13 nightmare14 nightmare15 nightmare16 nightmare17 nightmare18 nightmare19 nightmare20 rb.config add "Nightmare Bases" nightmare21 nightmare22 nightmare23 nightmare24 nightmare25 nightmare26 nightmare27 nightmare28 nightmare29 nightmare30 You will see photos only with 10 bases per Difficulty, beacause I am aware of people stealing my designs. In the pack you will se a file named: RaidableBases_Testing_cfg (this is another config for the pack, that makes the bases to spawn without any cooldown, while the main configuration in  the pack makes the bases to spawn between 30 min up to 1h 30 mins)    🛡️Optimized NPCs The number of NPCs is fully optimized for each difficulty tier. You can find and tweak these balanced guard configurations inside the Profiles/ folder A Note From Me 👋🏻 Hello and welcome! I’ve put my heart and countless hours into creating Raidable Bases Pack 2. Everything was built by me from scratch on my online server. I am incredibly proud of this project, especially the dual-loot table options designed to fit any server economy seamlessly. In case that you want to see few of my bases by urself, contact me and I will join on my public server and will spawn some of them, the ip: 148.251.177.248:28020     .    Why only $60? A massive pack with 300 custom bases and dual loot tables easily goes for $100+ on the market. But as a former server owner myself, I know how hard and expensive it is to find high-quality setups that don't break the bank. I wanted to keep it at a fair, accessible price while giving you top-tier quality for your server! 🌟Support the Work    If you love this pack, please consider leaving a 5-star review! Your feedback means the world to me and motivates me to keep building and improving future packs. Thank you for your support, and happy raiding!🚀
0.0
$19.99
SimplePVE is exactly what the name suggests: a simple and easy-to-use PVE plugin for Rust servers. It allows server owners to control and customize PVE rules individually, either through the config or with a clean in-game CUI. You can also create, edit, and manage PVE/PVP schedules directly, making it easy to run full PVE servers, purge events, or hybrid PVE/PVP setups. ⭐ Key Features Control PVE rules directly from in-game CUI or through the config Easy-to-understand rule system for managing damage, raiding, looting, and protection Enable or disable PVE/PVP manually with commands Create automatic PVP schedules for purge times Supports weekly schedules, such as Sunday to Friday or weekend-only PVP Supports date-specific schedules, such as January 1 to January 7, holiday events, wipe-weekend events, and custom purge periods Automatic PVE/PVP purge events based on your configured schedule Loot protection system to prevent unauthorized looting Zone Manager support for custom PVE/PVP zones Exclude specific zones from global PVE rules Supports many popular event plugins Works without using `server.pve true` In-game rule manager using `/sprules` Debug command to help check why damage is blocked or allowed Optional PVE/PVP status UI for players Customizable UI position, status text, icons, and colors Discord embed messages when PVP purge starts or ends Optional Discord warning messages before PVE/PVP schedule changes Run custom server commands when PVP purge starts or ends Admin bypass permissions for loot and damage control Supports PVP delay when leaving PVP zones Flexible config for server owners who want full control Designed for simple PVE servers, purge servers, hybrid PVE/PVP servers, and event-based servers NEW • CUSTOM STATUS  NEW • PVE/PVP HUD FOR DISPLAYING PURGE EVENTS 📌 Commands /simplepve - Use to enable or disable pve toggle (Chat & Console command) /simplepve on or off - Use to enable disable pve (Chat & Console command) /sprules - Use to Open a Cui to control PVE Rules & Creating Schedules   (Chat command) /spdebug - Use this for debuging rules /sp_change - Use this to change the SimplePVE hud from ingame (Chat command) 📜 Permissions simplepve.admin - Required to enable or disable SimplePVE simplepve.adminloot - Required to view Loots of other players simplepve.admindamage - Required for Admin damages to any entity                                                                                                                                                                                                     🎉 Game hosting perfected, that's Physgun Join the thousands of server owners using Physgun to take their game server communities to the top.   🎬 Video Showcase 🚀 API & Hooks void  OnSPVEPurgeStarted() void  OnSPVEPurgeEnded() TimeSpan  GetPVPStartTimeRemaining() TimeSpan  GetPVPEndTimeRemaining() ⚙️ Configurations 🗃️ Rules Data file in Oxide/data/SimplePVE 📜 FAQ Question: Does SimplePVE require server.pve to be set to false? Yes, it requires server.pve set to false. Question: Where can I change the rules for my PVE server? You can use the `/sprules` command to open the in-game CUI rule manager. You must have the `simplepve.admin` permission assigned to use this command. Question: PVE/PVP schedules times are not working properly, why is that happening? You may need to adjust the `UTC Time Difference` value in the config. Make sure the UTC offset matches your server’s intended timezone. For more details, please check the Info tab below. Question: How do I enable or disable PVE manually? You can use `/simplepve on` to enable PVE and `/simplepve off` to disable it. You need the `simplepve.admin` permission to use these commands. Question: Can I create automatic PVP purge schedules? Yes. SimplePVE supports scheduled PVP/PVE times, allowing you to automatically enable PVP during purge events and return to PVE when the schedule ends. Question: Can I do Weekly schedules like Sunday To Friday or specific date to another date? Yes. SimplePVE supports both option and you can only use one of them at once. Question: Can admins damage players or entities while PVE is enabled? Yes, but only if the admin damage settings and permissions allow it. The permission `simplepve.admindamage` is used for admin damage access. Question: Why is damage still happening during PVE mode? This usually means one of your rules allows that damage type, or another plugin is modifying damage before or after SimplePVE. Use `/spdebug` to help debug which rule is being applied. Question: What does `/spdebug` do? The `/spdebug` command helps you debug damage rules. It can be useful when you are trying to understand why damage is blocked or allowed. Question: How does loot protection work? Loot protection prevents players from looting protected entities or containers, depending on your config settings. Admins can be allowed to bypass this using the `simplepve.adminloot` permission. Question: Can I exclude specific entities from loot protection? Yes. You can add entity shortnames to the `Loot Protection Excluded Entitys` list in the config. Question: Does SimplePVE support zones? Yes. SimplePVE supports Zone Manager, allowing you to create different PVE/PVP behavior inside specific zones. Question: Can I exclude specific zones from SimplePVE rules? Yes. You can add zone IDs to the `Exclude Zone IDs From Rules` config option. Question: Can SimplePVE send Discord notifications? Yes. SimplePVE can send Discord embed messages when PVP purge starts, ends, or when a scheduled event is approaching, depending on your Discord config settings. Question: Can I run server commands when PVP purge starts or ends? Yes. You can add commands to the config options for commands that run when PVP purge starts or ends. ⚙️ Schedules Settings for your own timezone 🛠️ For Developers           💬 Support   Check Out My Other plugins as Well
5.0
Raid Time Manager  ·  Rust  ·  Oxide  ·  Carbon Your best players get raided at 4am and never log in again You set the hours raiding is open. Outside them the damage, the ladder stacks, the ceiling drops and the turret placements all stop — and everyone can see the schedule on screen. A full week is configured out of the box, and every hour of it is editable from a calendar in game. The HUD Six layouts, one of them fits your screen Switched live from the settings screen — every player's HUD is redrawn on the spot.         How it goes From install to the night before wipe MINUTE ONE It works before you open the config Raid time is set to 18:00–22:00 Monday to Friday, 10:00–22:00 Saturday, 08:00–22:00 Sunday. Every hour outside that is safe time, and the restrictions are already on. Your timezone, by offset or by name, daylight saving included Several raid windows in one day, or none at all for a full safe day Nothing to fill in first — edit the week later, or never EVERY DAY Nobody has to ask when raid time is A HUD shows today's windows as a bar, a marker for where the clock sits inside them, and a green or red dot for whether raiding is open right now. Six positions, switched live. Players can hide it, and it hides itself on cameras and drones Every player reads it in their own language, on a 12- or 24-hour clock An alert on screen the moment raid time opens, and again when it closes An optional Discord webhook warns your players a set time before it opens WHEN THEY TRY Blocking damage alone does not stop a raid Someone who cannot blow a wall will stack ladders, drop a ceiling inside your compound, or park a turret on your door instead. Thirteen switches, so you block what matters on your server and leave the rest alone. Damage. Other people's buildings, your own, twig, boats, tugboats, fire Raids with no player behind them. Patrol helicopter, MLRS, SAM sites and auto turrets, each its own toggle Building tricks. Ladders and ceilings inside someone else's privilege, cupboards and turrets placed next to one They are told why. A blocked shot or placement puts the reason on the player's screen Your own exceptions. A prefab list that stays damageable whatever the clock says, and a separate switch for other people's sleeping bags WIPE DAY The exceptions are where a schedule earns its keep A fixed week is fine until wipe day, a holiday, or the first complaint about being raided ten minutes after joining. All four of those are settings. Set hours for one specific date from the calendar — it beats the weekly rule Safe days after a wipe, written into the schedule for you New players protected for a few hours, if you want them to be Or block offline raids only, with a shorter grace period for your donators   Alongside the rest It fits what you already run All optional, all off until you point at them. ✓  TruePVE — its ruleset is switched with the schedule, so the two never disagree   ✓  ZoneManager — confine the whole thing to listed zones, or apply it everywhere except them ✓  Raidable Bases — event bases stay raidable around the clock, safe time never locks players out   ✓  Your own commands — run any server command the moment raid time opens, and again when it closes   Reference One command, and it is yours to rename Everything else is a screen you click through in game. Chat /rtm Open the raid calendar. Admins also get a settings button on it. Chat /rtm hud Hide the HUD, or bring it back Perm rtm.vip Shorter offline grace period. Rename it or add more groups.     Straight answers Asked before every purchase Do I need TruePVE? No, it blocks the damage itself. TruePVE is optional and only makes the two systems agree if you already run it.   Can I still raid people who are online? Turn on offline-only mode and safe time protects a base only while the owner and their whole team are away. Do I have to edit config files? Not for the schedule. The calendar and settings screens change the hours, the toggles and the HUD position from in game.   Is it English only? No. Days, months, AM/PM and every message are language file entries, so you translate once and each player sees their own. What about NPCs and scripted raids? One switch lets non-player raiders through at any hour, and the prefab list covers anything that must always stay damageable.   Will the HUD annoy my players? Six positions including a compact one, they can dismiss it themselves, and you can switch it off server-wide.   13 actions you can block 6 HUD layouts 3 integrations — TruePVE, ZoneManager, Raidable Bases 1 dependency — ImageLibrary
5.0
The Offline Raid Protection plugin is a comprehensive solution that reduces or completely prevents damage to player-owned bases, vehicles, and boats when their owners are offline. Offering unparalleled control, server owners can adjust the level of damage based on real-world hours or the amount of time a player has been offline. New in version 1.6.0, you can also set customized schedules and automated wipe phases. Designed for servers seeking meaningful offline or online protection, without sacrificing server performance, this plugin provides total control over damage scales, cooldowns, team behaviour, decaying bases, rentable shops, apartments and more. ✨Highlights Flexible Damage Scaling: Set damage scales based on real-world hours and/or offline time. A scale of 0.0 blocks all damage; a scale of 1.0 allows normal, vanilla-level damage; and values above 1.0 actively increase incoming damage. Scheduled Timescales: Temporarily override standard damage scales for specific date ranges. Perfect for custom weekend rates, holiday events, wipe-day protection, or planned balance changes. Wipe Templates: Automate your wipe cycle with reusable phases (e.g., more protection immediately post-wipe, scaling down over subsequent days). Assign a default template for every wipe, or queue a specific template for the next wipe only. Status HUD: An optional, configurable on-screen HUD that displays a building's or boat's current protection status, protection percentage, remaining time, and penalty timers. Position and visibility rules are customizable. Game Tip Messages: Displays color-coded game-tip messages to attackers, optionally restricted to specific damage types (Melee, Ranged, Explosive, and None for everything else). Admin-Only Map Markers: Equip your admins with color-coded map markers for protected Tool Cupboards and boats. Markers feature dynamic protection-state circles, live boat tracking, and detailed hover tooltips showing authorized players. Marker colors, radius, transparency, and refresh rates are configurable. Team, Clan & Code Lock Integration: Protection intelligently accounts for teams or clans, and optionally Code Lock whitelists. Boat & Vehicle Protection: Optionally extend protection to modular boats, tugboats, and vehicles, including their relevant authorization paths. Apartment & Rentable Shop Support: Protects against master-key break-ins based on the actual rental owner, ignoring team or clan status for these specific entities. Anti-Abuse Penalties: Discourage players from exploiting protection by applying configurable penalties when they leave or disband teams. Grief TC Detection: Automatically identifies and excludes later-placed, overlapping Tool Cupboards from receiving protection. Admins can manually inspect and override these classifications. Cache System: The plugin uses a caching system to optimize performance and keep the impact on the server to a bare minimum. Developer API: Exposes endpoints for other plugins to query protection scales, owner IDs, remaining time, and penalty states via Plugin.Call.   📅 Scheduled Timescales & Wipe Templates Your standard configuration acts as the baseline fallback when "Enable scheduled timescales" is true and a valid scheduled profile is active, its specific damage-scale tables take absolute precedence for that date range. Once the schedule expires (or if no profile is active), the plugin seamlessly reverts to your standard configuration. Wipe Templates are reusable blueprints, not live schedules. When the server detects a new save, the plugin checks for a queued template. If there is none, it uses your designated default template to automatically generate concrete, dated schedule profiles based on the template's phases. Then, the queued selection is cleared while the default template remains ready for future wipes. Configuration & Editing Carbon Users:  Type /orp.schedule to open a powerful in-game Schedule and Wipe Template editor. Oxide Users (or Carbon without Admin UI modules): Schedules and templates can be easily edited manually within their dedicated .json data files. The Documentation section describes how to edit the JSON files in detail. Using /orp.schedule will instead report the current schedule state in the chat.   ⚡ Built with performance in mind Offline Raid Protection is designed to minimize its impact on server performance, even on busy servers. Protection data is cached and recurring updates, such as status HUD and map marker refreshes, are processed in controlled batches. Temporary data is reused where appropriate to reduce unnecessary allocations. No other raid protection plugin is built with such a focus on efficient protection checks, caching, and controlled background work. This plugin is engineered to minimize server overhead and avoid unnecessary lag or FPS drops, even on large, active servers. Development is focused on Carbon, taking advantage of its modern runtime, optimized systems, and native modules to deliver the best possible performance. Carbon generally outperforms Oxide, ensuring that Offline Raid Protection maintains efficiency and responsiveness on demanding servers.   ✨ Flexible Protection for Every Server Offline Raid Protection supports a variety of server types, including full PvP, hybrid, and PvE. You can configure protection for bases, boats, vehicles, shops, apartments, teams, clans, and more. It also works with other plugins, such as "Raidable Bases", allowing you to customize raid protection for your server without altering the rest of your gameplay.   Commands All command names can be changed in the configuration. /orp  or /ao <Steam ID or full name>  —  Check a player's offline protection status.  You can type the command without a name when looking at a player's structure /raidprot  — Show Offline Raid Protection information /orp.fill.onlinetimes  — Fill all players offline times (Chat & Console command) /orp.test.offline <Steam ID or full name> <hours> — Change a player's offline time /orp.test.online  <Steam ID or full name>  — Change a player's offline time to the current time /orp.test.penalty  <Steam ID or full name> <hours>  — Change the duration of a player's penalty. A negative value or zero would disable the penalty /orp.test.grief — Display the detected Grief-TC status of the building you are looking at /orp.test.grief <true|false|none> — Force the Grief-TC status of the looked-at building /orp.test.grief <true|false|none> <TC network ID> [...] — Set the status for one or more Tool Cupboards by network ID /orp.schedule — Open the Carbon schedule/template editor when available; otherwise show scheduling information. /orp.schedule <true|false> — Enable or disable Scheduled Timescales (admin only). orp.update.permissions — Refresh the protection-permission status (`offlineraidprotection.protect`) for all players (Console command) orp.update.prefabs <true> — Updates the 'Prefabs to protect' list in the configuration. Overwrites the list with the 'true' argument  (Console command) orp.dump.prefabs — Clears the 'Prefabs to protect' list in the configuration  (Console command)   Permissions All permissions can be configured. offlineraidprotection.protect  — Allows a player to be protected from raids offlineraidprotection.check  — Allows a player to check the offline protection status of other players offlineraidprotection.admin  —  Allows use of administrative commands, including schedule controls Use oxide.grant / oxide.revoke or carbon.grant / carbon.revoke to manage permissions, depending on the framework in use.   Configuration The configuration is to a large extent self-explanatory. Raid Protection Options ⚙️  Only mitigate damage caused by players: Choose whether or not to only mitigate damage caused directly by players. Enable this to prevent players from causing base damage by baiting patrol helicopters, etc. ⚙️  Protect players that are online: Choose whether or not to protect the bases of the players who are online. Works when "Scale of damage depending on the current hour of the real day" is configured. ⚙️  Enable scheduled timescales: Enable this option to allow valid profiles in `ScheduledTimescale.json` to override the normal real-time and offline-time damage-scale tables during their configured date range. When disabled, the plugin always uses the normal configuration tables. This option also enables Wipe Template materialization on a new save. As an admin, use the command /orp.schedule true or /orp.schedule false to change it in-game. On Carbon with the required UI modules, `/orp.schedule` opens the editor; on Oxide or without those modules, edit the dedicated JSON files manually. ⚙️  Scale of damage depending on the current hour of the real day: Defines the protection levels based on the current hour of the real day. The key is the hour of the day (0-23), and the value is the protection scale (0  —  340282300000000000000000000000000000000). Example: "0": 0.0, "1": 0.0, "2": 0.0, "3": 0.0 This means that the protection level is 100% from midnight to 3am. ⚙️  Scale of damage depending on the offline time in hours: Defines the protection levels based on the time since the player went offline. The key is the number of hours since the player went offline, and the value is the protection scale (0  —  340282300000000000000000000000000000000). The value of the hours can also be a decimal number. Example: "12": 0.25, "24": 0.5, "48": 1.0, "96": 2.0 This means that 12 hours after the player goes offline, the protection level will be 75%. After 24 hours it will be 50% and after 48 hours it will be 0%. After 96 hours, the damage is increased by 100%. ⚙️  Cooldown in minutes: During this time, damage levels will remain vanilla. Raids are possible. Set this to a positive value to discourage defenders from interrupting raids by logging off. ⚙️  Scale of damage between the cooldown and the first configured time: During this time, the level of damage between the cooldown and the first configured time can be set to a specific value, such as 0.0 ⚙️  Online time to qualify for offline raid protection in minutes: Time to qualify for offline raid protection after a player connects Set this to a positive value to discourage players from quickly logging on and back off solely to reset protection. ⚙️  Protect all prefabs: Choose whether to protect all prefabs or only specific ones.   This will protect anything in the TC range. ⚙️  Protect AI (animals, NPCs, Bradley and attack helicopters etc.) if 'Protect all Prefabs' is enabled: Choose whether or not to protect AI entities if  "Protect all Prefabs" is enabled. Set to false to reduce hook times, and to avoid protecting wild animals that wander by offline bases. ⚙️  Protect modular and tug boats: Choose whether to protect modular boats and tugboats and their deployables. Checks wheel authorisation list, plus optionally lock authorisation lists. ⚙️  Protect vehicles: Choose whether to protect vehicles or not. Vehicle lock authorisation always has priority. If you want to exclude certain vehicles from protection, add them to the blacklist. Tugboats and modular boats are separate from this. ⚙️  Protect twigs: Choose whether to protect twigs or not. ⚙️  Protect decaying buildings: Choose whether to protect buildings that are either decaying, or have at least 50% of building blocks below 50% health. ⚙️  Ignore decay if due solely to twig: Choose whether to ignore decay state caused solely due to the presence of twig building blocks combined with a lack of wood in the TC. Set to true to ensure raiders cannot disable protection by building twig onto an offline base. ⚙️  Protect grief TCs: Choose whether detected grief Tool Cupboards should retain Offline Raid Protection. True: Detected grief TCs remain protected normally. False: A separately placed, later-created Tool Cupboard overlapping another building’s privilege area can be classified as a grief TC and will not receive Offline Raid Protection. The default is true. Set this to false only if you want ORP to exclude detected grief TCs. Admins can use `/orp.test.grief` to inspect or override individual classifications. ⚙️  Prefabs to protect: List of prefabs that will be protected. Make sure you remove the prefabs you don't want to protect, some of them are pointless. ⚙️  Prefabs blacklist: List of prefabs that will not be protected. Prefabs in the blacklist will always have priority to be unprotected.   Apartment Complex Protection Options ⚙️  Protect apartments from break-ins: Whether to protect apartments from master key break-ins when Raid Protection is active. ⚙️  Protect apartment even when owner absent: Whether apartments with no owner inside should remain protected. True: Apartment protection applies regardless of owner's offline location. False: Apartment protection applies only when owner is offline inside of the apartment. ⚙️  Protect apartment even when rent due: Whether apartments with no upkeep remaining should remain protected. True: Apartment protection applies even in Rent Due state. False: Apartment protection does not apply in Rent Due state. ⚙️  Protect shops from break-ins: Whether to protect rentable shops from master key break-ins when Raid Protection is active. ⚙️  Protect only when damage scale below: Whether to limit apartment and/or shop break-in protection based on damage scale. Example: Set to 0.2 to protect only when damage scale is between 0 and 0.2 (i.e. when protection level is between 80% and 100%). Set to 1.0 or higher to apply break-in protection regardless of damage scale. ⚙️  Use damage scale as break-in success chance: Whether to make a random roll on each break-in attempt, with chance of success equal to damage scale (e.g. 25% chance of success at 75% protection level, 80% chance at 20% protection level, etc.). Only applies when apartment or shop is otherwise protected.   Status HUD Options The Status HUD is optional and disabled by default. It provides players with a compact, configurable view of the protection state for the privilege area they are in. ⚙️ Enabled — Turns the Status HUD on or off. ⚙️ Anchor minimum / Anchor maximum — Sets the HUD anchor position using Unity screen coordinates. The default anchors place it at the top-right of the screen. ⚙️ Offset minimum / Offset maximum — Sets the HUD bounds in pixels relative to its anchors. Adjust these values to move or resize the panel without changing its anchor position. ⚙️ Refresh interval in seconds — Controls how often the HUD refreshes. A lower value updates it more frequently. ⚙️ Display inside trusted privilege — Choose whether the normal HUD is shown while the player is authorized on the relevant building or boat. ⚙️ Display only when protection is active — Hides the normal HUD whenever no active protection is being applied. ⚙️ Display after status command — Shows the HUD temporarily when a player uses the check status command. ⚙️ Status command display duration in seconds — Sets how long the command-triggered HUD remains visible. ⚙️ Show protection percentage — Displays the current protection percentage. ⚙️ Show remaining protection time — Displays the remaining time for the current protection scale when applicable. ⚙️ Show penalty timer — Displays a player’s active penalty timer when applicable. Map Marker Options Map markers are optional and disabled by default. Only players with the plugin’s admin permission can use them; regular players cannot. ⚙️ Enabled — Turns Tool Cupboard and boat markers on or off. ⚙️ Refresh interval in seconds — Controls how often marker state and labels are refreshed. Use a longer interval if immediate visual updates are not required. ⚙️ Enable boat live circle — Updates the map-radius circle for tugboats and modular boats as they move. ⚙️ Visual radius in metres — Sets the radius of each marker circle. ⚙️ Alpha — Sets circle transparency. "0" is fully transparent, and "1" is fully opaque. ⚙️ Protected color —  The color used for 100% protected status. ⚙️ Partial protection color — Color used when only partial protection applies. ⚙️ Vulnerable color — Color used when normal or vulnerable status applies. ⚙️ Decaying color — Color used for decaying building status. ⚙️ Grief color — Color used for a detected or forced grief tool cupboard status. ⚙️ Outline color — Color used for the marker circle outline. ⚙️ Tooltip marker text max. players — Limits how many authorized player names are shown in a marker tooltip.   Timezone Options The fallback timezone is UTC if you leave it blank in the configuration, or if your configured timezone doesn't exist. The timezone identifiers are different for Windows and Linux. You can check the appendices to find your preferred timezone.   Developer API Other Carbon/Oxide plugins can access ORP data through `Plugin.Call`. Available API methods: float API_GetEntityDamageScale(BaseCombatEntity entity, BasePlayer attacker) ulong API_GetEntityProtectionTargetID(BaseCombatEntity entity, BasePlayer attacker) float API_GetPlayerDamageScale(ulong playerID) long API_GetRemainingTimeTicks(ulong playerID) long API_GetPenaltyEndUtcTicks(ulong playerID) bool API_EnablePenalty(ulong playerID, float durationHours) bool API_DisablePenalty(ulong playerID) int API_EnablePenalties(ICollection<ulong> playerIDs, float durationHours) int API_DisablePenalties(ICollection<ulong> playerIDs) Return conventions: Damage-scale methods return -1f when no applicable ORP scale exists API_GetEntityProtectionTargetID returns 0UL when no target is available Time methods return 0L when no active value exists Bulk methods return the number of successfully processed known players   Conclusion The Offline Raid Protection plugin provides a comprehensive solution for protecting players' structures and vehicles. This plugin is essential for any Rust server owner who wants to provide a fair and enjoyable gaming experience for their players. Windows_Timezones.txt Linux_Timezones.txt   Prefabs.txt
4.4
In-game admin panel   Join our Discord Stop alt-tabbing to RCON. Run the whole server from inside the game. Seventeen sections behind one command. Players, permissions, plugins, console, ConVars, a live server map, ESP, Vanish, an entity hammer and your own custom buttons - all in a single panel that opens in half a second and never asks you to remember a console command. Every page and every action sits behind its own permission, so a junior moderator gets exactly what you hand them. /padmin   - that is the whole interface. Everything else is point and click, or a key you bound yourself.   17  ·  sections in the sidebar Dashboard Live console Players Vanish ESP Server map Binds Admin hammer Inspect tool Permissions & groups Logs Plugins ConVars Quick buttons Appearance Settings Bans DLC Freeze DLC Whitelist DLC Add-ons appear here once installed   01  ·  Out in the world Walk up to it and deal with it Most moderation does not start in a menu. It starts with you standing in front of a base, a player or a locked crate. Four tools cover that, none of them needing a client mod. Vanish that actually removes you Out of networking, out of colliders, out of entity queries and off the AI's list, so NPCs stop shooting and forget you were there. Radiation, cold, wetness, hunger, thirst and drowning stop touching you, and everything is restored exactly as it was when you switch it off. Optional silhouette so other admins can still see you, optional auto-vanish on connect, optional lock opening and noclip riding along. Admin hammer Hold a hammer, look at anything, and the HUD reads out owner, position, health, upkeep, power, who is authorized, the code lock codes and the full contents of the container. Shift+R arms a mode, Shift+LMB runs it: delete, delete with gibs, delete the whole linked structure, or on a hackable crate unlock it now and set its timer to any value. Inspect Look at a player and act without typing their name. E opens their inventory, RMB opens their full management card. An on-screen hint always says which key does what. Server-side ESP Drawn through the engine's own debug draw, visible only to admins holding the permission. Players and sleepers with name, HP and held item; loot, boxes, cupboards, bags, traps, stashes, NPCs, turrets and vehicles. Adjustable radius, opacity and text size, colour-coded enemy, team and admin.   02  ·  The player card One card per player, online or asleep A searchable, paginated roster of everyone the server has ever seen. Open a card and you get their SteamID, live status, session and total playtime, total Rust hours from the Steam API, groups, first and last seen, and their IP behind a separate permission. Underneath sit the actions, and each one has its own permission of its own. Heal Set, max, add or subtract HP Give Full item picker with categories, search, favourites, skins, custom items and a cart Kill / Strip Kill the target or clear the inventory Blueprints Unlock or reset any blueprint on a visual board Teleport To me, to player, to coordinates or to where you are looking Vitals HP and metabolism editor that respects each stat's real limits Mute / Kick Timed or permanent, with reason templates and notify routing Modifiers Metabolism modifiers with your own duration and value Inventory View and edit main, wear and belt Permissions Grant per-user permissions and manage their groups Spectate Jump into a live camera, press R to leave Markers Drop a note on the map against that player Offline players are not second-class Teleport to a sleeper, heal it, strip it, edit its inventory, mute the account, change its permissions. Only the actions that genuinely need a live connection - kick, spectate - grey out while the player is away.   03  ·  Server map The whole island inside the panel The real map with real positions, the Deep Sea zone included, zoomable to x4. The Deep Sea zone now follows its real open state and shows the time remaining before it closes. Layers switch on one at a time so you only look at what you came for, and every marker is clickable. Layers you switch on one by one Players, sleepers, cupboards, bags, stashes, shops, events, map notes, and vehicles split into cars, horses and air. Boats, submarines, trains, helicopters, the cargo ship and the cargo plane each get their own icon with a heading arrow showing where they are going. PVP and raid heat Built from real kills and real explosive damage over a window you choose, so the map shows you where the server is actually fighting rather than where you guessed it was. Same actions, straight from the map Search a player, click their marker, and the card next to the map carries the actions you picked - up to sixteen of them, chosen in Settings. Grouping instead of clutter Cupboards, bags and stashes can merge into counted cells rather than a thousand overlapping icons, per layer, whenever a wipe gets old.   04  ·  Running the server Console, plugins, permissions - without leaving the game Live console The real server console in the panel, tabbed into all, chat, commands, connections and errors. Search it, wrap it, export it to a file, run commands inline, or pop out a draggable mini-console and keep it on screen while you work. Permissions and groups Every permission on the server, grouped by the plugin that owns it, searchable across thousands of entries. Toggle per user or per group, create and delete groups, set parent inheritance. Plugins and ConVars Every loaded and unloaded plugin with title, author and version, loaded, unloaded or reloaded with a click. ConVars browsable by category, paginated and searchable, edited in place and persisted across restarts. Dashboard and logs Online and max players, sleepers, admins on duty, new players today, server FPS, entity count and the join queue - live. Underneath, an activity log of joins, leaves, chat, commands, admin actions and errors, filterable by category and kept in your storage backend. Storage that scales with you SQLite with zero configuration out of the box, plain JSON files if you prefer them, or MySQL when you run a network. Switching backend is one click in Settings and the data follows you across live. Discord, if you want it Webhook or a full bot, chosen per channel. Bans, kicks, chat, admin actions and plugin errors each route to their own channel, a two-way chat bridge links Discord to in-game, and slash commands come with autocomplete and role-based authorization. Entirely optional, configured in-game.   05  ·  Make it yours Your commands, your keys, your colours Quick buttons Turn any console command into a button with its own icon, colour and permission. Placeholders fill in the target's SteamID, name, coordinates and grid, or yours. Ask for confirmation on the dangerous ones. Show them on the player card, on the map, on the dashboard or in the widget. Binds Ready-made bind lines for the panel, Vanish, godmode, noclip, ESP, the hammer, inspect and the map. Pick your key, select the line, paste it into F1. One key toggles a tool on and off - no second bind for the way back. Appearance Three themes - Rust, Midnight, Plum - chosen per admin. A font per slot for titles, body, logs, console and HUD, ESP text size, a HUD readout of which tools are live, and a panel you can drag anywhere and have it remember where.   06  ·  Permissions Hand out exactly what you mean to Nineteen top-level permissions gate the pages and tools. On top of that, every action inside the player card registers its own powerfuladmin.player.NAME, and every quick button you create registers powerfuladmin.quickbtn.NAME. You can also lock PowerfulAdmin's own permissions so nobody edits their way upward. powerfuladmin.use Base access, opens the panel powerfuladmin.players Player roster and the management card powerfuladmin.map Server map powerfuladmin.hammer Admin hammer powerfuladmin.hammer.codes Reveal code lock codes in the hammer HUD powerfuladmin.esp ESP page and overlay powerfuladmin.vanish Vanish powerfuladmin.vanish.unlock Open code and key locks while vanished powerfuladmin.godmode Godmode toggle powerfuladmin.noclip Noclip toggle powerfuladmin.console Live console page and mini widget powerfuladmin.perms Permissions and groups manager powerfuladmin.logs Logs page powerfuladmin.plugins Plugin control powerfuladmin.convars ConVar editor powerfuladmin.quickbuttons Create and edit quick buttons powerfuladmin.settings Settings, storage, appearance and Discord powerfuladmin.viewip Reveal player IP addresses powerfuladmin.candisablevitals Edit player vitals and metabolism limits powerfuladmin.countableondashboard Counts toward the "admins online" figure Do not grant them one by one on day one. pa.setup <steamid or name> in the server console hands a player the full set at once, so you can be inside the panel a minute after install.   07  ·  Commands One in chat, three in console There is nothing else to memorise. The console ones exist so you can bind them to keys. /padmin Open the panel pa.open <page> Open the panel straight on a page, for example pa.open map pa.toggle <feature> Flip vanish, god, noclip, ESP, hammer or inspect - called without a value it toggles, so one key does both ways pa.setup <steamid|name> Grant the full permission set to a player, once, on install   08  ·  Install Four steps, and the fourth is optional 1 Drop the plugin into your scripts folder. It loads and writes a clean config on its own. Oxide and Carbon are both supported. 2 Run pa.setup <your name or steamid> once in the server console. 3 Type /padmin in game. You are in. 4 Later, in Settings: switch to MySQL, connect Discord, add a Steam API key for Rust hours, and copy your binds out of the Binds page.   09  ·  Add-ons Bans, Freeze and Whitelist, sold separately Three companion plugins drop straight into the sidebar and use the same card, the same permissions and the same storage backend. They are add-ons, not stubs - everything described above works without them. PowerfulBans Timed and permanent bans in their own database, reason templates, history and login enforcement. PowerfulFreeze Freeze a player in place while you talk to them, from the card, the map or the world. PowerfulWhitelist Closed-server whitelisting with JSON, SQLite or MySQL storage and its own standalone commands.   10  ·  Before you buy The questions that actually get asked Will it lag my server? It is built not to. Object pooling and reused buffers keep allocations down, only the element that changed repaints instead of the whole panel, saves are debounced, state is cached behind signatures, and ESP, inspect and the map run on intervals you can tune. Nothing runs for admins who are not looking at it. Is the ESP a cheat? No client mod is involved. It is drawn by the server through the engine's own debug draw and only sent to admins holding powerfuladmin.esp. Take the permission away and it stops existing for that admin. Can a junior moderator abuse it? Only as far as you let them. Every page has a permission, every action in the player card has its own permission, every quick button has one too, and PowerfulAdmin's own permissions can be locked so they cannot be edited from inside the panel. Do I need MySQL, or a database at all? No. SQLite is the default and needs no configuration. MySQL is there for networks that want shared data, JSON for people who like files, and moving between them is one click in Settings. Do I have to use Discord or a Steam API key? Neither. Discord is optional and set up in-game when you want it. The Steam key only fills in the "total Rust hours" figure on player cards; without it that one line says n/a and nothing else changes. Can I manage players who are offline? Yes. Teleport to a sleeper, heal, strip, edit the inventory, mute, change permissions. Only actions that need a live connection are disabled while they are away. Oxide or Carbon? Both. On Carbon the panel's internal commands are additionally protected, so nothing outside the panel can call them, while the public ones stay open for your binds. What language does it speak? Full English and Russian out of the box, and every single string lives in a language file, so another locale is a translation rather than a code change. Fonts without Cyrillic are marked in the picker. I write plugins. Can I hook into it? Yes. There is a section API for adding your own page to the sidebar with its access permission registered for you, plus calls such as API_KnownPlayers for the known-players list.   11  ·  For developers Your plugin, inside the panel PowerfulAdmin is not a closed panel. Any plugin can register its own sidebar section and render it inside the panel, in the player's language and in the admin's active theme. Bans, Freeze and Whitelist are built on this same public API. If you write plugins for your server, the sidebar, permissions, theming, player card and Settings page are already there for you. [PluginReference] private Plugin PowerfulAdmin; var definition = new Dictionary<string, object> {     ["id"]            = "mystats",     ["icon"]          = "assets/icons/star.png",     ["category"]      = "nav.cat.tools",     ["permission"]    = "myplugin.view",     ["title"]         = (Func<BasePlayer, string>)(p => "My Stats"),     ["open"]          = (Action<BasePlayer>)OpenSection,     ["cardRows"]      = (Func<string, List<string[]>>)CardRows,     ["settings"]      = (Action<BasePlayer, CuiElementContainer, string, int>)DrawSettings,     ["settingsHeight"] = (Func<BasePlayer, int>)(p => 180),     ["popupActions"]   = new Dictionary<string, Action<BasePlayer, ulong, string>>     {         ["ban"] = OnBan     } }; PowerfulAdmin.Call("API_AddSection", definition); Only id is required. Every other definition key is optional, and the permission is registered for you if no plugin has claimed it yet. id string  ·  Unique section id. Required. icon string  ·  Sidebar icon sprite. category string  ·  Nav group. Built in: nav.cat.main, nav.cat.tools, nav.cat.manage. Any other value creates a new group. permission string  ·  Permission needed to open the section. title Func<BasePlayer, string>  ·  Section title, so you can localise it per player. open Action<BasePlayer>  ·  Draw your page. cardRows Func<string, List<string[]>>  ·  Extra label and value rows on the player card. settings Action<BasePlayer, CuiElementContainer, string, int>  ·  Draw controls into a card on the Settings page. settingsHeight Func<BasePlayer, int>  ·  How tall that card is. popupActions Dictionary<string, Action<BasePlayer, ulong, string>>  ·  Extra buttons on the player card popup. var ctx = PowerfulAdmin.Call("API_SectionContext", player) as Dictionary<string, object>; var parent  = (string)ctx["parent"]; var bodyW   = Convert.ToInt32(ctx["bodyW"]); var pad     = Convert.ToInt32(ctx["pad"]); var palette = (Dictionary<string, string>)ctx["palette"]; Read the section context on every render. It provides the parent layer, body width and height, standard padding, the player's language code and the full theme palette. The admin can switch themes while your page is open. Use its page, bg, surface, elev, elev2, border, borderSoft, text, text2, text3, accent, accentH, accentSoft, accentText, danger, dangerSoft, success, warn, warnSoft, info, clear values and the fontBold, fontRegular, fontMono names to match every built-in theme. API_RemoveSection(string id) Unregister on Unload. API_OpenSection(BasePlayer player, string id) Open your section for a player. API_ReopenPanel(BasePlayer player) Reopen the panel where it was. API_RefreshPlayerCard(string steamId) Repaint the player card after your data changes. API_RefreshSettings(BasePlayer player) Repaint the settings page after saving a value. API_Log(string message, string category = null) Write into PowerfulAdmin's log section. API_KnownPlayers() Every player the server has seen, as a list of string arrays. API_RustHours(string steamId) Total Rust playtime from the Steam API, cached. API_GetInput(string key) Read a panel input value. API_GetToggle(string key, bool def) Read a panel toggle. API_GetSelect(string key, string def) Read a panel selector. Call API_RemoveSection in your Unload, and prefer repainting one named element over a full redraw so the panel does not jump under the admin's cursor. Support, updates and feature requests: LR Development Discord
5.0
330 Raidable bases by JaaaaaThomas All bases up until 08.06.2026  Important Reminder This is a Base Model Pack (.json files). It is NOT the Raidable Bases plugin script. These are the blueprints crafted by our professional building team.  Level Up Your Server Don't settle for basic cubes. Give your players a challenge they’ll never forget. Whether you're looking for a "Hardcore" event or a permanent fortress for your top clan, these 330  bases are built to dominate. [ Buy Now & Start Building] This package includes all of my other packages.
0.0
$9.99
An excellent plugin for remote trading between players with extensive functionality.   The ability to log successful trades; The ability to create new permissions; The ability to customize permissions flexibly, including both new and existing ones; The ability to limit slots in trade; The ability to configure the method(Personal, CommonMinimum, CommonMaximum) for limiting the number of slots; The ability to set a cooldown on sending trade requests; The ability to configure the method(InitiatorOnly, TargetOnly, Both) for applying cooldown to players; The ability to purchase a bypass for the trade request cooldown; The ability to set a daily limit on sending trade requests; The ability to purchase additional trade requests after reaching the daily limit; The ability to forbid trading when wounded; The ability to forbid trading while swimming; The ability to forbid trading while mounted on certain seats; The ability to forbid trading in specified monuments, by name or by monument type; The ability to forbid trading in someone else's building privileges; The ability to forbid trading when taking damage; The ability to forbid trading during a combat block; The ability to forbid trading during a raid block; The ability to forbid certain items from being traded; The ability to automatically generate language files for specified languages(with content filled in English); The ability to set an effect upon receiving a trade request; The ability to change the effect upon a successful trade completion; The ability to display a status bar while waiting for a trade; The ability to choose between bar types(TimeCounter and TimeProgressCounter); The ability to specify the order of the bar; The ability to change the height of the bar; The ability 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 ability to get images from the local folder(*SERVER*\oxide\data\AdvancedStatus\Images); The ability to set own image and customize the color and transparency of the image; The ability to set sprite instead of the image; The ability to customize the color, size and font of the text.   { "Chat command": "trade", "List of 'accept' commands": [ "accept", "yes" ], "List of 'cancel' commands": [ "cancel", "no" ], "Is it worth enabling GameTips for messages?": true, "Is it worth using Notify plugins for messages instead of the vanilla UI?": false, "Specify the regular message type for notify": 0, "Specify the warning message type for notify": 1, "Is it worth using the AdvancedStatus plugin?": true, "Is it worth saving trade logs to a file?": true, "List of language keys for creating language files": [ "en" ], "Slot limit calculation mode(Personal, CommonMinimum, CommonMaximum)": "CommonMaximum", "Trade cooldown apply mode(InitiatorOnly, TargetOnly, Both)": "InitiatorOnly", "Is it worth checking the target's trade cooldown?": false, "Time in seconds given to respond to a trade request": 15.0, "Price to skip 60 seconds of the trade request cooldown": 10.0, "The prefab name for the effect triggered when a trade request is received": "assets/bundled/prefabs/fx/invite_notice.prefab", "The prefab name for the effect triggered when a trade is successfully completed": "assets/prefabs/building/wall.frame.shopfront/effects/metal_transaction_complete.prefab", "List of mount names where trading is prohibited": [ "horsesaddle", "horsesaddlerear", "bikedriverseat", "bikepassengerseat", "motorbikedriverseat", "motorbikepassengerseat", "modularcardriverseat", "modularcarpassengerseatleft", "modularcarpassengerseatright", "modularcarpassengerseatlesslegroomleft", "modularcarpassengerseatlesslegroomright", "modularcarpassengerseatsidewayleft", "miniheliseat", "minihelipassenger", "transporthelipilot", "transporthelicopilot", "attackhelidriver", "attackheligunner", "submarinesolodriverstanding", "submarineduodriverseat", "submarineduopassengerseat", "snowmobiledriverseat", "snowmobilepassengerseat", "snowmobilepassengerseat tomaha", "workcartdriver", "locomotivedriver", "craneoperator", "batteringramseat", "ballistagun.entity" ], "Status. Bar - Display time in seconds. A value of 0 keeps it visible until the cooldown ends": 15.0, "Status. Bar - Type(TimeProgressCounter or TimeCounter)": "TimeCounter", "Status. Bar - Height": 26, "Status. Bar - Order": 10, "Status. Background - Color(Hex or RGBA)": "#EFC570", "Status. Background - Transparency": 0.7, "Status. Background - Material(Leave empty to disable)": "", "Status. Image - Url": "https://gitlab.com/IIIaKa/images/-/raw/main/StatusBars/Trader_Request.png", "Status. Image - Local(Leave empty to use Image_Url)": "Trader_Request", "Status. Image - Sprite(Leave empty to use Image_Local or Image_Url)": "", "Status. Image - Is raw image": false, "Status. Image - Color(Hex or RGBA)": "#EFC570", "Status. Image - Transparency": 1.0, "Status. Image Outline - Color(Hex or RGBA)": "0.1 0.3 0.8 0.9", "Status. Image Outline - Transparency": 1.0, "Status. Image Outline - Distance(Leave empty to disable). Example '0.75 0.75'": "", "Status. Text - Size": 12, "Status. Text - Color(Hex or RGBA)": "#FFFFFF", "Status. Text - Transparency": 1.0, "Status. Text - Font(https://umod.org/guides/rust/basic-concepts-of-gui#fonts)": "RobotoCondensed-Bold.ttf", "Status. Text - Offset Horizontal": 0, "Status. Text Outline - Color(Hex or RGBA)": "#000000", "Status. Text Outline - Transparency": 1.0, "Status. Text Outline - Distance(Leave empty to disable)": "", "Status. SubText - Size": 12, "Status. SubText - Color(Hex or RGBA)": "#FFFFFF", "Status. SubText - Transparency": 1.0, "Status. SubText - Font": "RobotoCondensed-Bold.ttf", "Status. SubText Outline - Color(Hex or RGBA)": "0.5 0.6 0.7 0.5", "Status. SubText Outline - Transparency": 1.0, "Status. SubText Outline - Distance(Leave empty to disable)": "", "Status. Progress - Background Color(Hex or RGBA)": "1 1 1 0.15", "Status. Progress - Background Transparency": 0.15, "Status. Progress - Reverse": true, "Status. Progress - Color(Hex or RGBA)": "#EFC570", "Status. Progress - Transparency": 0.7, "Status. Progress - OffsetMin": "0 0", "Status. Progress - OffsetMax": "0 0", "List of trade permissions": [ { "Permission Name": "trader.default", "Number of available trade slots": 3, "Cooldown time(in seconds) before next trade": 600.0, "Daily trade request limit. A value of 0 disables the limit": 50, "Price to purchase a trade after exceeding the daily limit. A value of 0 disables the purchase": 5.0, "Is it worth forbidding trade if the player is in a wounded state?": true, "Is it worth forbidding trade if the player is swimming?": true, "Is it worth forbidding trade if the player is mounted?": true, "Is it worth forbidding trade if the player is in someone else's building privilege area?": true, "Is it worth forbidding trade if the player has taken damage?": true, "Is it worth forbidding trade if the player has combat block?": true, "Is it worth forbidding trade if the player has raid block?": true, "List of monuments where trade is forbidden": null, "List of monument categories where trade is forbidden": [ "RadTown", "RadTownWater", "RadTownSmall", "TunnelStation", "Custom" ], "List of forbidden trade items": [ "rock" ] }, { "Permission Name": "trader.vip", "Number of available trade slots": 6, "Cooldown time(in seconds) before next trade": 450.0, "Daily trade request limit. A value of 0 disables the limit": 100, "Price to purchase a trade after exceeding the daily limit. A value of 0 disables the purchase": 2.5, "Is it worth forbidding trade if the player is in a wounded state?": true, "Is it worth forbidding trade if the player is swimming?": true, "Is it worth forbidding trade if the player is mounted?": true, "Is it worth forbidding trade if the player is in someone else's building privilege area?": true, "Is it worth forbidding trade if the player has taken damage?": true, "Is it worth forbidding trade if the player has combat block?": true, "Is it worth forbidding trade if the player has raid block?": true, "List of monuments where trade is forbidden": null, "List of monument categories where trade is forbidden": [ "RadTown", "RadTownWater", "TunnelStation" ], "List of forbidden trade items": [ "rock" ] }, { "Permission Name": "realpve.vip", "Number of available trade slots": 9, "Cooldown time(in seconds) before next trade": 300.0, "Daily trade request limit. A value of 0 disables the limit": 0, "Price to purchase a trade after exceeding the daily limit. A value of 0 disables the purchase": 0.0, "Is it worth forbidding trade if the player is in a wounded state?": false, "Is it worth forbidding trade if the player is swimming?": false, "Is it worth forbidding trade if the player is mounted?": false, "Is it worth forbidding trade if the player is in someone else's building privilege area?": false, "Is it worth forbidding trade if the player has taken damage?": false, "Is it worth forbidding trade if the player has combat block?": false, "Is it worth forbidding trade if the player has raid block?": false, "List of monuments where trade is forbidden": [ "oilrig_1" ], "List of monument categories where trade is forbidden": null, "List of forbidden trade items": [ "rock" ] } ], "Version": { "Major": 0, "Minor": 1, "Patch": 4 } }   EN: { "CmdNotAllowed": "You do not have permission to use this command!", "CmdPlayerNotFound": "Player '{0}' not found! You must provide the player's name or ID.", "CmdMultiplePlayers": "Multiple players found: {0}", "CmdEconomicsNotEnough": "Not enough funds!", "CmdMain": "Available trade commands:\n\n<color=#D1CBCB>/trade</color> <color=#D1AB9A>bars *boolValue*(optional)</color> - Toggle status bar display\n<color=#D1CBCB>/trade</color> <color=#D1AB9A>*nameOrId*</color> - Send a trade request to the specified player\n<color=#D1CBCB>/trade</color> <color=#83BA7C>accept/yes</color> - Accept a pending trade request\n<color=#D1CBCB>/trade</color> <color=#DE5757>cancel/no</color> - Decline a pending or active trade\n<color=#D1CBCB>/trade</color> <color=#D1AB9A>limits</color> - View your trade limits\n<color=#D1CBCB>/trade</color> <color=#D1AB9A>buy limits *amount*(optional)</color> - Purchase additional trade requests\n<color=#D1CBCB>/trade</color> <color=#D1AB9A>buy cd *amount*(optional)</color> - Purchase a 60 second(* by amount) cooldown skip\n\n--------------------------------------------------", "CmdBarsEnabled": "Status bar display enabled!", "CmdBarsDisabled": "Status bar display disabled!", "CmdDailyLimitExtra": "You have exceeded the daily limit({0}) for sending trade requests!\n<size=10>However, you can buy additional requests using the <color=#D1AB9A>/trade buy limits</color> command for <color=#D1CBCB>${1}</color></size>", "CmdDailyLimit": "You have exceeded the daily limit({0}) for sending trade requests!", "CmdCooldownSkip": "You must wait {0} seconds before sending another trade request!\n<size=10>However, you can skip the cooldown using the <color=#D1AB9A>/trade buy cd</color> command for <color=#D1CBCB>${1}</color> per 60 seconds</size>", "CmdCooldown": "You must wait {0} seconds before sending another trade request!", "CmdWoundBlock": "You can't trade while wounded!", "CmdSwimming": "You can't trade while swimming!", "CmdMountBlock": "You can't trade while mounted here!", "CmdBuildingBlock": "You can't trade inside someone else's base!", "CmdDamageBlock": "You can't trade while taking damage!", "CmdCombatBlock": "You can't trade during combat block!", "CmdRaidBlock": "You can't trade during a raid block!", "CmdAcceptEmpty": "You have no pending trade requests!", "CmdAcceptOngoing": "You already have an active trade with player '<color=#D1AB9A>{0}</color>'!", "CmdDeclineEmpty": "You have no pending or active trades!", "CmdDecline": "Trade between you and player '<color=#D1AB9A>{0}</color>' has been canceled!", "CmdDeclineOther": "Player '<color=#D1AB9A>{0}</color>' canceled the trade with you!", "CmdSendSelf": "You cannot send a trade request to yourself!", "CmdSendNoRespond": "Player '<color=#D1AB9A>{0}</color>' has not responded to your trade request!", "CmdSendAlredyHave": "You already have a pending or active trade with player '<color=#D1AB9A>{0}</color>'!\n<size=10><color=#83BA7C>/trade yes</color> - Accept the pending trade request\n<color=#DE5757>/trade no</color> - Decline the pending or active trade</size>", "CmdSendTargetNotAllowed": "Player '<color=#D1AB9A>{0}</color>' does not have permission to use trading!", "CmdSendTargetAlredyHave": "Player '<color=#D1AB9A>{0}</color>' already has a pending or active trade with player '<color=#D1AB9A>{1}</color>'!", "CmdSendTargetHasCooldown": "Player '<color=#D1AB9A>{0}</color>' has an active cooldown, {1} seconds remaining!", "CmdSendTo": "Trade request successfully sent to player '<color=#D1AB9A>{0}</color>'.", "CmdSendFrom": "Player '<color=#D1AB9A>{0}</color>' has sent you a trade request.\n<size=10><color=#83BA7C>/trade yes</color> - Accept the pending trade request\n<color=#DE5757>/trade no</color> - Decline the pending or active trade</size>", "CmdPurchaseNotLimited": "You haven't reached your daily limit yet!", "CmdPurchaseHaveExtra": "You still have {0} additional trade requests! Use them before purchasing more.", "CmdPurchaseLimitsNotAllowed": "Purchasing additional trade requests is unavailable!", "CmdPurchasedLimits": "You have successfully purchased <color=#D1CBCB>{0}</color> trade requests!\n<size=10>Now you have <color=#D1CBCB>{1}</color> additional trade requests</size>", "CmdPurchaseNoCooldown": "You don't have a cooldown for sending trade requests!", "CmdPurchaseCooldownNotAllowed": "Purchasing a cooldown skip for trade requests is not available!", "CmdPurchasedCooldown": "You have successfully purchased a cooldown skip for <color=#D1CBCB>{0} seconds</color> for trade requests!\n<size=10>Now you need to wait <color=#D1CBCB>{1} seconds</color></size>", "CmdMyLimits": "Your trade request limits:\n\n<color=#D1CBCB>Cooldown</color> - <color=#D1AB9A>{0} sec</color>\n<color=#D1CBCB>Daily Limit</color> - <color=#D1AB9A>{1}</color>\n\n--------------------------------------------------", "BarInitiator": "Trade to: {0}", "BarTarget": "Trade from: {0}", "BarCooldown": "Trade cooldown:", "MsgStarted": "You have started a trade with player '<color=#D1AB9A>{0}</color>'!", "MsgCompleted": "Trade with player '<color=#D1AB9A>{0}</color>' completed successfully!", "MsgCanceled": "Player '<color=#D1AB9A>{0}</color>' canceled the trade!" } RU: { "CmdNotAllowed": "У вас недостаточно прав для использования этой команды!", "CmdPlayerNotFound": "Игрок '{0}' не найден! Вы должны указать имя или ID игрока.", "CmdMultiplePlayers": "Найдено несколько игроков: {0}", "CmdEconomicsNotEnough": "Не достаточно средств!", "CmdMain": "Доступные команды для трейда:\n\n<color=#D1CBCB>/trade</color> <color=#D1AB9A>bars *булевоеЗначение*(опционально)</color> - Переключение отображения статус баров\n<color=#D1CBCB>/trade</color> <color=#D1AB9A>*имяИлиАйди*</color> - Отправить запрос на трейд указанному игроку\n<color=#D1CBCB>/trade</color> <color=#83BA7C>accept/yes</color> - Принять ожидающий запрос на трейд\n<color=#D1CBCB>/trade</color> <color=#DE5757>cancel/no</color> - Отклонить ожидающий или активный трейд\n<color=#D1CBCB>/trade</color> <color=#D1AB9A>limits</color> - Узнать свои лимиты\n<color=#D1CBCB>/trade</color> <color=#D1AB9A>buy limits *количество*(опционально)</color> - Докупить дополнительное количество трейд запросов\n<color=#D1CBCB>/trade</color> <color=#D1AB9A>buy cd *количество*(опционально)</color> - Купить пропуск 60 секунд(* на количество) задержки перед отправкой трейд запросов\n\n--------------------------------------------------", "CmdBarsEnabled": "Отображение статус баров включено!", "CmdBarsDisabled": "Отображение статус баров выключено!", "CmdDailyLimitExtra": "Вы превысили допустимую дневную норму({0}) на отправку трейд запросов!\n<size=10>Но вы можете купить дополнительные запросы с помощью команды <color=#D1AB9A>/trade buy limits</color> за <color=#D1CBCB>{1}$</color></size>", "CmdDailyLimit": "Вы превысили допустимую дневную норму({0}) на отправку трейд запросов!", "CmdCooldownSkip": "Перед отправкой нового запроса на трейд вам необходимо подождать {0} секунд!\n<size=10>Но вы можете купить пропуск задержки с помощью команды <color=#D1AB9A>/trade buy cd</color> за <color=#D1CBCB>{1}$</color> за каждые 60 секунд</size>", "CmdCooldown": "Перед отправкой нового запроса на трейд вам необходимо подождать {0} секунд!", "CmdWoundBlock": "Вам запрещено пользоваться трейдом в предсмертном состоянии!", "CmdSwimming": "Вам запрещено пользоваться трейдом в воде!", "CmdMountBlock": "Вам запрещено пользоваться трейдом сидя в данном месте!", "CmdBuildingBlock": "Вам запрещено пользоваться трейдом в чужой базе!", "CmdDamageBlock": "Вам запрещено пользоваться трейдом при получении урона!", "CmdCombatBlock": "Вам запрещено пользоваться трейдом во время боя!", "CmdRaidBlock": "Вам запрещено пользоваться трейдом во время рейда!", "CmdAcceptEmpty": "У вас нет ожидающих запросов на трейд!", "CmdAcceptOngoing": "У вас уже есть активный трейд с игроком '<color=#D1AB9A>{0}</color>'!", "CmdDeclineEmpty": "У вас нет ожидающих или активных трейдов!", "CmdDecline": "Трейд между вами и игроком '<color=#D1AB9A>{0}</color>' отменён!", "CmdDeclineOther": "Игрок '<color=#D1AB9A>{0}</color>' отменил трейд с вами!", "CmdSendSelf": "Нельзя отправить трейд запрос самому себе!", "CmdSendNoRespond": "Игрок '<color=#D1AB9A>{0}</color>' не ответил на ваш трейд запрос!", "CmdSendAlredyHave": "У вас уже есть ожидающий или активный трейд с игроком '<color=#D1AB9A>{0}</color>'!\n<size=10><color=#83BA7C>/trade yes</color> - Принять ожидающий запрос на трейд\n<color=#DE5757>/trade no</color> - Отклонить ожидающий или активный трейд</size>", "CmdSendTargetNotAllowed": "У игрока '<color=#D1AB9A>{0}</color>' недостаточно прав для использования обмена!", "CmdSendTargetAlredyHave": "У игрока '<color=#D1AB9A>{0}</color>' уже есть ожидающий или активный трейд с игроком '<color=#D1AB9A>{1}</color>'!", "CmdSendTargetHasCooldown": "У игрока '<color=#D1AB9A>{0}</color>' имеется активный кулдаун, осталось {1} секунд!", "CmdSendTo": "Игроку '<color=#D1AB9A>{0}</color>' был успешно отправлен запрос на трейд.", "CmdSendFrom": "Игрок '<color=#D1AB9A>{0}</color>' отправил вам запрос на трейд.\n<size=10><color=#83BA7C>/trade yes</color> - Принять ожидающий запрос на трейд\n<color=#DE5757>/trade no</color> - Отклонить ожидающий или активный трейд</size>", "CmdPurchaseNotLimited": "Вы ещё не исчерпали свой дневной лимит!", "CmdPurchaseHaveExtra": "У вас ещё есть {0} дополнительных трейд запросов! Используйте их прежде, чем покупать новые.", "CmdPurchaseLimitsNotAllowed": "Покупка дополнительных трейд запросов недоступна!", "CmdPurchasedLimits": "Вы успешно докупили <color=#D1CBCB>{0}</color> трейд запросов!\n<size=10>Теперь у вас <color=#D1CBCB>{1}</color> дополнительных трейд запросов</size>", "CmdPurchaseNoCooldown": "У вас нет задержки на отправку трейд запросов!", "CmdPurchaseCooldownNotAllowed": "Покупка пропуска задержки на трейд запросы недоступна!", "CmdPurchasedCooldown": "Вы успешно купили пропуск на <color=#D1CBCB>{0} секунд</color> задержки для трейд запросов!\n<size=10>Теперь вам нужно подождать <color=#D1CBCB>{1} секунд</color></size>", "CmdMyLimits": "Ваши лимиты трейд запросов:\n\n<color=#D1CBCB>Время задержки</color> - <color=#D1AB9A>{0} сек</color>\n<color=#D1CBCB>Дневной лимит</color> - <color=#D1AB9A>{1}</color>\n\n--------------------------------------------------", "BarInitiator": "Трейд с: {0}", "BarTarget": "Трейд от: {0}", "BarCooldown": "Задержка трейда:", "MsgStarted": "Вы начали трейд с игроком '<color=#D1AB9A>{0}</color>'!", "MsgCompleted": "Трейд с игроком '<color=#D1AB9A>{0}</color>' успешно завершён!", "MsgCanceled": "Игрок '<color=#D1AB9A>{0}</color>' отменил трейд!" }   bars *boolValue*(optional) - Toggle status bar display. *nameOrId* - Send a trade request to the specified player. accept/yes - Accept a pending trade request. cancel/no - Decline a pending or active trade. limits - View your trade limits. buy limits *amount*(optional) - Purchase additional trade requests. buy cd *amount*(optional) - Purchase a 60 second(* by amount) cooldown skip. Example: /trade bars true /trade iiiaka /trade yes /trade limits /trade buy limits 1 /trade buy limits 0.5
0.0
Highest Rated
Top-rated picks trusted and loved by the community.
Trending Files
Popular picks members are downloading the most right now.
Great Deals
Discounted picks, limited-time deals, and sale items worth grabbing now.
Latest Reviews
See what customers are saying about their experience with files.
Unfortunately, this plugin has been abandoned for years now. There's a disconnect between the plugin and the site where it doesn't show accurate information. Dev hasn't responded to two my support tickets in months. Any updates where explained with "Use the older version"  Picture below shows the website stating my server hasn't wiped in two months. 
I was a bit sceptical at first because of bad experiences with the last "enchanting" plugin, tough the documentation is awesome and the possibilites are endless. But this plugin is developed actively and the dev helped out very fast with all problems and wishes I had. I'm really looking forward to the next "armor" step 🙂 Recommended !
Absolutely fantastic plugin! This plugin makes it incredibly easy to create beautiful and impressive fireworks shows. The included shows are very well designed, and the timing and presentation are excellent. You can really feel the developer’s great sense for creating a spectacular show. What impressed me just as much as the plugin itself was the support. Whenever I had a question or encountered an issue, the developer responded very quickly and kindly, and worked to help resolve it.
An absolutely solid map, didn't discover big mistakes yet. Some really interesting custom places/monuments. Even some with a portion humour, like a car accident 🙂 Also Litum was always very quick with help if there was a question.  Recommended !
Loving this game! its like a whole game itself.  Its got me addicted to coming back and trying to get new scraplings.  I think you can tell what i was inspred by 😄 and its such great fun!
happy with this plugin as it both looks and feels really good .  The Advanced Apartment plugin completely shifts how players live and progress on a Rust server. Instead of just being a place to log off safely, it turns an apartment into a fully functional base. i hope more gets added it be fun to see i pay more to
Solid plugin.  My Players absolutely love it.  With the new volume that facepunch added this completely completes the radio experience.  Thank you for your hard work.
Such a great quality of life addon.  This just fills a need that I didn't know how to fix.  Thank you for your time and effort putting this together.  

About Us

Codefling is the largest marketplace for plugins, maps, tools, and more, making it easy for customers to discover new content and for creators to monetize their work.

Downloads
2.9m
Total downloads
Customers
11.8k
Customers served
Files Sold
168.2k
Total sales
Payments
3.6m
Processed total
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.