Search the Community

Team Spawner makes regrouping with your team fast, simple, and player-friendly. Its clean, auto-generated UI lets players quickly select teammates directly from the death screen—no manual commands or reliance on beds and sleeping bags required. Perfect for fast-paced, action-packed team PvP. Features powerful restriction controls: Monument Blocking – Prevent team spawning near key monuments. Player State Blocking – Restrict spawning when swimming, sleeping, mounted, inside elevators, or on the cargo ship. Condition Blocking – Prevent usage while raid-blocked, combat-blocked, building-blocked, or on cooldown. Whether you’re running a casual or competitive server, Team Spawner gives server owners full flexibility while providing players with a seamless team experience. You can also create various permission based cool-down restrictions inside the config and simply grant players there permission based cool-down restriction. Notes: Requires Monument Finder from umod for monument blocking to work. ( Simply add the plugin ) Permissions teamspawner.use - needed to use the plugin. config cool down permissions will look like this: teamspawner.cooldown.vip Config { "GUI Settings": { "Main Panel Default: #000000, 0f": { "A": 0.0, "Hex": "#000000" }, "Content Panel Default: #000000, 0f": { "A": 0.0, "Hex": "#000000" }, "Buttons Default: #000000, 0.4f": { "A": 0.4, "Hex": "#000000" }, "Text Default: #FFFFFF, 0.7f": { "A": 0.7, "Hex": "#FFFFFF" } }, "Block Types": { "swimming": true, "sleeping": true, "mounted": true, "monument": true, "cargo ship": true, "elevator": true, "raid blocked": true, "combat blocked": true, "building blocked": true, "cooldown blocked": true }, "Permission Based CoolDown times in seconds": { "vip": 150, "default": 300 }, "Blocked Monuments": { "airfield_1": false, "arctic_research_base_a": false, "bandit_town": false, "cave_large_hard": false, "cave_large_medium": false, "cave_large_sewers_hard": false, "cave_medium_easy": false, "cave_medium_hard": false, "cave_medium_medium": false, "cave_small_easy": false, "cave_small_hard": false, "cave_small_medium": false, "compound": false, "desert_military_base_a": false, "desert_military_base_b": false, "desert_military_base_c": false, "desert_military_base_d": false, "excavator_1": false, "ferry_terminal_1": false, "fishing_village_a": false, "fishing_village_b": false, "fishing_village_c": false, "gas_station_1": false, "harbor_1": false, "harbor_2": false, "ice_lake_1": false, "ice_lake_2": false, "ice_lake_3": false, "ice_lake_4": false, "junkyard_1": false, "launch_site_1": false, "lighthouse": false, "military_tunnel_1": false, "mining_quarry_a": false, "mining_quarry_b": false, "mining_quarry_c": false, "nuclear_missile_silo": false, "oilrig_1": false, "oilrig_2": false, "powerplant_1": false, "radtown_small_3": false, "satellite_dish": false, "sphere_tank": false, "stables_a": false, "stables_b": false, "supermarket_1": false, "swamp_a": false, "swamp_b": false, "swamp_c": false, "trainyard_1": false, "underwater_lab_a": false, "underwater_lab_b": false, "underwater_lab_c": false, "underwater_lab_d": false, "warehouse": false, "water_treatment_plant_1": false, "water_well_a": false, "water_well_b": false, "water_well_c": false, "water_well_d": false, "water_well_e": false } } Supports the ability to add more Languages using oxides multi language file system: { "Unavailable": "team member is dead or wounded.", "Sleeping": "team member is sleeping.", "Swimming": "team member is swimming.", "Mounted": "team member is mounted.", "Cargo": "team member is aboard cargo.", "Elevator": "team member is using an elevator.", "BuildingBlocked": "team member is building blocked.", "RaidBlocked": "team member is raid blocked.", "CombatBlocked": "team member is combat blocked.", "MonumentBlocked": "team member is monument blocked.", "CoolDownBlocked": "cooldown blocked: {0}" }

Command Limiter Info Command Limiter allows you to limit the use of commands that players can use. For each command you can set the cooldown, minute, hourly, daily and wipe usage limits. It also allows you to apply limits in case of Building Blocks, Safe Zones, block the command permanently, etc... Command Limiter is useful for limiting the use of commands from plugins that do not implement a blocking system or implement an inflexible blocking system. Commands Commands can be typed in chat (by putting the / character in front of the command), or from console. /cl reset <steamID> -- This command allows you to reset usage limits for a specific player. To use this command you must have permission: commandlimiter.admin /cl wipe -- This command allows reset all usage limits for all players. To use this command you must have permission: commandlimiter.admin Commands can be added or modified in the configuration file: /oxide/config/CommandLimiter.json Permissions commandlimiter.admin -- Allows the use of commands reserved for administrators commandlimiter.bypass -- Allows you to bypass the command usage limit, but only for commands that have the CanBeBypassed field set to TRUE commandlimiter.bypass.force -- Allows you to easily bypass the command usage limit, regardless of the CanBeBypassed field Default Configuration { "TimeZone": "Europe/London", "Clear data on map wipe": true, "Print usage limits when command is blocked": true, "Chat Command": [ "cl", "commandlimiter" ], "Command Setting": [ { "Enabled": true, "Command": "cmd", "Commands alias": [], "BlockCommand (If set to TRUE players will no longer be able to use this command. Default FALSE)": false, "SafeZone. Value [AllowOnly | Allow | Block] (Default Allow)": "Allow", "BuildingBlocked. Value [AllowOnly | Allow | Block] (Default Allow)": "Allow", "CanBeBypassed (If set to TRUE the command block can be bypassed. It depends on the user permissions)": false, "CooldownSeconds (-1 infinite)": 30, "MaxUsagePerMinute (-1 infinite)": -1, "MaxUsagePerHour (-1 infinite)": -1, "MaxUsagePerDay (-1 infinite)": -1, "MaxUsagePerWipe (-1 infinite)": -1, "BypassPermission (Permissions to bypass the block even if [CanBeBypassed] is set to false)": [] }, { "Enabled": true, "Command": "cmd_2", "Commands alias": [ "alias 1", "alias 2" ], "BlockCommand (If set to TRUE players will no longer be able to use this command. Default FALSE)": false, "SafeZone. Value [AllowOnly | Allow | Block] (Default Allow)": "Allow", "BuildingBlocked. Value [AllowOnly | Allow | Block] (Default Allow)": "Allow", "CanBeBypassed (If set to TRUE the command block can be bypassed. It depends on the user permissions)": false, "CooldownSeconds (-1 infinite)": 30, "MaxUsagePerMinute (-1 infinite)": -1, "MaxUsagePerHour (-1 infinite)": -1, "MaxUsagePerDay (-1 infinite)": -1, "MaxUsagePerWipe (-1 infinite)": -1, "BypassPermission (Permissions to bypass the block even if [CanBeBypassed] is set to false)": [] } ], "VersionNumber": { "Major": 1, "Minor": 0, "Patch": 7 } } TimeZone -- Set the time zone with which the dates will be saved: Default: Europe/London. Clear data on map wipe -- Clear command usage data after a wipe. Default TRUE. Print usage limits when command is blocked -- Prints the command usage limits when a player uses one of the configured commands. Default TRUE. Chat Command -- Here you can add, edit or delete commands can be typed in chat (by putting the / character in front of the command), or from console. Command Setting -- The list of commands on which to apply the usage and cooldown limits must be inserted here. Enabled -- If set to TRUE, limits and cooldowns for this command will be enabled. Command -- The command on which to apply limits and cooldowns. Commands alias -- Here you can specify other commands to block with the same configurations. Useful to block a command, which has several similar or differently named commands, to do the same thing. Or alternatively to block multiple commands without creating different configurations. BlockCommand -- If set to TRUE, the command cannot be used by any player, except for players with the permissions: commandlimiter.admin or commandlimiter.bypass.force. SafeZone. Value [AllowOnly | Allow | Block] (Default Allow) -- Sets whether the command can be used in safe zones: AllowOnly: The command can only be used in safe zones. Block: The command cannot be used in safe zones. Allow: No restrictions for safe zones. BuildingBlocked. Value [AllowOnly | Allow | Block] (Default Allow) -- Sets whether the command can be used in areas where you have building permissions: AllowOnly: The command can only be used where you do not have building permissions. Block: The command can only be used where you have building permissions. Allow: No restrictions for building zones. CanBeBypassed -- If set to TRUE the command can be bypassed by players with permission: commandlimiter.bypass. CooldownSeconds -- Cooldown for command reuse. MaxUsagePerMinute -- Limit the use of the command for each minute. MaxUsagePerHour -- Limit the use of the command for each hour. MaxUsagePerDay -- Limit the use of the command for each day. MaxUsagePerWipe -- Limit the use of the command for wipe. BypassPermission (Permissions to bypass the block even if [CanBeBypassed] is set to false) -- Here you can specify one or more names, to create permissions to bypass the limit. If the player has at least 1 of these permissions, he can bypass the limit even if the CanBeBypassed property is set to false. Example: if you enter "vip1” as permission, a command called commandlimiter.bypass.vip1 will be created that you can assign to players. Order Application Limits The usage and cooldown limits of the various commands are applied in the following order: Wipe limits -- If the wipe limits have not been exceeded, proceed to the next check, otherwise the command will be blocked. Daily limits -- If the daily limits have not been exceeded, proceed to the next check, otherwise the command will be blocked. Hourly limits -- If the time limits have not been exceeded, proceed to the next check, otherwise the command will be blocked. Limits per minute -- If the minute limits have not been exceeded, proceed to the next check, otherwise the command will be blocked. CooldownSeconds -- The command will be executed if the cooldown has expired, otherwise you will have to wait for the cooldown to reset. LOCALIZATION The plugin are translated into the following languages: English Italian Translation files are located in the /oxide/lang folder, here is an example of a /oxide/lang/en/CommandLimiter.json translation file. You can add translations for other languages by adding them to the folder: /oxide/lang

Allows complete individual settings of Beds, Towels, Bags & Campers using Permissions or Global setters with radius, limits Unlock Time, Respawn Cooldown! Improves server/client performance by auto-managing players bag limits & radius! You can assign a bed to a friend on your friends list in game & when they join it will give them the invite to join your team to get the bed/bag/towel/etc! Notes: Better Vanish ( the paid version ) has known bugs with chat commands not working while in vanish. To resolve the problem leave vanish mode. Permissions You can add or remove as many permissions as you'd like in the config! Player Chat Commands /bag <Shows just the limits & how many of what you have placed.> /bag bags | towels | beds | campers <Selects & shows how many of the specific bag you have placed down.> /bag towels clear | rename | limits /bag towels clear <Clears all of the selected bag type from the player that ran the command> /bag towels rename dingus <Renames all of the selected bag type to the new name> Configuration { "Toggle Offline Team Invite System through bag gifting. Default: Off": false, "# of players that can place a spawn point in a zone radius": 16, "Player Respawn Zone Radius Check": 35, "Sets Global Defaults": { "True Only Owner can set name | False Allows team members": false, "Sets Total Max Limit within a radius": 12, "Sets Limit radius": 35, "Sleeping Bags": { "DefaultTextName": "Unnamed Bag", "SecondsBetweenReuses": 300.0, "UnlockTime": 30.0 }, "Towel Bags": { "DefaultTextName": "Unnamed Towel", "SecondsBetweenReuses": 300.0, "UnlockTime": 30.0 }, "Beds": { "DefaultTextName": "Bed", "SecondsBetweenReuses": 120.0, "UnlockTime": 30.0 }, "Camper Bags": { "DefaultTextName": "Unnamed Camper Seat", "SecondsBetweenReuses": 120.0, "UnlockTime": 30.0 } }, "Player Permissions": { "vip1": { "True Only Owner can set name | False Allows team members": false, "Sets Total Max Limit within a radius": 12, "Sets Limit radius": 35, "Sleeping Bags": { "DefaultTextName": "Unnamed Bag", "SecondsBetweenReuses": 150.0, "UnlockTime": 20.0 }, "Towel Bags": { "DefaultTextName": "Unnamed Towel", "SecondsBetweenReuses": 150.0, "UnlockTime": 20.0 }, "Beds": { "DefaultTextName": "Bed", "SecondsBetweenReuses": 60.0, "UnlockTime": 20.0 }, "Camper Bags": { "DefaultTextName": "Unnamed Camper Seat", "SecondsBetweenReuses": 150.0, "UnlockTime": 20.0 } }, "vip2": { "True Only Owner can set name | False Allows team members": false, "Sets Total Max Limit within a radius": 12, "Sets Limit radius": 35, "Sleeping Bags": { "DefaultTextName": "Unnamed Bag", "SecondsBetweenReuses": 75.0, "UnlockTime": 15.0 }, "Towel Bags": { "DefaultTextName": "Unnamed Towel", "SecondsBetweenReuses": 75.0, "UnlockTime": 15.0 }, "Beds": { "DefaultTextName": "Bed", "SecondsBetweenReuses": 30.0, "UnlockTime": 15.0 }, "Camper Bags": { "DefaultTextName": "Unnamed Camper Seat", "SecondsBetweenReuses": 75.0, "UnlockTime": 15.0 } } } }

Features : Set a maximum sleepingbag/bed limit per player with permissions Debug mode available through cfg settings Player commands for info/limitations Notifies the player he has reached the limit Support for sleepingbags/beachtowels (combined) Support for beds Settings for respawn cooldown Admin perm for bypass limits and cooldown ignore Set a Welcome message on sleeping bags and beds if placed Set Max rename to 1x and block others from renaming a sleepingbag/bed Sleepingbag + Beachtowel share settings (subject to change) Beds have their own settings Various messaging on placement (restricted/info/remaining or when reached the limit) Can refund true/false if reached the limit Commands : /bag info : Shows Plugin info + commands list /bag mylimit : Replies with the settings for your permission and how many placements you have left /bag check {playername or id} : list amounts and bag/bed id's in a list (admin) /bag teleport {bagid} : Teleports you to the bag/bed id (admin) /bag remove {bagid} : Removes the bagi/bed with that ID (admin) /bag purge {playername or id} : Removes all bags and beds from that player (admin) Permisions : betterbeds.restrictdefault : Gives the limitations to default rank/player betterbeds.restrictvip : Gives the limitations to vip rank/player betterbeds.renameblock : Blocks renaming of bag is not yours betterbeds.chat : Grants chat command usage betterbeds.admin : Sets bypass for admins or assigned player betterbeds.nocd : Grants no cd on respawning on sleepingbags/beds betterbeds.denypickup : Blocks picking up any placed sleepingbags/beds Configuration : { "Settings Plugin": { "Debug": false, "Chat Steam64ID": 0, "Chat Prefix": "[<color=yellow>Better Beds</color>] " }, "Settings Global": { "Bag cooldown": 30.0, "Bed cooldown": 20.0, "Only 1x rename per placement": false, "NO bed/sleepingbag cooldown": false }, "Settings Bags": { "Refund Sleepingbags": true, "Max placements Default": 5, "Max placements Vip": 10 }, "Settings Beds": { "Refund Beds": true, "Max placements Default": 1, "Max placements Vip": 3 } } Language file : { "InvalidInput": "<color=red>Please enter a valid command!</color>", "BagText": "Welcome to our server", "Version": "Version : V", "LimitBags": "You have been limited to {0} sleeping bag(s)", "LimitBeds": "You have been limited to {0} bed(s)", "MaxLimitDefault": "You have already placed the limit of {0} for a player", "MaxLimitVip": "You have already placed the limit of {0} for VIPs", "LimitHeader": "Your Restrictions and Placements:", "Info": "\n<color=green>Available Commands</color>\n<color=green>/bag info</color> : Shows info on version/author and commands", "InfoMyLimit": "\n<color=green>/bag mylimit</color> : Lists your restriction heights and placements", "InventoryFull": "<color=red>You had no inventory space; no item was refunded!</color>", "InventoryNotFull": "<color=green>Your item has been refunded!</color>", "NoPermission": "<color=red>You do not have permission to use that command!</color>", "RenameBlock": "<color=red>Renaming is blocked on this server</color>", "RenameBlock2nd": "<color=red>Max 1 rename allowed on this server</color>", "BagsUsed": "You have placed {0}", "BagsLeft": "You have {0} placement(s) left", "RestrictedLimit": "You are restricted to placing only 1 sleeping bag and 1 bed.", "TargetPlayerMaxLimit": "The player {0} has reached their maximum number of beds/bags.", "BagCheckHeader": "Bag/Bed count for player {0}:", "BagCount": "Bags: {0}", "BedCount": "Beds: {0}", "PlayerNotFound": "Player {0} not found.", "InvalidInputCommand": "Invalid input. Please use '/bag check playerName'.", "InvalidBagID": "Invalid bag ID format. Please provide a valid ID.", "BagNotFound": "Bag with ID {0} not found.", "BagRemoved": "Bag with ID {0} has been removed.", "TeleportedToBag": "You have been teleported to the bag with ID {0}.", "PurgeSuccess": "All bags and beds for player {0} have been removed.", "PurgePlayerNotFound": "Player {0} not found. No bags were purged.", "BagIds": "Bag IDs: {0}", "BedIds": "Bed IDs: {0}" }

Personal Heli Give your players the power to summon their own personal patrol helicopter! This plugin lets players call in a customizable helicopter with tiered permissions, configurable costs (Scrap, Economics, ServerRewards), and advanced privacy controls (Owner, Team, Friends, Clan, PVE, Public). Features include: Multiple helicopter tiers with unique cooldowns, health, speed, and costs In-game UI for easy heli requests and status Announcements in chat and Discord (optional) Full support for Economics, ServerRewards, Friends, and Clans plugins Advanced privacy: restrict who your heli can attack or protect Admin override and full configuration support Perfect for VIP perks, events, or just adding a new layer of fun and strategy to your Rust server!

No more sleeping bag cooldowns ! Great for those crazy, heavy modded servers. You can control to which users the cooldown will be removed by granting the permission OxidationNoBagCooldown.Allow. If you'd like to remove the cooldown to all your players just grant the permission to the default group on the console like so: oxide.grant group default OxidationNoBagCooldown.Allow

This plugin sets the cooldown for suicide when you type "kill" from the console in the game or select "Respawn" from the ESC screen. Restricts players from quickly committing suicide and respawning. Permission: You must give "suicidecooldown.use" permission to the oxide groups you want to set the cooldown for. Configuration: You can set the desired cooldown time in the "Default suicide time (seconds)" section. If you want to customize your notifications with the Notify plugin, you can set the "Use Notify plugin" section to "true". ( Notify plugin is required. ) { "Settings": { "Default suicide time (seconds)": 60, "Use Notify plugin": false } }

Features Removes the delay after suiciding. Usage - Copy the downloaded DLL file into server/HarmonyMods folder Support - If you need help or If you have any issues or suggestions you can contact me by joining my discord server: https://discord.gg/efVKDG6z6F or by adding me on discord: Farkas#6006

A must have for PVE servers! Allows you to modify the damage rate of the MLRS for Player bases, raidable/abandonded bases, and NPCs. Also allows you to adjust the cooldown timer of the MLRS. Console Commands mlrsdamage.damage <amount> - Changes damage multiplier amount. mlrsdamage.cooldown <amount> - Changes server cooldown timer for MLRS mlrsdamage.pvp <true/false> - Enable/Disable player pvp damage done by MLRS mlrsdamage.pvpbase <true/false> - Enable/Disable player base damage done by MLRS mlrsdamage.raidable <true/false> - Enable/Disable raidable/abandoned base damage done by MLRS mlrsdamage.npc <true/false> - Enable/Disable NPC damage done by MLRS mlrsdamage.rockets <amount> - Change total capacity of rockets able to be fired by MLRS mlrsdamage.module {true/false} - Enable/Disable the need for an Aiming Module mlrsdamage.interval {amount} - Change the interval between rocket launches Configuration "MLRS Settings": { "MLRS Damage Multiplier": 1.0, // scale at which the MLRS does damage "Allow Damage to Player entities": true, // allow damage to player owned entities "Allow Damage to Players": true, // allow damage to players "Allow Damage to Raidable and Abandoned Bases": true, // allow damage to Raidable or Abandoned Bases "Allow Damage to NPCs": true, // allow damage to NPCs on the map "MLRS Cooldown time (in minutes)": 10.0 // cooldown timer for MLRS, default is 10 "Total Rockets for MLRS to fire": 12 // total number of rockets to shoot in a single barrage, default is 12 "Rocket Launch Interval (in seconds)": 0.5, // time inbetween rocket launches. Must be positive, but can cause issues if set lower than 0.1 "Requires Aiming Module": false // When set to true, an aiming module is always put in the MLRS and is locked from being looted by players }

A plugin that allows server owners to prevent their staff from bypassing suicide cooldown, along with adding configurable suicide cooldowns. Working on a better unload and load process. Documentation Just use the config to enable/disable the default respawn cooldown of 60 seconds, if you put false for the Default Suicide Cooldown, then it will follow whatever cooldown value you put into Suicide Cooldown. This can be however long you want, from 0-9999999. Initalization Upon loading the plugin, it will update the users cooldown if the default cooldown is disabled and the cooldown is less than 60 seconds (the default). This means if you have it set to 40 seconds, and the users cooldown is at 50, it will be set to 40 instead. However, if the cooldown happens to be 120 seconds, the plugin during loading will do nothing because I have no fair way of making a user who suicided prior to loading the plugin wait longer after already waiting a while. Unloading Upon unloading this plugin, if the cooldown for the user is longer than the default cooldown, it will update their cooldown to the default cooldown. However, if your suicide cooldown is less than typical respawn times, it does nothing since I couldn't find a fair way to set it to 60 without knowing that they did or didn't just wait 50 seconds to try to suicide (ie, if the suicide cooldown happened to be 55), and then the plugin got unloaded and the user now has to wait another 60 seconds. Config (Default Config) { "Default Suicide Cooldown": false, "Suicide Cooldown": 10, "Round the suicide cooldown to a whole number when displaying to user": true, "Send responses to the user via F1 Console": true, "Send responses to the user via chat": true }

Temporarily or permanently restrict players to sending one message per configured interval. Permissions slowmodechat.exclude - Excludes granted players/groups from slowmode Console Commands slowmode enable - Enable slowmode slowmode disable - Disable slowmode slowmode interval <seconds> - Adjust the interval between messages slowmode reload - Load new config values without reloading the entire plugin Configuration Enabled - Enables slowmode Rcon_Only - Forces console commands to be ran via rcon Permission_Enabled - Enables slowmodechat.exclude permission Interval - Adjust the interval between messages Icon by @SawyerWD