igraes's Wishlist

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!  ❤️
 
 

🧹 CarbonCleaner
 
 
 
🧩 Short description
Finds orphaned files in `carbon/config/`, `carbon/data/`, and `carbon/lang/` based on the installed/loaded plugins and provides a sleek in-game CUI for selecting and deleting them.
 
⚙️ Features
- Matching logic (plugin detection)
  - Reads plugin base names from `carbon/plugins` (`*.cs`) **and** from the Carbon runtime (loaded plugins).
  - Base names `Admin` and `CorePlugin` are always treated as present.
 
- Scan areas
  - config: Top-level `*.json` and top-level folders whose base name does not correspond to a plugin.
  - data: Top-level files (except `*.data`/`*.db`) and top-level folders without a plugin match.
  - lang: `lang/<LOCALE>/*.json` whose base name does not correspond to a plugin.
 
- UI (CUI)
  - Three columns: CONFIG, DATA, LANG with count, file size, and checkboxes.
  - Select All for CONFIG/DATA, language sections can be expanded/collapsed for LANG.
  - Delete button shows number of selections; after deletion, automatic rescan.
 
  - Secure deletion
  - Deletes only within the `carbon/` root (path is validated).
  - Supports files **and** folders (recursively).
 
  - Backup
  - You have the option to decide whether you want to back up individual files..
 
> Note: `*.data` and `*.db` in the **data** root are **not** listed as orphaned (are skipped). This protects runtime databases.
 
💬 Commands
 
In-Game (Chat)
- `/carboncleaner` — Opens the UI (requires permission).
 
Server console
- `carboncleaner.scan` — Shows number/size of hits.
- `carboncleaner.delete “<relativePath>|<relativePath>|...”`  
  Example:  
  `carboncleaner.delete “config/Old.json|data/OldFolder|lang/en/Old.json”`  
  Deletes the specified relative paths under `carbon/`.
 
 
 
🔐 Permissions
- `carboncleaner.admin` — required for all functions (chat/UI).
 
 
 


 

DISCLAIMER
Due to Rust modding limitation, the turret head always face up, this have no impact on how the turret function.

This is how the roof turret will look like in game :



Elevate your players gameplay with Roof Turret!

For surprising new angles, enhanced roof control or hidden jump-up traps,
Roof Turret unlocks new defense options for defenders while posing fresh challenges to raiders.
 
Key Features
- Place auto turrets/flame turrets on roof undersides with precise rotation control
- Tailored placement system
- Intuitive UI indicator for valid/invalid placement
- Configurable deployed roof turret limit per User / VIP
(If enabled & on placement, inform player of his turret limit left via private chat message)
 

2025-03-26 18-27-46.mp4
Installation
Paste RoofTurret.cs in your  rustserver\[oxide-carbon]\plugins folder.


Permission
roofturret.vip roofturret.vip is used for the following config options :
- VIP only roof turret placement
- Increased VIP deployed roof turret limit

Use oxide.grant  to give this permission


Configuration
 
{ "VIP Only": { "Disable roof auto turret for non-VIP (true/false)": false, "Disable roof flame turret for non-VIP (true/false)": false }, "VIP Settings": { "How many roof auto turrets can a VIP place (0 = unlimited)": 0, "How many roof flame turrets can a VIP place (0 = unlimited)": 0 }, "User Settings": { "How many roof auto turrets can a User place (0 = unlimited)": 0, "How many roof flame turrets can a User place (0 = unlimited)": 0 } } "Error message for non-VIP" is privately send when a non-VIP player tries to place a roof auto turret


Have a request or a concern ?
DM me on Codefling  or comment below.
Feedbacks are always welcomed 🙂
 

Event-tournament duels between players (1x1, 2x2, 3x3, etc)
Event goal
Players duel among themselves until the last survivor. In a situation with team muzzles, first they duel in teams, and then if there are not enough players for a team duel, then among themselves.

 
What features:
- Outsiders cannot enter the arena
- Tournament participants in the role of spectators do not take damage and have a hardened metabolism
- All things are saved and given to the participants after leaving the tournament, in the same form in which they were
- After the event, the player returns to the same place from where he teleported to him
- After a duel in the arena, all items dropped from duelists are cleaned
- There is an API for compatibility between plugins
- There is a blocking of prohibited chat and console commands in the tournament
- Very thoughtful matchmaking generator for duels
- Present UI
- There is a full-fledged plugin setting with great functionality
- There is an automatic start of tournaments after a certain time
- Easy installation and configuration

 
Installation:
- Install CopyPaste [https://umod.org/plugins/copy-paste]
- Install ArenaTournament
- Ready 🙂

Commands:
/qq - register for the tournament [optional, as there is a button with UI]

 
Admin commands:
/o - launch a random tournament [admin or permission arenatournamentbeta.admin]
at.start - start random tournament [admin]
at.copy name of existing name of new - copy arena settings to create a new one [admin]

 
Creating a new arena:
Build an arena
Put resources in the closet so that it would be enough for a wipe and hide it
Place the spawn point of the first team using regular chairs [https://rustlabs.com/item/chair]
Set a spawn point for the second team using gaming chairs [https://rustlabs.com/item/secret-lab-chair]
Set a spectator respawn point using sirens [https://rustlabs.com/item/siren-light]
Save arena /copy name
Add the arena to the config using the command at.copy nameexisting namenew
Open plugin config
Change in the config in your new arena "Position [coordinates]" to random, but within the map (not outside the grid!)
Set up the arena (Important! Do not specify "Tournament Modes" more than you have specified spawn locations for each of the teams)
Restart plugin
 
API:
API: [PluginReference] Plugin ArenaTournament; private bool IsOnTournament(ulong userid) { return ArenaTournament != null && ArenaTournament.Call<bool>("IsOnTournament", userid); } private bool IsDueling(BasePlayer player) { return ArenaTournament != null && ArenaTournament.Call<bool>("IsOnTournament", player); }  
Arena pack:
https://haxlite.ru/fermens_Arenas.zip

Demonstration:
from the buyer
 

✨ TC Controller 

A premium quality of life Rust plugin that gives players fast, safe, and clean Tool Cupboard management through an in-game UI
No more sprinting to every TC to manually top them up.
 
📌 What it does
🖥️ One command, instant TC control
Use /tc (configurable) to open a slick TC management panel that lists every Tool Cupboard you’re authorized on within a configurable radius.
Each TC entry shows the essentials at a glance:
- 📍 Distance to the cupboard
- ⏳ Upkeep protection time with clear colour status (Green / Yellow / Red / Decaying)
- 👥 Authorized player count
- 📦 Storage usage (slots used / capacity)
------------------------------------------------------------------------------------------------------------------
⚡ Fast upkeep deposits (no hassle)

Top up the selected TC directly from your inventory:
- 🌲 Wood
- 🪨 Stone
- 🔩 Metal Fragments
- 💎 HQM
Includes easy deposit buttons:
- ✅ Configurable quick amounts (e.g. 100 / 1,000 / 5,000 / 10,000)
- ✅ Plus an ALL button for instant full transfer
------------------------------------------------------------------------------------------------------------------
🔥 Top Up multiple cupboards in one click

Got more than one tc? No problem.
Use Top Up to distribute upkeep across all nearby authorized TCs, with smart filters:
- 🔵 Top up ALL
- 🟢 Green only
- 🟡 Yellow only
- 🔴 Red only
Perfect for large compounds
------------------------------------------------------------------------------------------------------------------
🧠 Smart sorting + organization

Keep things tidy with built-in sorting options:
- 📍 Sort by Distance
- 🏷️ Sort by Nickname
- ⏱️ Sort by Protection status/time
Add custom TC nicknames (saved per-player) like:
- “Main”
- “Compound”
- “Farm”
- “External”
…and instantly find what you need.
------------------------------------------------------------------------------------------------------------------
🛡️ Built-in protection against abuse (raid-friendly)
🚨 Optional Raid Block system
If a building is taking damage and the attacker is not authorized on its cupboards, the building is flagged as “being raided” for a configurable duration.
While raid-blocked, the UI prevents:
- ❌ Empty TC
- ❌ Repair Base
This helps stop “evacuate everything” or “instant repair” abuse mid raid.
🚪 Optional Exterior Entry Access Check (Anti “Through-Walls” Abuse)
To prevent “through-walls” style TC interaction, you can enable an extra rule:
A TC is only usable through the UI if the plugin can detect a legitimate exterior entry path to the building (anti-bunker / anti-sealed-base abuse).
------------------------------------------------------------------------------------------------------------------
🧰 Extra convenience tools
📤 Empty TC to inventory
Move as much as possible into your inventory (anything that can’t fit stays in the TC).
🔧 Repair Base (inventory-based)
Scan nearby building pieces and repair them using materials from the player’s inventory 
🔁 Undo last deposit
Made a mistake? TC Controller supports a short undo window that can return deposited items back to you when possible.
------------------------------------------------------------------------------------------------------------------
🔐 Permissions & access control

- ✅ tccontroller.use — allows players to use the UI