IQTeleportation - is an advanced, optimized teleportation system that provides a wide range of features to improve player comfort and convenience. Only the necessary, user-friendly features — the plugin isn’t overloaded with extras. All capabilities are designed for stability and maximum player convenience. Plugin Installation : When you download the resource, you receive an archive with plugins and data folders. Move the file from data strictly following the archive path: oxide/data/IQSystem/IQTeleportation. If any of these files don’t exist on your server, create them. Move IQTeleportation.cs from plugins strictly following the archive path: oxide/plugins. Note for users who use a “web editor” on hosting panels. Before uploading, unpack the archive locally in any convenient place, then upload the files from there. Feature List : Minimalist UI for the player : The plugin supports UI for teleport requests and for setting a home point. These are optional and configured in the config. Teleport directly into vehicles : Optional feature. Allows accepting a teleport while controlling a vehicle. The player will be teleported into a free seat; if there are no free seats, the teleport is canceled. Sound effects : Built-in sound effects for teleportation. Players can feel the timer through sound: as teleport time approaches, the sound frequency increases. This makes it clear when a teleport to a friend or home point will occur, without distracting from gameplay and keeping focus. Home points on G-Map : Optional feature. Displays the last 6 home points the player teleported to directly on the G-Map, with the ability to teleport to them via the UI. It fits the Rust and G-Map style nicely and is very convenient for players! Teleport requests via G-Map : Now you can simply right-click on a friend’s nickname (or near it) on the G-Map, and a teleport request will be sent automatically. This helps players stay focused on gameplay and simplifies team interactions. Automatic teleport between friends : The plugin supports automatically accepting teleport requests from friends. This feature can be toggled with the /atp command. Players in a team no longer need to confirm requests manually — friend teleports will happen automatically, making co-op play even more comfortable. Block teleporting from monuments : You can forbid teleporting from specific monuments. This improves gameplay and prevents using monument structures as a hideout followed by teleporting away from an opponent, creating a more balanced experience for everyone. Home point marker : After setting a home point, the player automatically gets a duplicate marker with the point’s name on their G-Map. This improves visibility, helps orientation, and simplifies coordination with home points. A temporary mark with a visual effect is also shown at the placement location. Simplified commands :  The goal is to simplify usage and add convenience for players — commands weren’t overlooked: /sethome has a shorter alias /sh /removehome has a shorter alias /rh /tpr has “built-in memory,” making player interaction easier. You no longer need to specify a nickname every time you send a teleport request. The command remembers the last player you teleported to, and when you run /tpr again without a name, it will send the request to that player. This makes teleporting even faster and more convenient. See the full command list in the “Commands” section. WARP system : The plugin includes a warp system with multiple points and convenient commands. What is this system for? For example, you want players to teleport to Outpost (or any other monument) with /compound — you can do this with the system: just create the points, and the commands will be registered automatically and will persist every server wipe! Other uses? Use it however you like: for events, create a teleport point for the event, then remove the warp after it’s over. Points placed outside standard monuments will not be saved after a map change. Logging system : If you want to monitor the plugin and know about your players’ teleports to analyze activity, there’s an optional logging feature for teleport requests, accepted teleports, and home teleports. There are many simple, clear configuration options — you can preview them in the “Configuration” section. Permissions : iqteleportation.gmap — permission to use /gmap and instant admin teleports via G-Map to any point on the map iqteleportation.tp — permission to use /tp for instant teleport to a player iqteleportation.warpadmin — for using WARP features and the /warp command These permissions are intended for administrators only and do not affect player features. Do not grant them to regular players! Command List :  Chat Commands : /atp – toggle automatic acceptance of teleport requests from friends /sethome Name – set a home point at your current position /sh Name – shorthand alias for /sethome /removehome Name – remove a previously set home point /rh Name – shorthand alias for /removehome /home NameHome – teleport to your home point /home NameHome FriendName – teleport to a friend’s home point /homelist – view all your home points /tpr Name – send a teleport request to a player /tpr – send a teleport request to the last player who accepted your request /tpa – accept a teleport request /tpc – cancel a teleport request Warp System : /warp list – show all available warps /warp points WarpName – show all teleport points for the specified warp /warp add WarpName – create a new warp or add an extra teleport point to that warp /warp edit WarpName PointNumber – edit a specific teleport point for the warp /warp remove WarpName – remove the warp and all its teleport points /warp remove WarpName PointNumber – remove the specified teleport point of the warp /NAMEWARP – command to teleport to a warp; created automatically based on your warp name For Administrators :  /gmap – enable teleporting to any position via G-Map by right-clicking the map /tp Name – instantly teleport to a player /tp Name NameTwo – instantly teleport player “Name” to player “NameTwo” /mblock – block teleportation from the monument where the admin is currently standing /a.home points NameOrID – show all named home points of the specified player /a.home clear NameOrID – delete all home points of the specified player Console Commands :  atp – toggle automatic acceptance of teleport requests from friends sethome Name – set a home point at your current position sh Name – shorthand alias for sethome removehome Name – remove a previously set home point rh Name – shorthand alias for removehome home NameHome – teleport to your home point home NameHome FriendName – teleport to a friend’s home point homelist – view all your home points tpr Name – send a teleport request to a player tpr – send a teleport request to the last player who accepted your request tpa – accept a teleport request tpc – cancel a teleport request For Administrators : gmap – enable teleporting to any position via G-Map by right-clicking the map tp Name – instantly teleport to a player tp Name NameTwo – instantly teleport player “Name” to player “NameTwo” Configuration :  { "General plugin settings": { "Log player actions to file (true = yes / false = no)": false, "Use sound effects (true = yes / false = no)": true, "Use GameTip messages instead of chat (true = yes / false = no)": false, "Wake the player immediately after teleport (otherwise they remain 'sleeping') (true = yes / false = no)": false, "List of monuments where teleportation is forbidden (applies to home points / teleport-to-player / warps)": [], "IQChat settings": { "IQChat : Custom prefix in the chat": "[IQTeleportation]", "IQChat : Custom avatar in the chat (Steam64ID) (If required)": "0" }, "SimpleStatus settings": { "SimpleStatus: Enable plugin support": false, "SimpleStatus: UI settings for teleportation": { "SimpleStatus: Background panel color": "0.3 0.3 0.3 0.5", "SimpleStatus: Prefix translations [LanguageKey] = Text": { "ru": "Телепортация", "en": "Teleporation" }, "SimpleStatus: Prefix color": "0.5647059 0.5490196 0.5333334 1", "SimpleStatus: UI sprite": "assets/icons/stopwatch.png", "SimpleStatus: Sprite color": "0.5647059 0.5490196 0.5333334 1" } } }, "Teleport-to-player settings": { "Teleport request settings": { "Offer to accept teleport requests in the UI (true = yes / false = no)": true, "Teleportation mode: true — teleport the player to the position where the request was accepted; false — teleport the player to the other player regardless of where it was accepted": false, "Allow players to send teleport requests via G-Map (true = yes / false = no)": true, "Use instant teleport to a point via G-Map (true = yes / false = no) (requires admin rights or the iqteleportation.gmap permission)": true, "Disable teleportation features on the server (tpr and tpa will be unavailable) (true = yes / false = no)": false, "Forbid sending and accepting teleport requests while the player is in a vehicle (true); otherwise teleport directly into the vehicle if a seat is free (false)": true, "Block sending and accepting teleport requests in a safe zone (true = yes / false = no)": false, "Block sending and accepting teleport requests during raid block (true = yes / false = no)": true, "Block sending and accepting teleport requests while the player is in the subway (train tunnels) (true = yes / false = no)": true, "Block sending and accepting teleport requests while the player is in the Underwater Lab (true = yes / false = no)": true, "Block sending and accepting teleport requests while the player is on the Cargo Ship (true = yes / false = no)": true, "Block sending and accepting teleport requests while the player is in a hot air balloon (true = yes / false = no)": true, "Block sending and accepting teleport requests while the player is cold (freezing) (true = yes / false = no)": true, "Block sending and accepting teleport requests while the player is swimming (true = yes / false = no)": true, "Block sending and accepting teleport requests while the player is under radiation (true = yes / false = no)": true, "Block sending and accepting teleport requests while the player is bleeding (true = yes / false = no)": true, "Block sending and accepting teleport requests while the player is in another player's building privilege area (building blocked) (true = yes / false = no)": true, "Allow teleportation only to friends (true = yes / false = no)": false }, "Teleport-to-player cooldown settings": { "Default count for players without permissions": 60, "Count overrides for players with permissions [Permission] = Count": { "iqteleportation.vip": 45, "iqteleportation.premium": 35, "iqteleportation.gold": 25 } }, "Teleport-to-player countdown settings": { "Default count for players without permissions": 20, "Count overrides for players with permissions [Permission] = Count": { "iqteleportation.vip": 15, "iqteleportation.premium": 10, "iqteleportation.gold": 5 } }, "Teleport-to-player limit settings": { "Use player teleport-to-player limits (true = yes / false = no)": false, "Hours until player limits are reset": 24, "Player teleport limit settings": { "Default count for players without permissions": 15, "Count overrides for players with permissions [Permission] = Count": { "iqteleportation.vip": 20, "iqteleportation.premium": 25, "iqteleportation.gold": 30 } } } }, "Home points settings": { "Allow teleporting to a friend's home point (true = yes / false = no)": true, "Enable UI with recent home points on G-Map (true = yes / false = no)": true, "Offer setting a home point in the UI after placing a bed or sleeping bag (true = yes / false = no)": true, "Allow players to teleport to a home point via G-Map (true = yes / false = no)": false, "Block home teleports in a safe zone (true = yes / false = no)": false, "Add a visual ping effect to the home point after it’s set (true = yes / false = no)": true, "Add a marker on the player’s G-Map after setting a home (true = yes / false = no)": true, "Permissions for setting home points": { "Block setting a home point during raid block (true = yes / false = no)": true, "Allow setting home points on tugboats (true = yes / false = no)": false, "Allow setting home points only when building privilege is present (true = yes / false = no)": true, "Allow setting home points only when authorized in the building privilege area (true = yes / false = no)": true }, "Home point count settings": { "Default count for players without permissions": 2, "Count overrides for players with permissions [Permission] = Count": { "iqteleportation.vip": 3, "iqteleportation.premium": 4, "iqteleportation.gold": 5 } }, "Home teleport cooldown settings": { "Default count for players without permissions": 30, "Count overrides for players with permissions [Permission] = Count": { "iqteleportation.vip": 25, "iqteleportation.premium": 20, "iqteleportation.gold": 15 } }, "Home teleport countdown settings": { "Default count for players without permissions": 20, "Count overrides for players with permissions [Permission] = Count": { "iqteleportation.vip": 15, "iqteleportation.premium": 10, "iqteleportation.gold": 5 } }, "Home teleport limit settings": { "Use player home-teleport limits (true = yes / false = no)": false, "Hours until player limits are reset": 12, "Home teleport limit settings": { "Default count for players without permissions": 15, "Count overrides for players with permissions [Permission] = Count": { "iqteleportation.vip": 20, "iqteleportation.premium": 25, "iqteleportation.gold": 30 } } } }, "Warp system settings": { "Enable warp support (true = yes / false = no)": false, "Block teleport to a warp if the player is hostile (safe-zone aggression) (true = yes / false = no)": true, "Teleport-to-warp cooldown settings": { "Default count for players without permissions": 120, "Count overrides for players with permissions [Permission] = Count": { "iqteleportation.vip": 100, "iqteleportation.premium": 80, "iqteleportation.gold": 60 } }, "Teleport-to-warp countdown settings": { "Default count for players without permissions": 30, "Count overrides for players with permissions [Permission] = Count": { "iqteleportation.vip": 25, "iqteleportation.premium": 20, "iqteleportation.gold": 15 } }, "Permissions for teleporting to specific warps: [WarpKey] = Permission (otherwise available to everyone)": { "warpName": "iqteleportation.warpPermission" }, "Teleport-to-warp limit settings": { "Use player teleport-to-warp limits (true = yes / false = no)": false, "Hours until player limits are reset": 6, "Teleport-to-warp limit settings": { "Default count for players without permissions": 15, "Count overrides for players with permissions [Permission] = Count": { "iqteleportation.vip": 20, "iqteleportation.premium": 25, "iqteleportation.gold": 30 } } } } } For Developers :  API : private void ClearHomesPlayer(UInt64 userID, String pluginName) // Clears all home points of the player. private Boolean API_HavePendingRequest(BasePlayer player) // Returns true if the player has an active (pending) teleport request. private Dictionary<String, Vector3> GetHomes(UInt64 userID) // Returns all home points of the player. Hooks :   private Object CanTeleport(BasePlayer player) // Called when attempting to teleport to a player. // Return a string with the reason to cancel the teleport. private Object canTeleport(BasePlayer player) // Same as above (alternate hook name). // Return a string with the reason to cancel the teleport. private Object OnTeleportRequested(BasePlayer player, BasePlayer requester) // Called when a teleport request is sent to a player. // You can cancel by returning false (bool) or a String (your message). private Object CanTeleportHome(BasePlayer player, Vector3 positionHome) // Called when attempting to teleport home. // You can cancel by returning a String with the reason. private Object OnHomeAdd(BasePlayer player, String homeName, Vector3 positionHome) // Called when attempting to set a home point. // You can cancel by returning a String with the reason. private void OnTeleportRejected(BasePlayer player, BasePlayer requester) // Called when a teleport request to a player is canceled/rejected. private void OnTeleportAccepted(BasePlayer player, BasePlayer requester, Int32 countdown) // Called when a teleport request is accepted. private void OnPlayerTeleported(BasePlayer player, Vector3 playerPos, Vector3 teleportationPos) // Called after the player has been teleported. private void OnHomeAccepted(BasePlayer player, String homeName, Int32 countdown) // Called after the player has sent a teleport-home request. private void OnHomeAdded(BasePlayer player, Vector3 positionHome, String homeName) // Called after a home point has been set. private void OnHomeRemoved(BasePlayer player, Vector3 positionHome, String homeName) // Called after a home point has been removed. private Object CanTeleportWarp(BasePlayer player) // Called when a player tries to teleport to a warp. // Return a string to cancel; return null to ignore (allow). private Object CanTeleportHome(BasePlayer player, Vector3 positionHome) // Called when a player tries to teleport to a home point. // Return a string to cancel; return null to ignore (allow). private Object CanTeleportPlayer(BasePlayer player) // Called when a player tries to teleport to another player. // Return a string to cancel; return null to ignore (allow). private void OnPlayerTeleported(BasePlayer player, BasePlayer target) // Called when a player has teleported to another player. private void OnPlayerTeleportedWarp(BasePlayer player, Vector3 positionWarp) // Called when a player has teleported to a warp. private void OnPlayerTeleportedHome(BasePlayer player, Vector3 positionHome) // Called when a player has teleported to a home point.  

Features Target Designator System: Players receive a binocular designator. Aim and left-click to mark a target point and call in an airstrike Strike and Nuke Support: Supports both standard F15 Strike and F15 Nuke runs, each with independent settings for planes, shots, rocket speed, delay, cooldown, and more Strike Modes: Includes multiple strike patterns: precise, circle, line, and carpet Custom F15 Flight: Flight altitude, plane speed, and pre-fire distance are fully configurable Aircraft spawn, fly their attack run, fire, and clean up automatically when the strike is complete Rocket Mechanics: Configurable rocket speed, rate of fire, shots per plane, plane stagger, and impact spread Direct Designator Delivery: Admins can deliver Strike or Nuke designators directly to players using the give subcommand In-Game Store: Optional in-game store support for purchasing Strike and Nuke designators. Supports Auto, Economics, and ServerRewards providers Admin Control Panel: Includes an in-game admin panel for managing store settings, strike settings, warnings, and zone restrictions without editing the config manually Combat Alerts: Includes target-marked warnings, inbound warnings, and countdown alerts with map grid support Blocked Use Zones: Can block strike usage while the caller is inside a safe zone, and can also block target points inside safe zones or monument bounds Commands are configurable from the config Permissions f15estrike.strike → allows using Strike designators f15estrike.nuke → allows using Nuke designators f15estrike.strike.give → allows giving Strike designators to other players f15estrike.nuke.give → allows giving Nuke designators to other players f15estrike.admin → full admin access and admin panel access Commands /f15 → opens the in-game F15 store /strike → gives the player an F15 Strike designator /nuke → gives the player an F15 Nuke designator /strike give <name|SteamId64> → gives an F15 Strike designator to another player /nuke give <name|SteamId64> → gives an F15 Nuke designator to another player Config { "Config Version": 3, "Flight altitude (m)": 250.0, "Plane speed (m/s)": 200.0, "Pre-fire distance (m)": 750.0, "Chat prefix": "[F15]", "Commands": { "Strike": { "Enabled": true, "Primary": "strike", "Aliases": [] }, "Nuke": { "Enabled": true, "Primary": "nuke", "Aliases": [] } }, "Blocked use zones": { "Block caller while inside a safe zone": true, "Block target point inside a safe zone": true, "Block target point inside monument bounds": false }, "Global warnings": { "Enabled": true, "Broadcast when target is marked": true, "Broadcast countdown reminders": true, "Countdown warning seconds": 5, "Broadcast when aircraft are inbound": true, "Include map grid": true, "Include world coordinates": true }, "Purchases": { "Enabled": false, "Provider (Auto/Economics/ServerRewards)": "Auto", "Strike": { "Enabled": true, "Cost": 1500.0 }, "Nuke": { "Enabled": true, "Cost": 10000.0 } }, "Strike": { "Planes (count)": 1, "Shots per plane": 10, "Rocket speed (m/s)": 150.0, "Rate of fire (shots/sec)": 2.5, "Stagger between planes (s)": 0.25, "Impact spread radius (m)": 3.0, "Confirm delay (s)": 5.0, "Cooldown (s)": 5.0, "Default mode": "circle", "Designator display name": "F15 Strike" }, "Nuke": { "Planes (count)": 5, "Shots per plane": 10, "Rocket speed (m/s)": 200.0, "Rate of fire (shots/sec)": 1.5, "Stagger between planes (s)": 0.35, "Impact spread radius (m)": 6.0, "Confirm delay (s)": 6.0, "Cooldown (s)": 120.0, "Default mode": "circle", "Designator display name": "F15 Nuke" } }     Need Support?

Advanced RPG Progression System for Rust ItemX is a comprehensive RPG-style progression plugin for Rust that transforms standard items into powerful upgradeable equipment with enchantments, a player-driven marketplace, and extensive customization options. Perfect for servers looking to add deep progression mechanics and player economy.   Core Features - Item Upgrade System = 10 Upgrade Levels with progressive stat bonuses - Customizable Success Rates per level (configurable chance system) - Perfect Upgrade Tokens for guaranteed success - Destruction Risk at higher levels (8→9, 9→10) - Dynamic Skin System with unique skins for level 9 and 10 items - Indestructible Items at level 9+ Stat Bonuses for Weapons (Damage multipliers) and Armor (Protection multipliers) - Visual Rarity System: Common, Uncommon, Rare, Epic, Legendary, Mythic Item Quality - Tracking with condition-based calculations - Enchantment System - 4 Enchantment Slots per item (slot 4 unlockable with token) - Lock/Unlock Mechanism to protect desired enchantments - Reroll System with configurable costs - Available Enchantments: - Gathering Bonuses (Wood, Stone, Scrap, Metal Ore), - Combat Bonuses (Damage, Protection), - Utility (Movement speed, health regeneration) - Rarity Tiers: Common, Uncommon, Rare, Epic, Legendary Percentage-based Bonuses (fully configurable) - Player Marketplace - Buy/Sell System for upgraded items Advanced Search & Filtering by item name, level, rarity, weapon/armor type with pagination support - Listing Management: Set custom prices, view detailed item stats, remove listings, purchase confirmation system - Social Features: Player profiles with statistics, direct messaging system, conversation history, player reputation tracking - Transaction History tracking - Trade-Up System - Item Sacrifice Mechanic to combine multiple items for a higher tier reward - Configurable Requirements: Minimum item count, rarity-based rules, success chance system - Random Enchantments on trade-up results - Visual Reward Display with claim system - Storage/Deposit System - Personal Storage Slots (configurable per player) - Secure Item Storage with full upgrade/enchant data preservation - Slot Management: Deposit/withdraw items, clear individual slots, visual inventory display - Persistent Storage across server restarts - Crafting System - Token Crafting: Perfect Upgrade Tokens, Bonus Upgrade Tokens, Slot Unlock Tokens - Custom Material Requirements (fully configurable) - Skin Support for crafted items Economics/ServerRewards Integration - Configurable Elements - Upgrade costs and progression Success/failure rates Stat multipliers per level Enchantment types and values - Marketplace fees Storage capacity Crafting recipes Payment methods (Scrap/Economics/ServerRewards) - UI colors and styling - Commands - /upgrade - Open upgrade menu - /enchant - Open enchantment menu - /marketplace - Open marketplace - /tradeup - Open trade-up menu - /deposit - Open storage menu   - API Methods IsItemUpgradeable(ulong itemUID) - Check if item can be upgraded GetItemUpgradeLevel(ulong itemUID) - Get current upgrade level GetItemUpgradeData(ulong itemUID) - Get complete upgrade statistics GetItemEnchantData(ulong itemUID) - Get enchantment information SetItemUpgradeLevel(ulong itemUID, int level) - Programmatically set level Discord for contact and support : mariantrex    

Basements lets players build underground rooms beneath their bases. Place a hatch on your foundation and dig straight down into a hidden basement with walls, ceilings, and full building privileges. Great for stashing loot, setting up secret bunkers, or just adding extra space. Readme Link - Click Here for Instruction and Documentation 👆Highly recommend reading the FAQ section! BUILD Build basements easily from your tool cupboard. Just place an entrance to get started.  EXPAND Expand your basement by drilling underground. But don't forget to bring a headlamp - its dark down there! TRAVERSE Place multiple entryways, building out your labyrinth of tunnels beneath your base.  DECORATE All deployables, electricity, and storage items can be placed in your basement. Take advantage of your new space! RAID Nothing is safe in Rust, including your basement. If all the entrances are destroyed, then the basement is too. Any loot below will float to the surface. Protect the entrance at all costs! API METHODS (For Plugin Developers) // Returns true if the given entityId is part of a basement. bool IsBasementEntity(ulong entityId) // Returns the building ids of the basements connected to a given surface building id. uint[] GetBasementBuildingIds(uint surfaceBuildingId) // Returns the building ids of the surface buildings connected to a given basement building id. uint[] GetSurfaceBuildingIds(uint basementBuildingId) Extension Plugins These are free plugins that add additional functionality to Basements. BasementsManager Provides a UI for admins to view and manage the basements on the server. Useful for debugging & fixing issues. Use with the /bm command, requires the basements.admin permission to use. BasementsManager.cs

🌃 Metropolis: Where Concrete Meets Carnage  Dive into Metropolis, a densely packed, abandoned city map where danger lurks on every street corner and the highest loot awaits the bold. This 4700-sized environment transforms the survival sandbox into an intense urban battleground, perfect for players craving high-stakes PVP and intricate exploration. The heart of the map is the vast Metropolis itself—an urban labyrinth heavily patrolled by two formidable Bradleys and overseen by airborne Scientists. Navigate the city's depths to find multiple puzzle rooms (2 Red, 1 Blue, 2 Green) and unlock the abundant loot scattered throughout its concrete canyons.   Custom Safe Zone: New Haven Outpost This once-abandoned locale has been meticulously re-energized by a team of Cobalt scientists, providing the starting population with an abundance of supplies and services. This monument retains all the essential features of the original Outpost—and delivers much more: Striking Architecture: The central compound is now secured by large, custom glass walls, creating a visually stunning and unique aesthetic. Custom Water Features: A tranquil, custom-built lake and an elegant fountain enhance the environment. Functional water catchers are installed, providing players with a reliable source of hydration. Expanded Services: A custom Air Wolf vendor has been integrated for convenient helicopter purchases. High-Stakes Casino: An all-new, dedicated casino allows players to safely gamble their riches, adding a fun and high-risk activity to the safe zone. Ample Safe Loot: Players can safely gather a generous amount of loot scattered throughout the outpost.   Thrills and Exploration Experience the map's unique flair with a custom-built, fully working rollercoaster that is plug-in controlled to spawn a vehicle for your player with the press of a button! Explore intricate infrastructure including underground train tunnels, underground roads, and custom bridges, as well as two Heli Towers offering verticality to the fight.    💧 Water Treatment & Sewer Branch Reimagined Welcome to the New Sewer Treatment Plant, a monument that takes the best features of both Water Treatment Plant and Sewer Branch to create one incredible, high-value loot location. This massive, abandoned facility is loaded with features and rewards. Cobalt's Control: Don't be fooled by the ruin; Cobalt Scientists still maintain control over the facility's sewer drains. Underground Puzzles: Navigate two new, exclusive puzzles deep within the piping, featuring a dedicated Blue and Green keycard room. Lurking Danger: Keep your guard up—a scientist or two may still be lurking in the shadows, guarding their subterranean assets.     Map Prefabs Count: 25249 | Map Size: 4700 Monument List Custom Monuments and Prefabs Metropolis New Haven Outpost Murder Farm The Roller Coaster Sewage Treatment Plant 19 custom build locations Underground Train Tunnels Underground Roads Custom Bridges 2x Heli Towers Mod Room For Staff Facepunch Monuments Bandit Camp Launch Site Artic Research Stone, Hqm, & Sulfer Quarry Rad Town Power Plant Airfield Trainyard Jungle Ziggurat 2x Mining Outpost Large Harbor Small Harbor 3x Oxums gas Station 2x lighthouse Supermarket Large Barn Ranch Military Tunnel Ferry Terminal Giant Excavator Abandoned Cabins Large Fishing Village 2x Small Fishing Village Large Oil Rig Small Oil Rig 2x WaterWell For any Assistance or questions Please contact me on Discord @ https://discord.gg/HNhPTPZVmd   Acknowledgements Shoutout to Substrata for helping with making the plugin for the rollercoaster. Shoutout to MrLiquid and the Luffy Map Testing team for their help polishing this map. Shoutout to Milky for help with making the video.

Manage your Rust server easier and more efficiently with the AdminMenu plugin. Track players, interact with them, edit their data and permissions, as well as change server convars and manage plugins. Features: Menu retains its state after closing, you won't lose everything you did before. Ability to fully translate the menu into any language.   Large range of permissions for each action, will allow you to flexibly customize the admin menu for each group of administrators. Quick menu that allows you to perform quick actions Full list of players with the ability to filter by online, offline, admins and moderators. Also has a frame of different colors depending on the level of authorization. Wide range of information and actions for the selected player. Editing convars with search. Has a complete list of editable convars with descriptions for some of them. Extensive issue menu by category, with easy management of name, skin and amount (manual, +1, +100, +1000, +10000). Plugin management menu. It is possible to reload, unload or load a plugin easily and quickly. Updates occur in real time. Ability to create your own custom buttons that execute several commands Quick Start: You install the plugin in the plugins folder. Give yourself the adminmenu.fullaccess permission.   Commands, use one of your choice, one for the player and one for the admin group:   o.grant user [name or steamid] adminmenu.fullaccess   o.grant group admin adminmenu.fullaccess Press the X button (swap  seat button) or type adminmenu in the console. Enjoy   Useful stuff: You can quickly open a player in the admin menu. To do this, point at the player and press X. You don't have to hover over the player exactly, you will be able to open players within a certain radius of the place you are looking at.   CUSTOM BUTTONS Custom buttons are buttons that when pressed will execute commands on behalf of the administrator, commands can be several, below will be the details. At the moment, custom buttons can be created in two places: in the quick menu and in the menu when selecting a player. These places are separated in the config. Button Fields: "Execution as server" - Call the command on behalf of the server, not the administrator "Label"  - Text that will be on the button, for each such inscription creates a field in the lang file, accordingly you can translate this text into several languages. "Commands" - Array of commands that will be executed on behalf of the administrator. Chat commands require a special entry, see examples. "Permission"- permission to display and use the button. You need to write the permission that will be after  "adminmenu.". Example: if you enter the permission "test"  the permission will be adminmenu.test "Position"  - The location for the button, the first number is responsible for the row number, the second for the position within the row, starts from 0.There are limits of locations, if you have gone beyond the limit - the button will not be displayed. Common Tags: {adminUID} - administrator's id. {position} - administrator coordinates (underfoot) {view_position} - the position where the administrator is looking (can be used for spawning or something similar) {view_direction_forward} - forward view direction of the administrator {view_direction_backward} - the direction the administrator is looking backwards {view_direction_left} - direction of the administrator’s view to the left {view_direction_right} - administrator’s view direction to the right Tags for target only: {steamid}, {steamID}, {userID}, {STEAMID}, {USERID} - mean the same thing, namely the id of the selected player. {target_position} - target coordinates (underfoot)   Example of commands: chat.say \"/{chat command}\" vanish ban {steamID} teleport {steamID} {adminUID}     More information about the grant menu: The grant menu includes the full list of items including hidden items as well as custom items created by the CustomItemDefinitions library. The menu can be accessed from the navigation or from the menu of the selected player. When issuing itself has categories. Search works in any registry by any part of the name or short name.   Has a page system at any stage. More information about the buttons in the Quick Menu: [Teleport to 0 0 0] - Teleport to coordinates 0 0 0. Requires  adminmenu.quickmenu.teleportto000 permission [Teleport to Deathpoint] - Teleport to your deathpoint. Requires adminmenu.quickmenu.teleporttodeath  permission [Teleport to Spawn point] - Teleport to a random spawn point. Requires adminmenu.quickmenu.teleporttospawnpoint  permission [Kill Self] - Kill Self, kills even when immortal. Does not require permission. [Heal Self] - Fully heal yourself. Requires  adminmenu.quickmenu.healself  permission   [Call Heli] - Call Helicopter to yourself (arrives in time). Requires adminmenu.quickmenu.helicall  permission [Spawn Bradley] - Spawn bradley on yourself. Requires adminmenu.quickmenu.spawnbradley  permission More information about the buttons in the menu of the selected player: [Teleport Self To] - Teleport yourself to the selected player. Requires adminmenu.userinfo.teleportselfto permission [Teleport To Self] - Teleport the selected player to yourself. Requires adminmenu.userinfo.teleporttoself  permission [Teleport To Auth] - Teleportation to random authorization (TC). Requires adminmenu.userinfo.teleporttoauth permission [Teleport to Deathpoint] - Teleportation to a player's deathpoint. Requires adminmenu.userinfo.teleporttodeath  permission [Heal] - Full healing, including metabolism. Requires adminmenu.userinfo.fullheal  permission [Heal 50%] - Half healing. Requires adminmenu.userinfo.halfheal permission. [View Inventory] - View and edit player's inventory. Requires adminmenu.userinfo.viewinv  permission [Strip Inventory] - Clear player's inventory. Requires adminmenu.userinfo.stripinventory permission [Unlock Blueprints] - Unlock all Blueprints. Requires adminmenu.userinfo.unlockblueprints  permission [Revoke Blueprints] - Reset all Blueprints. Requires adminmenu.userinfo.revokeblueprints permission.   [Kill] - Kill a player. Requires adminmenu.userinfo.kill  permission [Kick] - Kick a player. Requires adminmenu.userinfo.kick permission [Ban] - Ban a player. Requires adminmenu.userinfo.ban  permission More information about the buttons in the menu of the selected group: [Remove Group] - Remove group, has confirmation. Requires adminmenu.groupinfo.removegroup  permission [Clone Group] - Clone group with the ability to copy users. Requires adminmenu.groupinfo.clonegroup permission Permissions: adminmenu.use - Ability to use admin menu with basic set. Open tab quick menu (each button has its own permission, without permissions is present only kill yourself button) and the list of players. adminmenu.fullaccess - Full access to all functions without the need for each permission, includes also adminmenu.use. It is recommended to give only to the main administrators. adminmenu.quickmenu.teleportto000 - Access to the button in the quick menu, teleportation to coordinates 0 0 0 0. adminmenu.quickmenu.teleporttodeath - Access to the button in the quick menu, teleportation to the point of your death. adminmenu.quickmenu.teleporttospawnpoint - Access to the button in the quick menu, teleportation to a random spawn point. adminmenu.quickmenu.healself - Access button in quickmenu, heal yourself completely. adminmenu.quickmenu.helicall - Access to the button in the quick menu, call a helicopter to yourself (arrives in time). adminmenu.quickmenu.spawnbradley - Access button in quickmenu, spawn bradley. adminmenu.userinfo.teleportselfto - Access to the button in the menu of the selected player, teleportation to the selected player. adminmenu.userinfo.teleporttoself - Access to the button in the menu of the selected player, teleport the selected player to himself. adminmenu.userinfo.teleporttoauth - Access to the button in the menu of the selected player, teleportation to random authorization (TC). adminmenu.userinfo.teleporttodeath - Access to the button in the menu of the selected player, teleportation to the place of death of the player. adminmenu.userinfo.fullheal - Access to the button in the menu of the selected player, full healing, including metabolism. adminmenu.userinfo.halfheal - Access to the button in the menu of the selected player, half healing. adminmenu.userinfo.viewinv - Access to the button in the selected player's menu, view and edit the player's inventory. adminmenu.userinfo.stripinventory - Access to the button in the menu of the selected player, clear the player's inventory. adminmenu.userinfo.unlockblueprints - Access the button in the menu of the selected player, unlock all drafts. adminmenu.userinfo.revokeblueprints - Access to the button in the menu of the selected player, reset all drafts. adminmenu.userinfo.kill - Access the button in the selected player's menu to kill the player. adminmenu.userinfo.kick - Access the button in the selected player's menu to kick the player. adminmenu.userinfo.ban - Access to the button in the menu of the selected player, ban the player. adminmenu.groupinfo.removegroup - Access to the button in the menu of the selected group, the ability to remove the group. adminmenu.groupinfo.clonegroup - Access to the button in the menu of the selected group, the ability to clone the group. adminmenu.convars - View and edit convars. adminmenu.permissionmanager - View and edit permissions in groups, player groups, create, delete and clone groups (requires additional permissions from these buttons). adminmenu.pluginmanager - Access to plugin management, reloading, unloading, loading plugins. adminmenu.give - Access to give resources, as well as yourself and the selected player.

DemoPro: The Anti Cheat That Works 🎥 DemoPro turns F7 reports into a single evidence bundle with timeline markers + jump points, so you can jump straight to the key moments fast. It captures footage  Before / during / after the f7 report is made Cheaters can’t hide from this system — no more relying on outdated anti-cheat plugins. This is clear video evidence that makes decisions easier, faster, and fairer. 100% accurate, No False Positives  Key Features 🎥      ✅ Converts **F7 reports** into a  single evidence bundle      ✅ Records BEFORE, DURING, and AFTER every F7 report. You NEVER miss what happens.      ✅ Saves you and your admins loads of time. No more wasting hours spectating players      ✅ Smart sorts demos with Timeline markers + jump points  to reach key moments fast      ✅ Private portal access for you and your admins with **Steam sign-in**      ✅ Assignments, notes, outcomes  (keeps reviews organised)      ✅ Server-friendly: all data is stored off-site on your account, not on your game server, keeping things lightweight and smooth.      ✅ Can be use as a content tool,  you can make cinematic videos from the demos you receive.      ✅ Fully compatible with all Rust server setups.   Proof it works: 🔍 join our Discord and check out the #cheater-clips channel  https://discord.gg/2DCfVFFgvW   7-day free trial: https://rustdemopro.com   RustAdmin Integration: https://www.rustadmin.com Visual snippet of recoil mapping with each attack in timeline Shareable filtered portal links Discord ban feed + global portal search Redesign the portal + dashboard for a more modern and fluid feel  New portal is now live Future Updates AI Integration 🧠 Introduce an AI/ML system that analyses demo files to learn the difference between normal players behaviour vs a cheaters behaviour All Seeing Eye  👁️ An AI powered monitoring layer that automatically flags suspicious players and triggers evidence capture without relying on F7 reports.   Set Up Guide   Step 1 — Create Your DemoPro Space Sign in at https://rustdemopro.com using your Steam account Create your community space Choose monthly or annual billing (includes a 7-day free trial)   Step 2 — Install the Harmony Mod Copy the DLL into: server_root/HarmonyMods/ Start the server once to generate: server_root/HarmonyConfig/ (this contains the config) After editing the config, run: rdm.reloadcfg to apply changes   Step 3 — Connect Your Server In the portal, generate a Server Key Paste the key into the plugin config Make sure uploads are enabled in the config Reload the config, enter this command in your console rdm.reloadcfg    Step 4 — Reports Create Cases When an in-game report (F7) happens, DemoPro automatically builds an evidence bundle The bundle is uploaded to your portal as a case for review   Step 5 — Review & Decide Open the case, assign it, and add notes Download the bundle, jump to the timeline markers Mark the outcome as Reviewed (Clear) or Reviewed (Cheating) with notes for your team If you need any help setting up DemoPro, please open a ticket on our Discord.         How it works  🎥 Server records players in 15-minute chunks with ~30 minutes rolling history. When someone is F7 reported, Demo Pro grabs the “before” buffer and keeps recording. 15 minutes later it adds the “after” clip and uploads everything to the portal. If a player disconnects/reconnects, chunk lengths can be shorter than 15 minutes—that’s normal. Portal statuses 🎥 Players reported → Clip uploaded → Needs Review → Admin downloads → Admin reviews → Mark result Needs Review — new or reset incidents. Downloaded (Needs Review) — someone pulled the bundle but hasn’t finished. Reviewed — Clear / Reviewed — Cheating — finished decisions. Opening & assigning a report 🎥 Click Open on a card to see details. Assign it to yourself immediately and add notes as you investigate. Set the review state to Reviewed (Clear) or Reviewed (Cheating) when done. Assignments and outcomes keep other moderators from duplicating work. Finding the action fast 🎥 Timeline dots: hits/shots, kills, report moment. Use the event feed to jump to notable damage or kill events. Report marker shows where the F7 report landed inside the clip. Downloading the bundle Use Download bundle for a ZIP containing .dem files and a README. The README points to the first demo and the timestamp to jump to—start there. Clip lengths can vary if players disconnect; that’s expected. Load demos into Rust 🎥 Copy the suggested .dem into C:\Program Files (x86)\Steam\steamapps\common\Rust\demos. If the demos folder doesn’t exist, create it (restart Rust once if needed). Playing + controls From Rust main menu, open the Demo browser, refresh, pick the file, and play. Use Alt to toggle cursor, Tab for UI, and debugcamera to free-fly. Cycle nearby players with Spacebar; pause/rewind/fast-forward as needed. Review guidance 🎥 Use the README timestamps as a starting point; check other demos if nothing obvious. If cheating is confirmed: capture proof, upload to the usual place, mark Reviewed (Cheating), and leave clear notes. If clean: mark Reviewed (Clear) and add a quick note (e.g., desync, valid prefire). long story short, when someone f7 reports, you can get a clip, you replay in rust of exactly why, and it shows footage before and during the report. For tips and useful keybinds to help you get the most out of DemoPro, check out the dedicated channels in our Discord.    Discord: https://discord.gg/2DCfVFFgvW Website: https://rustdemopro.com/ Youtube: https://www.youtube.com/@RustDemoPro Cheater Videos            

CodeFling Creator Bot is a Discord bot, written in Python using Discord.py. The bot monitors users specified in the config and using the CodeFling API, sends notifications to Discord for various actions: New Releases (Plugins, Maps, Tools etc) Plugin/Release Updates New Comments/Discussion Posts New Support requests and replies to threads New Reviews New Private Messages The bot is lightweight and written with efficiency and reliability in mind. It makes only the API calls it needs and stores data in an SQLite database for use later. When guild members use the bot commands, the data is pulled from the local database and doesn’t make extra calls to the API, which means you don’t need to worry about rate limiting or getting banned by the API. The bot polls the API looking for new content at set periods as set in the config, notifying about new content and then updating the database with new data. PLEASE NOTE: Requires Python 3.6 or higher.   README: CodeFling Creator Bot 1.1.1 Discord Bot by ZEODE ========================================== Minimum requirements: Python 3.6 or higher Dependacies: Discord.py aiohttp Using pip: pip install -U discord.py pip install -U aiohttp The -U flag just means “upgrade to the latest version if already installed.” Using apt: apt install python3-discord apt install python3-aiohttp This file explains each configuration option in config.json *************** DEFAULT CONFIG FILE IS CREATED ON FIRST RUN *************** DISCORD SETTINGS ---------------- Make sure your Discord bot has at least "Send Messages", "Read Message History" and "Embed Links" permissions. bot: bot_token: Your Discord bot token from the Discord Developer Portal. Get it from: https://discord.com/developers/applications channels: release_channel_id: Discord channel ID where file release/update notifications will be posted. To get channel ID: Enable Developer Mode in Discord settings, right-click channel, "Copy ID" purchase_channel_id: Discord channel ID for purchase notifications (recommend private channel). Shows when someone buys one of your paid plugins. support_channel_id: Discord channel ID for support request notifications. comments_channel_id: Discord channel ID for comment/discussion notifications. Shows when users comment on your files (excludes file author replies). downloads_channel_id: Discord channel ID for file downloads notifications (recommend private channel). Shows when users download your files. reviews_channel_id: Discord channel ID for file review notifications. Shows when users review a monitored file. messages_channel_id: Discord channel ID for user message notifications (recommend private channel). Notifys when a monitored user receives a message on CodeFling. commands_channel_id: Discord channel ID for people to use bot commands. People can use bot ! commands here, all user messages can be cleaned automatically, see below. admin_commands_channel_id: Channel for users with the bot admin role to use admin commands away from public channels All normal commands also work here for bot admin role users to use here too NOTE: - Leaving any of the channel IDs blank will disable notifications for those actions - Although there are separate channels for each type in the config, this is just for anyone wanting this, if you want you can put the same channel ID in more than one channel config misc: clean_commands_channel: If true, users messages are automatically deleted shortly after they are sent to the channel. max_number_files_to_list: Number of files to return when users use the "!list plugins" command bot_admin_role_id: Users need this role to use the admin only commands ping_release_channel: If this is true, new releases or updates to files will be notified with the @everyone tag presence: enabled: true or false to enable or disable Discord presence. type: Available options: "playing" "watching" "listening" "competing" text: The text to display, e.g. www.codefling.com CODEFLING SETTINGS ------------------ monitored_users: Dictionary of Codefling user IDs and their API tokens. Format: "user_id": "api_token" How to get your User ID: - Visit your Codefling profile - Hover over or click on "See my activity" - Your user ID is in the URL: https://codefling.com/profile/USER_ID-username/content/ - Copy just the numbers, without the "-username" part How to get API Token: - Visit: https://codefling.com/settings/apps/ - Click "Add App" > "Creator API" - Select "All" under scopes - Copy the access token to paste in your config NOTE: For message_buyer_on_purchase you will require a Creator Pro API token. Example: "monitored_users": { "user_id_1": "your_api_token_here", "user_id_2": "another_api_token" } Note: Each user needs to use their own API token. poll_interval_seconds: How often (in seconds) the bot checks Codefling for new content. Default: 120 (2 minutes) Suggested values: | Type | Safe poll interval | Notes | | ----------------------- | ------------------ | ----------------------------------- | | Light use (1–2 authors) | 60 s | Feels instant, safe if few requests | | Medium (3–5 authors) | 120 s | Recommended default | | Heavy use (5+ authors) | 300 s | Low strain, good scaling | | Massive / strict API | 600–900 s | Extremely safe | Note: Too frequent polling may hit API rate limits. The more files a user has, the harder it is on the API leading to possible rate limits or IP ban, so be cautious. retention_days: How many days of historical data to track and store. Default: 7 days The bot will: - Only notify about content within this time window - Automatically clean up older data daily - On first run, load existing content from this period Recommended values: - 7 days (minimal storage) - 30 days (balanced) - 90 days (extended history) NOTE: Monitored resource/file data is kept indefinitely for users !stats !list commands etc, but the bot will only look for new actions within this period to send notifications to Discord or not. This maintains speed and performance so the bot isn't retreiving more data than is necessary with each API call. In most cases, 7 days should be more than sufficient for all use cases. message_buyer_on_purchase: If true, when a new purchase is detected, the bot will send a private message on the Codefling website with the message content taken from users/{userid}/purchase_message.txt. This can be edited to whatever you like, using html formatting and with available placeholders: {buyer_name} {resource_name} {resource_url} {support_url} NOTE: You will require a Creator Pro API token to use this feature!!! notify_support_request_replies: Limitation of the API at present means that it is not possible to know the reply comment author in support requests. Therefore we cannot filter replies by the file owner, so all replies will be announced, inclduing from the file owner. If you do not want this, you can disable announcing replies so that only new support requests are announced. If the API endpoint is updated in future this can be improved. LOGGING SETTINGS ---------------- timestamp_date_format: The format for timestamps in the console/log output. Availble: - %d - %m - %y e.g: %d-%m-%y would make something like 30-10-25 timestamp_time_format: Specify the format for the timestamp. - 12h - 24h log_file_path: Set the path to the OPTIONAL log file. If left blank, no log file will be used. API OPTIONS ----------- Note: You can usually leave this as is and it will work absolutely fine. max_attempts: How many times to try an API request if it fails before giving up on that attempt Useful for occasional CloudFare errors/timeouts timeout_seconds: How long to wait before retrying a API request due to timeout DEBUG OPTIONS ------------------ enable_verbose_debug_logging: As it says, enabled verbose loigging which can help in troubleshooting issues. Default is false. config_version: DO NOT EDIT THIS COMMANDS ------------------ NOTE: Commands by users do not query the CodeFling API every time. They only retreive data from the SQLite database, so you don't have to worry about rate limiting or banning from users abusing the commands on Discord. This also means it is much quicker with results. The database is updated with all the info every time the API is queried as per the poll rate in the config only. Non-Admin Commands: !help Lists all available commands !stats [username] Get own stats without parameter if you are monitored by the bot or get stats for the user specified !list files List all files monitored by the plugin (config option to limit results) !list authors List all file authors/devs monitored by the bot !file <FileName> / !file <file_id> Give information about that file Admin Commands: !user add <user_id> <api_token> Add the specified user ID and API token to the bot, save in the config and begin monitoring !user remove <user_id> Stops monitoring and removes the specified user ID from the bot and config !rotate Immediately rotate the log file and begin a new blank log file (rotated files saved in logs/) !cleardb Immediately clear the SQLite database and re-seed a new database (ALL DATA WILL BE CLEARED) !test <review|download|purchase|comment|support|message> Send a test notification to Discord for the most recent entry of the given type !test <purchase_msg> <user_id> <purchaser_id> Send a test purchase message by PM on CodeFling !test <file> [new|updated] Send a test notification to Discord for the most recent entry for files/releases, using the new or updated parameter accordingly/ FIRST RUN BEHAVIOR ------------------ On first run, the bot will: 1. Create a SQLite database (codefling_bot.db) 2. Load/Cache all users existing files. 3. Load/Cache all existing content from the last N days (retention_days) 4. DOES NOT send any notifications for existing content 5. Only notify about NEW content after initialization On subsequent runs: 1. Check for content created while bot was offline 2. Send notifications for missed content 3. Continue normal monitoring TROUBLESHOOTING --------------- No notifications appearing: - Verify channel IDs are correct - Check bot has "Send Messages", "Read Message History" and "Embed Links" permissions - Confirm API tokens are valid and have correct scopes Getting rate limited: - Increase poll_interval_seconds value - Default 300 seconds (5 minutes) should be safe Bot sends old notifications on startup: - This is normal if content was created while bot was offline - Bot catches up on missed content within retention period - On first run, no old notifications should appear SUPPORT ------- For issues with the bot, check console output for error messages. Get more support in my Discord: https://discord.gg/jnyg3FvDnc For Codefling API issues, see: https://codefling.com/developers    

Well rounded shop, with various features. It's standalone plugin which is compatible with WelcomePanel, HumanNpc. This plugin also supports selling commands, wipe block, no escape, sales, permission access.   Multi-currency support Use different currencies for different items. Economics and ServerRewards (RP) is supported as well as scrap or any other ingame item.     Restrictions Combat, raid, spawn and building block supported alongside with  basic cooldowns and wipe block.   NoEscape is required for combat and raid block.       Appearance   Simple and clean design to ensure smooth user experience for your players.   Additionally Shop can be inserted into WelcomePanel to achieve "all in" server panel.   Customization Widely customizable and feature rich Shop which will  fit all needs of your community.         Field Tested Plugin made by experienced developer,  tested by hundreds of server owners and used by some big organizations.       Discord   Customer support available on discord,   Installation - unzip downloaded package and place Shop.cs file into your plugin folder. - after succesfuly loading the plugin, data folder oxide/data/Shop will be generated - take data files provided in plugin package and drop them into your Shop data folder After finishing these steps your shop is ready to used.         Server Currency   If you don't wish to use ingame items as currency make sure you use either Economics or ServerRewards as you currency management as only those two plugins are compatible with Shop. Default currency setting is Economics ("eco"), if you wish to change it navigate to "oxide/data/Shop/Items.json", open this file in some text editor (VSC recommended) and simply select "eco" and mass replace for desired value. (video here) "eco" for Economics "rp" for ServerRewards "scrap" or any other ingame item   Shop Categories To remove, change or add new categories open "oxide/data/Shop/Categories.json" file. There you will find all categories alongside with items lists. If you wish to remove certain items from category, just head over to item list and delete from there.   Items Changing prices In "oxide/data/Shop/Items.json" you will find every item with their properties, to quick search for specific items press "CTRL + F".  By leaving BuyPrice or SellPrice at 0 you will disable selling or buying of said item. Due to multi-currency support prices can be set only in whole numbers, no decimals. To offset for this, you can set minimal amount requirement. For example instead of selling one piece of wood for 0.01$ you can set minimal amount of  100x wood for 1$.   Removing items If you wish to remove some items from Shop, you can do that directly in  "data/Shop/Categories.json" file. Removing items from "Items.json" is not needed as they have no effect unless they are listed in some category. Adding new items To add new item you must first head over to "Items.json" data file and create new entry by copy pasting some of the existing ones. Once done with that you can add the  item into category. To add multiple versions of same item can be created by simply adding unique tag behind shortname, for example "rifle.ak{1}",  "rifle.ak{2}", etc...   Commands Adding new commands Commands can be create at "data/Shop/Commands.json". Plugin can only run server side console commands and then parse steam id or player name with tags {steamid} and {playername}. There are two examples shown in default data file. Server side console commands are common thing and almost all plugins utilize them. Listing commands in categories Simply type in one of your command names into category item list like this "cmd/yourCommandName". Slash cmd in front of command name is there to make difference between ingame item and command.   Cooldowns These are very basic, cooldown is triggered when buy/sell action is triggered. By using minimal amount requirement for items you can manage how much player buy and how often. Cooldowns are managed in "data/Shop/Cooldowns.json". Default data file contains two example of cooldowns but it's simply shortname and amount of seconds.     Restrictions Raid and Combat Block Managed by NoEscape plugin, option to enable these two block can be found in config file. Building Block Prevents players from using shop while they are building block, option can be found in config file. Spawn Block Prevents players from using shop after they respawn, amount of seconds can be set in config file, 0 = disabled. Wipe Block Prevents players from buying specific items after wipe. Settings are located in "data/Shop/ItemsWipeBlock.json", similar as cooldowns.   Sales By Permission (config file) Discount on every item in the shop assigned by permission, multiple permission can be created with their own discount values. By Category (categories data file) Discount for every item within specified category. By Item Discount for specific item in the shop. If item is already in discounted category, higher discount will be applied.   WelcomePanel integration To integrate this plugin into WelcomePanel simply use one of the four configs included in download package. These config were premade for each WelcomePanel template (goes from 1 to 4). In case you have own  highly customized layout for WelcomePanel you will have to adjust "Layout Container" in Shop config file by yourself.                  

This custom package, designed by us, features 210 handcrafted bases across five 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 base pack we previously offered. If you've already purchased the FullWiped-110 bases, you only need to buy the expanded package, 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 package includes: (In addition to the bases, it includes a well-configured config file that can be uploaded to 📁/serverfiles/oxide/config, but its usage is optional. It also contains 5 different profile configs that can be uploaded to 📁/oxide/data/RaidableBases/Profiles. These are also well-configured and optional to use. The usage of both is entirely up to you.) 🏡70 Easy Bases 🏡60 Medium Bases 🏡60 Hard Bases 🏡10 Expert Bases 🏡10 Nightmare Bases   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—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 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 4: 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. Note:  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: 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,   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 need not only these bases but also the loot tables for the items that will spawn inside them, check out our one-of-a-kind, exceptional Raidable Base Loot Tables at the link below: https://codefling.com/customizations/raidable-bases-loot-tables-pack (Our loot tables are designed to cater to different server types, including Vanilla (1x) servers as well as 2x, 3x, 5x, 10x, and higher multipliers to match various loot requirements.)   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!   Support:  FULLWIPED DISCORD