Search the Community

Give players rewards they can unlock Choose the rewards and how many points each one takes to unlock. Players earn points, for example by playing, then claim unlocked rewards in Rust. They keep their points after claiming a reward. Oxide and Carbon · Multiple reward catalogues on one server Open the PimpMyRust configurator → How it works in Rust The configurator’s Survival example awards 1 point for every 15 minutes of active play. At 1 point, the player unlocks 100 wood. At 2 points, after 30 minutes, the player also unlocks 50 cloth. They type /starter to open the menu and claim the rewards. After claiming both, they still have 2 points. They need one more to unlock 750 stones at the next milestone. The Survival catalogue at 2 points How players earn points Custom Rewards has three automatic ways to award points. Choose one per catalogue. Active playtime. Players earn the number of points you set for each interval of active play. Daily bonus. Players earn points once a day after reaching the amount of active playtime you set. Welcome bonus. Players earn points once, on their first connection with access to the catalogue. Manual awards. An admin can give points in Rust chat with /customrewards_give <catalogue> <player or SteamID> <points>. This command uses the customrewards.admin permission. Integrate other plugins. Use External mode to let another plugin handle automatic progression. A compatible or custom-built plugin can use the Custom Rewards API to award a player points in a catalogue of your choice. For example, an event plugin can award points after a challenge. Reward votes with Vote Reward The Vote Reward bundle includes Vote System and Custom Rewards. Vote System collects votes, Vote Reward opens the menu with /votes, and Custom Rewards delivers the rewards. The included catalogue unlocks rewards based on how many times the player votes. Create a catalogue in PimpMyRust Start with an example or create a catalogue. Choose how players progress and which command opens the menu. Add rewards and set their milestones. A reward can give out Rust items, grant access to a group, or run a command. Download the catalogue or send it to a connected server. You can also edit its JSON file directly. Five included menu layouts Pick a layout in the PimpMyRust configurator. Change titles, colors and illustrations to suit your server. Manual installation Extract the ZIP and merge its folders into oxide/ or carbon/. Load the included PimpMyCUI 1.4.0, then CustomRewards. Keep the manifest and five layouts together in data/PimpMyCUI/plugin-pages/customrewards/. On first load, CustomRewards creates data/CustomRewards_rewards/main.json. Review the sample reward, set Enabled to true and reload. Grant customrewards.main.use and test /rewards_main. PimpMyCUI and the included layout files are required for the reward menu. The installation guide covers migration from the separate Playtime Reward extension. You can edit the JSON directly or use the optional PimpMyRust configurator. Installation guide → · Codefling support →

SimplePVE Simple, powerful PVE for Rust. Control every damage, raid, loot and protection rule from a clean in-game menu. Save rules as profiles and switch between them on a schedule. Run a full PVE server, weekend purges or a hybrid PVE/PVP server, all from one plugin. Tip No server.pve needed. SimplePVE handles everything itself. Keep server.pve false. Video Showcase Features Rules and profiles In-game rule manager (/sprules). Toggle every rule with one click, no config editing needed. Rule profiles. Save several rule sets (for example Normal PVE, Raid Weekend, Event Night), then duplicate, rename and switch them live. Easy rule categories. Damage, raiding, looting, NPCs, traps, vehicles, Deep Sea and Apartments. Debug mode (/spdebug). Shows exactly which rule blocked or allowed a hit. Schedules and purges Automatic PVE/PVP purges. PVP turns on and off by itself on your schedule. Weekly schedules. Pick days and times, like Friday 18:00 → Sunday 22:00 or weekends only. Dated schedules. For example January 1 → January 7, holiday events or wipe weekends. Priorities. Several schedules can overlap and the highest priority wins. Outside every schedule, your base profile runs. Run commands when a purge starts or ends. Master switch (/simplepve on|off). Pauses everything and turns the server vanilla in one command. Protection Loot protection. Corpses, backpacks, boxes and supply drops are protected from other players, with team access. Building, vehicle and boat protection. Separate rules for your own, your team's and other players' property. Vehicle auto-claim. Vehicles are claimed when you start the engine. You can also lock claimed vehicles to the owner and their team. Admin bypass permissions for loot and damage. Zones and events ZoneManager support. Create PVP zones inside your PVE server. Exclude zones from the global PVE rules. PVP delay when leaving a PVP zone. Nobody can escape a fight by stepping out. Works with many popular event plugins. HUD, status and notifications SimplePVE HUD. Shows the current mode, what's next, a live countdown and a progress bar. Green when safe, red during raid time. In-game HUD editor (/sp_change). Move it and save it without touching the config. Status UI for PVE/PVP, PVP zones, PVP delay, purge countdown and Deep Sea (via CustomVitalsManager). Discord embeds when a purge starts or ends, plus optional early warnings. In-game warnings before every schedule change. Chat, UI, Toastify or Notify for warning messages. Multi-language. Every message is in the lang file, sent in each player's language. Profile names can be translated too. How it works Rules. Open /sprules and set what players can and can't do. Profiles. Save those rules as a profile, and create more for different situations. Schedules. Tell SimplePVE when each profile (or full PVP) should run. Players see it. The HUD shows the current mode and counts down to the next change, with chat and Discord warnings ahead of time. Note Example setup: Base profile PVE all week. A weekly schedule switches to PVE OFF (full PVP and raiding) every Saturday 18:00 → Sunday 23:00. Players get a warning 30 minutes before, and Discord announces the purge. Rule categories Category What it controls General Friendly fire, suicide, sleepers, radiation, codelock raids, wallpaper, bee swarms, clan support Player Player vs player, animals, NPCs, vehicles, boats, buildings (own / team / others), twigs Deep Sea PVP and boat damage out in the Deep Sea NPC NPCs, animals, Patrol Heli, Bradley and SAM sites vs players and buildings Entity Walls, barricades, MLRS, vehicle collisions and all traps Loot Loot protection, team access, PVP-zone looting, supply drops, Deep Sea looting Zone ZoneManager integration and the PVP delay Apartment Apartment combat zones, master keys, break-ins, rental shops, basement bribes Commands Command Type Description /sprules Chat Open the menu for rules, profiles and schedules /simplepve Chat & Console Toggle SimplePVE on or off /simplepve on / /simplepve off Chat & Console Turn SimplePVE on, or turn it off (vanilla, schedules paused) /spdebug Chat & Console Debug mode: shows why damage was blocked or allowed /sp_change Chat Open the in-game HUD position editor /sp_hide Chat Hide or show the SimplePVE HUD (players, name set in the config) /spve.langkeys Chat & Console Create lang keys for your profile names so they can be translated /resetsprules Chat & Console Reset the rules to default Permissions Permission Allows simplepve.admin Using the admin commands and the /sprules menu simplepve.adminloot Looting other players' protected containers and using their claimed vehicles simplepve.admindamage Damaging any entity while PVE is on Hosting partner Game hosting perfected, that's Physgun. Join the thousands of server owners using Physgun to take their game server communities to the top. Get your server at Physgun Installation Upload SimplePVE.cs to oxide/plugins. Make sure server.pve is false. Grant yourself admin: oxide.grant user YourName simplepve.admin Type /sprules in game and set up your rules. (Optional) Create profiles and schedules in the same menu. (Optional) Set your timezone (see below) if you use schedules. Schedule timezone Schedules use UTC plus your offset in minutes. Set it in the config under Schedules Setting → UTC Time Difference. Your timezone Calculation Value UTC 60 × 0 0 United Kingdom (GMT+1, summer) 60 × 1 60 Central Europe (UTC+2) 60 × 2 120 Bangladesh (UTC+6) 60 × 6 360 US Eastern (UTC−4) 60 × −4 -240 US Pacific (UTC−7) 60 × −7 -420 Warning Schedules starting at the wrong time? Your UTC Time Difference doesn't match your timezone. Fix it and reload the plugin. Configuration Tip Translating: copy the lang file to another folder (for example oxide/lang/de/SimplePVE.json) and translate the values. Each player gets their own language. Run /spve.langkeys to add lang keys for your profile names too. FAQ Does SimplePVE need server.pve? No. Keep server.pve set to false. SimplePVE does all the protection itself. Where do I change the rules? Type /sprules in game (needs simplepve.admin). Every rule is a toggle, and changes save to the profile you're editing. What are profiles? A profile is a saved set of rules. Make one for normal PVE days and one for raid weekends, then switch them by hand or let a schedule switch them. Can I make automatic purges? Yes. Create a schedule in /sprules → Schedules, pick what it runs (a profile, PVE ON or PVE OFF) and when. Outside every schedule, your base profile runs. Weekly or date-based schedules? Both. A schedule's time windows can be weekly (days and times, or a day-to-day span) or dated (a date range, or a daily time inside a date range). When schedules overlap, the one with the highest priority wins. My schedules start at the wrong time. Your UTC Time Difference doesn't match your timezone. See Schedule timezone above. How do I turn PVE on or off by hand? /simplepve on or /simplepve off (needs simplepve.admin). Off makes the server vanilla and pauses all schedules until you turn it back on. Damage still happens in PVE mode. Why? Either one of your rules allows that damage, or another plugin changes damage too. Turn on /spdebug to see which rule decided each hit, and turn it off again when you're done. How does loot protection work? Players can't loot other players' corpses, backpacks, containers and called supply drops. Teammates can if you allow it. Admins with simplepve.adminloot can bypass it. Add entity short names to Loot Protection Excluded Entitys to keep them open to everyone (mailboxes and drop boxes by default). Can admins damage things while PVE is on? Yes, with the simplepve.admindamage permission. Does it support ZoneManager? Yes. ZoneManager zones can run PVP inside your PVE server, with an optional PVP delay when players leave. List zone IDs under Exclude Zone IDs From Rules to keep SimplePVE out of them completely. Can it post to Discord? Yes. It sends embeds when a purge starts or ends, and optional warnings a set number of minutes before. In-game warnings work without Discord too (Warn Players Before Schedule Change). Can I run commands when a purge starts or ends? Yes. Add them to Commands when PVP Purge Starts and Commands when PVP Purge Ends. The menu or HUD looks see-through. Keep UI - Use blur materials set to false. Blur is broken on Rust's new render pipeline. For developers Hooks and API void OnSPVEPurgeStarted() void OnSPVEPurgeEnded() TimeSpan GetPVPStartTimeRemaining() TimeSpan GetPVPEndTimeRemaining() bool IsServerPVE() bool IsStatusEnabled_API() bool AddToExcludeZone(string zoneId) bool RemoveFromExcludeZone(string zoneId) Override hooks. Return true or false to force the result and skip SimplePVE's own checks. Return null to let SimplePVE decide. object CanEntityTakeDamage(BaseCombatEntity entity, HitInfo hitInfo) // true = allow damage, false = block object CanEntityBeTargeted(BasePlayer player, BaseEntity entity) // true = allow targeting, false = block object CanEntityTrapTrigger(BaseTrap trap, BasePlayer player) // true = allow trigger, false = block Support Need help or found a bug? Open a support ticket on this page or join the Discord. Check out my other plugins

TreasureEvent.cs Description : - This plugin offers a complete treasure hunt event system for your Rust server, with real-time distance tracking and customizable loot rewards. Settings : - HUD colors - Event duration (in F1 commands) - Server message (true/false) - Items (customize everything you want in the treasure, even the skins of the items) Server message = true (you need the ServerMessage.cs plugin, https://codefling.com/plugins/server-message) Server message = false (these messages will appear in the global chat, replacing the UI) F1 Commands : - t.start <x> <z> <time> (the treasure appear in a specific location) - t.stop Permissions : - ownerid <steamID/user> WuyZar's Discord : https://discord.gg/NVwRcQwGwh

ServerPeriods.cs Description : - This plugin offers a complete periodic event system for your Rust server, allowing you to create structured game phases with customizable restrictions. Each period can independently control PvP, raiding, gathering, and building permissions, providing a dynamic gameplay experience. It includes a persistent, real-time user interface displaying the current period name and remaining time, with an automatic "Next Period" indicator, and the execution of custom server commands for each period. Settings : - HUD colors - Custom periods (name/perms/time/commands) F1 Commands : - p.start (to start the periods) - p.stop (to stop the periods) - p.next (to move on to the next period) - p.prev (to move on to the previous period) Permissions : - ownerid <steamID/user> WuyZar's Discord : https://discord.gg/NVwRcQwGwh Chat messages : Game interface :

PlayerDuel.cs Description : - This plugin allows players to duel 1v1 in a dedicated arena. After the fight, you respawn with your original inventory and stats; the arena automatically regenerates between each duel. Settings : - HUD colors - Warmup Time - Fight Time - Request Time F1 Commands (ADMIN) : - pd.spawn1 (To set spawn player 1) - pd.spawn2 (To set spawn player 2) - pd.zone <radius> (To define the zone, arena's auto-clear. - pd.kit <name> (To crate kit) - pd.kits (To see kits list) - pd.deletekit <name> (To remove kit) - pd.test (To test the duel) - pd.stop (To stop a duel) Chat Commands : - /duel <name> <kit> - /duel accept - /duel refuse - /duel (To see kits and commands) Permissions : - ownerid <steamID/user> WuyZar's Discord : https://discord.gg/NVwRcQwGwh Test video : Rust 2026-03-28 18-03-26 - Trim.mp4 Game interface :

Provides timed/manual/disabled unlocking of workbenches. Introduction This plugin will allows the server owner to lock out any or all workbenches from being crafted until specified amounts of time have elapsed since start of wipe, or indefinitely / until manually unlocked. Also optionally supports blocking research of locked workbenches so that players can't then replicate them via industrial crafters. Supports the following notification method(s) on craft/research failure: Chat (up to once every 5 seconds), sound, toast. Tutorial Island players are exempted from lockouts, as completing that requires crafting a Level 1 Workbench. Important This plugin is based on "Timed Workbench" by DizzasTeR, but is a significant overhaul. The two plugins cannot coexist in a single server installation. The plugin will detect map wipes and will automatically refresh the workbench locks. To facilitate other forms of wiping, the server owner/maintainer may manually invoke the `twwipe` command. Permissions * `timedworkbenchunlock.skiplock` — Enables bypass for all blocking checks * `timedworkbenchunlock.admin` — Gives access to **all** commands below * `timedworkbenchunlock.broadcast` — Gives access to the `twbroadcast` command * `timedworkbenchunlock.info` — Gives access to the `twinfo` command * `timedworkbenchunlock.modify` — Gives access to the `twmodify` command * `timedworkbenchunlock.reload` — Gives access to `twreload` command * `timedworkbenchunlock.reset` — Gives access to `twreset` command * `timedworkbenchunlock.wipe` — Gives access to `twwipe` command Note: No permissions are granted automatically. Commands * `twbroadcast <value>` — Configure global status broadcast period to the specified number of seconds, or specify a non-positive number to disable * `twinfo` — Prints elapsed time since wipe, and unlock status and times for each workbench tier * `twmodify <tier> <value>` — Configure lockout for the given workbench tier, where a negative value is indefinite lockout, zero is unlocked, and a positive value is the number of seconds to unlock after start of wipe * `twreload` — Reload the config file to pick up manual changes while the server is running * `twreset` — Resets config to the default settings (**be careful with this!**) * `twwipe` — Resets the last wipe timestamp to the current time, effectively restarting the lockout timers Configuration Example config file: { "Block crafting of locked workbench(es)": true, "Block deploying of locked workbench(es)": true, "Block researching of locked workbench(es)": true, "Report blocking via chat message": false, "Report blocking via sound effect": true, "Report blocking via toast message": true, "Global status broadcast interval in seconds (0 to disable)": 300, "Time that current wipe started (UTC)": "2026-08-07T19:59:52.1442827Z", "Workbench unlock times (seconds from start of wipe, or 0 for unlocked, or -1 for permanently locked)": [ 86400, 172800, 259200 ] } Except for detailed tweaks to wipe time, all of the config settings are modifiable via ingame comands. Credits * DizzasTeR for the original "Timed Workbench" plugin on which this is based * Umod.org documentation/forums/discord * Other plugins as examples of best practices and Oxide API usage * MrBlue for being patient with me lol * misticos for detailed feedback

Want the locked crate timer to go faster but not for free? Trade bullets for time and shoot your timer down! Powerful and easy config to give you full control. Chat commands (only enabled with config): /slcspawn - Spawn a locked crate at your location /slcremove - Remove looked at crate Permissions Need permission to use commands: shootablelockedcrates.admin Config Default config includes most weapons, but it's highly recommended to at least look over and tweak it as needed. Note that DLC weapons count as a unique item and has to be added separately (look at rifle.ak as example) Default weapon damage - How many seconds to remove from timer when weapon not specified Weapon damage - {"weapon.short.name": seconds} How many seconds to remove from timer with specified weapon, overrides default weapon damage for this weapon Default bullet damage - How many seconds to remove from timer when bullet is not specified Bullet damage - {"bullet.short.name": seconds} How many seconds to remove from timer with specified bullet, overrides default bullet damage for this bullet Time removed from weapons and bullets are added together before the crate timer is changed, this gives some interesting options. Examples using default config: Using a rifle.ak (3.0) with ammo.rifle (1.0) will remove 4 (3.0 + 1.0) seconds from the timer each shot Using a rifle.ak (3.0) with ammo.rifle.hv (2.0) will remove 5 (3.0 + 2.0) seconds from the timer each shot Using a rifle.bolt (10.0) with ammo.rifle.hv (2.0) will remove 12 (10.0 + 2.0) seconds from the timer each shot Negative numbers also work. Using a pistol.nailgun (0.0 because of default weapon damage) with ammo.nailgun.nails (-1.0) will add 1 (0.0 - 1.0) second to the timer each shot { "Default weapon damage": 0.0, "Weapon damage": { "rifle.ak": 2.0, "rifle.ak.diver": 2.0, "rifle.ak.ice": 2.0, "rifle.lr300": 4.0, "rifle.m39": 7.0, "rifle.bolt": 10.0, "rifle.l96": 20.0, "rifle.semiauto": 3.0, "rifle.sks": 3.0, "shotgun.double": 0.5, "blunderbuss": 0.5, "shotgun.m4": 0.5, "shotgun.pump": 0.5, "shotgun.spas12": 0.5, "smg.2": 2.0, "smg.mp5": 0.5, "smg.thompson": 0.5, "pistol.m92": 2.0, "pistol.prototype17": 4.0, "pistol.python": 5.0, "pistol.revolver": 2.5, "pistol.semiauto": 2.0, "minigun": 0.5, "hmlmg": 1.0, "lmg.m249": 1.5 }, "Default bullet damage": 0.0, "Bullet damage": { "ammo.rifle": 1.0, "ammo.rifle.hv": 2.0, "ammo.rifle.explosive": 3.0, "ammo.pistol": 1.0, "ammo.pistol.hv": 2.0, "ammo.pistol.incendiary": 3.0, "ammo.shotgun": 0.2, "ammo.shotgun.fire": 0.3, "ammo.nailgun.nails": -1.0 } }

The plugin displays the time until restart in the status bar. Depends on AdvancedStatus plugin. The ability to to add and modify any restart plugins; The ability to automatically generate code for restart hooks; The ability to automatically generate language files for different languages(filled in English); The ability to choose between bar types(TimeCounter and TimeProgressCounter); The ability to specify the order of the bar; The ability to change the height of the bar; The abillity to customize the color and transparency of the background; The ability to set a material for the background; The ability to switch between CuiRawImageComponent and CuiImageComponent for the image; The ability to get images from the local folder(*SERVER*\oxide\data\AdvancedStatus\Images); The abillity to set own image and customize the color and transparency of the image; The abillity to set sprite instead of the image; The ability to customize the color, size, font and outline of the text. { "Is it worth generating restart hooks? 0 - disabled, 1 - one-time activation, 2 - always enabled": 2, "List of language keys for creating language files": [ "en" ], "The type of the bar(TimeProgressCounter or TimeCounter)": "TimeCounter", "The height of the bar": 26, "The display order of the bar": 10, "The background color of the bar(HEX or RGBA)": "#E5423F", "The background transparency of the bar": 0.7, "The background material of the bar, leave empty to disable": "", "The URL of the bar image": "https://i.imgur.com/rAiHloW.png", "The local image of the bar, leave empty to use URL": "RestartStatus_Default", "The sprite image of the bar, leave empty to use local or URL": "", "Is it worth using a raw image for the bar?": false, "The color of the bar image(HEX or RGBA)": "#E5423F", "The transparency of the bar image": 1.0, "The outline color of the bar image(HEX or RGBA)": "0.1 0.3 0.8 0.9", "The outline transparency of the bar image": 1.0, "The outline distance of the bar image, leave empty to disable. Example '0.75 0.75'": "", "The size of the bar text": 12, "The color of the bar text(HEX or RGBA)": "#FFFFFF", "The transparency of the bar text": 1.0, "The font of the bar text(https://umod.org/guides/rust/basic-concepts-of-gui#fonts)": "RobotoCondensed-Bold.ttf", "The horizontal offset of the bar text": 0, "The outline color of the bar text(HEX or RGBA)": "#000000", "The outline transparency of the bar text": 1.0, "The outline distance of the bar text, leave empty to disable": "", "The size of the bar subtext": 12, "The color of the bar subtext(HEX or RGBA)": "#FFFFFF", "The transparency of the bar subtext": 1.0, "The font of the bar subtext": "RobotoCondensed-Bold.ttf", "The outline color of the bar subtext(HEX or RGBA)": "0.5 0.6 0.7 0.5", "The outline transparency of the bar subtext": 1.0, "The outline distance of the bar subtext, leave empty to disable": "", "The background color of the progress bar(HEX or RGBA)": "1 1 1 0.15", "The background transparency of the progress bar": 0.15, "Is it worth making the progress reversible?": true, "The color of the bar progress(HEX or RGBA)": "#E5423F", "The transparency of the bar progress": 0.7, "The OffsetMin of the bar progress": "0 0", "The OffsetMax of the bar progress": "0 0", "The list of restart hooks. Note: After modifying hooks, do not forget to toggle hook generation": [ { "Hook triggered at the start of a restart": "OnSmoothRestartInit", "Argument position containing the number of seconds until restart(counting from 0)": 0, "Hook triggered at the cancellation of a restart": "OnSmoothRestartCancelled" }, { "Hook triggered at the start of a restart": "OnRestartScheduled", "Argument position containing the number of seconds until restart(counting from 0)": 0, "Hook triggered at the cancellation of a restart": "OnRestartCancelled" } ], "Version": { "Major": 0, "Minor": 1, "Patch": 1 } } EN: { "BarText": "RESTART IN" } RU: { "BarText": "РЕСТАРТ ЧЕРЕЗ" }

Temp grants users VIP either randomly or by being one of the first X amount of people to join after wipe. A great incentive to get players to join right on wipe and a great way to reward players for joining and playing! FEATURES - Grant vip to random players on join based on a % chance - Grant vip to the first X amount of players to join after wipe - Options to remove the ranks on next wipe - Options to remove the ranks on a time basis - ETC* CONFIG { "VIP options on new wipe": { "Grant VIP on wipe to the first X amount of joiners (0 = disabled)": 10.0, "Oxide group to grant": "vip", "Remove rank after X minutes (0 = disabled)": 120.0, "Remove rank on new wipe": true, "Count as a free VIP rank if the user already has that VIP rank": false }, "Random VIP granter options": { "Random % chance of user getting a VIP rank on join (0 = disabled)": 5.0, "Oxide group to grant": "vip", "Max Random VIP's given per wipe (0 = inf)": 10.0, "Remove rank after X minutes (0 = disabled)": 120.0, "Remove rank on new wipe": true, "Allow user to randomly get VIP more than once a wipe": false } } Need support or want updates about what is coming to the plugin? Join the support discord here https://discord.gg/RVePam7pd7

Introducing Parkour Pro, the ultimate tool to elevate your server experience! What's better than a heart-pounding challenge? Bragging rights, of course. Engage your players with a thrilling parkour adventure that not only tests their skills but also lets them flaunt their victories. With Parkour Pro, setting up a captivating parkour area on your server is a breeze. Define the starting point, the exhilarating path, and the sweet taste of victory at the end—all at your fingertips. This plugin empowers you to craft unique parkour courses tailored to your server's theme and vibe. Why should you consider adding a parkour element to your server? Because it's the perfect recipe for increased player engagement and server popularity. As players tackle these dynamic courses, your server's metrics will soar, creating an environment that's not only fun but also competitive. To kickstart your parkour revolution, Parkour Pro comes complete with a demo prefab. Brace yourself—this challenging yet conquerable course is ready to captivate your players. Take the first step in transforming your server into a realm of excitement, skill, and, most importantly, epic bragging rights. With Parkour Pro; the thrill is in your hands! Video Walkthrough Permissions parkourpro.admin parkourpro.use - Required to run any parkour courses Console Commands pk_close_ui - Close the UI pk_leaderboard - Show the leaderboard UI pk_courses - List all the courses [Admin Only] pk_clear_course_data - Clear the course data for the given course pk_clear_all_course_data - Clear all course data. pk_wipe_leaderboard "Course_1" → Wipes leaderboard for a single course pk_wipe_leaderboard all → Wipes all leaderboard data Chat Commands /pk_close_ui - Close the UI /pk_leaderboard - Show the leaderboard UI /pk_courses - List all the courses /pk_end - End your current Parkour Run [Admin Only] /pk_clear_course_data - Clear the course data for the given course /pk_clear_all_course_data - Clear all course data. /pk_wipe_leaderboard "Course_1" → Wipes leaderboard for a single course /pk_wipe_leaderboard all → Wipes all leaderboard data For any issues please Reach out to me on Discord: http://discordapp.com/users/233662340179034112

Advanced Timed Permission Management System for Groups Timed Group Permissions allows you to assign permissions to any group for a limited amount of time! You can easily give, revoke, or extend timed permissions — all fully controlled by simple commands. Discord Integration - You can log all permission grants, revokes, and extensions directly to a Discord channel. - Simply add your Discord webhook URL to the config file, then run the command: - oxide.reload TimedGroupPermissions That’s it! Your actions will now be logged automatically to Discord. Data Storage To check which groups currently have timed permissions assigned, open the file: data/TimedGroupPermissions.json Commands Section Chat & Console Commands: 1. givegroupperm <group> <permission> <time> → Give a timed permission to a group. 2. extendgrouptimeperm <group> <permission> <time> → Extend the duration of an existing timed permission. 3. revokegroupperm <group> <permission> → Revoke a permission from a group. 4. viewgroupperm <group> → View all active timed permissions for that group. Example output: [Timed Group Permissions] Permissions for group 'admin': - kits.donadiscord (Expires in 23 hour(s) 59 minute(s) 39 second(s)) Examples givegroupperm admin minicopter.infinitefuel 10d → Gives the group “admin” the permission “minicopter.infinitefuel” for 10 days. extendgrouptimeperm admin minicopter.infinitefuel 10d → Extends the permission “minicopter.infinitefuel” for the group “admin” by an additional 10 days. revokegroupperm admin minicopter.infinitefuel → Removes the permission “minicopter.infinitefuel” from the group “admin”. ------------------------------------------------------------ Default Configuration { "Send messages to Discord Webhook? (Requires DiscordAPI plugin)": true, "Discord Webhook URL": "https://discord.com/api/webhooks/..." } Summary: Timed Group Permissions is the perfect solution for managing temporary permissions on your server. Reward VIP groups, event teams, or temporary staff roles — all with automatic expiration and Discord logging.

The plugin displays the time to wipe from the WipeTimer plugin Features: Shows the exact time before the wipe Ability to display the timer within the time specified in the config, after connecting the player Comprehensive setup of all aspects Option to tailor text for different languages to reach players from various countries Lang files for all languages are auto-generated, so you only need to write your text. Important! Time format for specifying the time to the second: "Time Format": "d\\d\\ hh\\h\\ mm\\m\\ ss\\s",

SAVE 13% WHEN BUYING THE BUNDLE This plugin will allow you to run console commands at any given schedule. The syntax was inspired on the Unix's crontab format but ported to json for easy of use. Below you'll find some examples.. but sky is the limit. +------------- minute (0 - 59) | +------------- hour (0 - 23) | | +------------- day of the month (1 - 31) | | | +------------- month (1 - 12) | | | | +------------- day of the week (0 - 6) (Sunday to Saturday); | | | | | | | | | | | | | | | * * * * * <command to execute> { "Minute": "*", "Hour": "*", "Day": "*", "Month": "*", "DoW": "*", "Command": "ai.sleepwakestats" } New features "@forced" and "!forced" to be used on the Command field as conditionals: /* * > minute = 15, hour = 19, DoW = 4, command = @forced restart 60 * > minute = 15, hour = 12, DoW = 4, command = !forced restart 900 * > The special keys "@forced" and "!forced" will allow you to execute commands * > only of forced wipe days or only on non forced wipe days. This example will * > restart the server every thursday at 12:15 except forced wipe days were it * > will only execute at 19:15. */ New features "@wipe" and "!wipe" to be used on the Command field as conditionals: /* * > minute = @restart, command = @wipe my_command * > minute = @restart, command = !wipe my_other_command * > The special keys "@wipe" and "!wipe" will allow you to execute commands * > only if the map was wiped. This example will execute my_command on server * > restart if the map was wiped otherwise will execute my_other_command. */ Execute the command "ai.sleepwakestats" every 3m: { "Minute": "*/3", "Hour": "*", "Day": "*", "Month": "*", "DoW": "*", "Command": "ai.sleepwakestats" }, Execute the command "status" at 15m of every hour: { "Minute": "15", "Hour": "*", "Day": "*", "Month": "*", "DoW": "*", "Command": "status" }, Restart the server every day at 6:45: { "Minute": "45", "Hour": "6", "Day": "*", "Month": "*", "DoW": "4", "Command": "restart 60" }, Have a specific plugin running only during the weekends: { "Minute": "0", "Hour": "0", "Day": "*", "Month": "*", "DoW": "6", "Command": "oxide.load MyWeekEndPlugin" }, { "Minute": "0", "Hour": "0", "Day": "*", "Month": "*", "DoW": "1", "Command": "oxide.unload MyWeekEndPlugin" } Execute the command "oxide.version" every Tuesday between 10:15 to 10:25: { "Minute": "15-25", "Hour": "10", "Day": "*", "Month": "*", "DoW": "3", "Command": "oxide.version" } Sets the fps limit to 30 at every server restart: { "Minute": "@restart", "Hour": "*", "Day": "*", "Month": "*", "DoW": "*", "Command": "fps.limit 30" } Keeps the plugin MyWeekEndPlugin unloaded during weekend restarts: { "Minute": "@restart", "Hour": "*", "Day": "*", "Month": "*", "DoW": "1", "Command": "oxide.unload MyWeekEndPlugin" }, { "Minute": "@restart", "Hour": "*", "Day": "*", "Month": "*", "DoW": "6", "Command": "oxide.unload MyWeekEndPlugin" }

SimpleEvents allows scheduling console commands for in-game events and separate timed commands. Features: - Schedule custom console commands. - Schedule console commands for in-game events. - Configure independent timed commands. - Choose between sequential or simultaneous execution of timed commands. - Define minimum and maximum intervals for timed commands. - Set minimum player count requirements for timed commands. - In-game events, such as Patrol Helicopter, CH47 Helicopter, Cargo Ship, Cargo Plane, Easter Egg Hunt, Santa's Sleigh, Halloween Hunt, and Bradley APC. Default Config: { "Custom Commands Execution Mode | 1 = Sequentially, 2 = Simultaneously, 3 = Disabled": 1, "Custom Commands": [ { "Commands": [ "", "" ], "Min Interval (s)": 60, "Max Interval (s)": 120, "Min Players": 0 }, { "Commands": [ "", "" ], "Min Interval (s)": 180, "Max Interval (s)": 300, "Min Players": 0 } ], "Patrol Helicopter": { "Commands": [ "", "" ], "Min Players": 0, "Prefab": "assets/prefabs/npc/patrol helicopter/patrolhelicopter.prefab" }, "CH47 Helicopter": { "Commands": [ "", "" ], "Min Players": 0, "Prefab": "assets/prefabs/npc/ch47/ch47scientists.entity.prefab" }, "Cargo Ship": { "Noninitial LootRound Min Players": [], "Commands": [ "", "" ], "Min Players": 0, "Prefab": "assets/content/vehicles/boats/cargoship/cargoshiptest.prefab" }, "Cargo Plane": { "Commands": [ "", "" ], "Min Players": 0, "Prefab": "assets/prefabs/npc/cargo plane/cargo_plane.prefab" }, "Easter Egg Hunt": { "Commands": [ "", "" ], "Min Players": 0, "Prefab": "assets/prefabs/misc/easter/egghunt.prefab" }, "Santa's Sleigh": { "Commands": [ "", "" ], "Min Players": 0, "Prefab": "assets/prefabs/misc/xmas/sleigh/santasleigh.prefab" }, "Halloween Hunt": { "Commands": [ "", "" ], "Min Players": 0, "Prefab": "assets/prefabs/misc/halloween/halloweenhunt.prefab" }, "Bradley APC": { "Commands": null, "Min Players": 0, "Prefab": null } }

This plugin adds an extremely simple (non-invasive) ingame hud to the top right of your screen. /showhud - enable/disable the ingame hud (client-side, will only affect player that runs the command) I plan on updating and adding to this over time so feel free to make suggestions!

ComTimer is a plugin that runs console commands after an amount of time. Good for automating events quickly and easily Set the commands you want to run into the config list. Set a timer upper limit and a timer lower limit and the plugin will pick a number between and countdown... on completion it will run a command from the list and start the whole process over again. any command that you can run in rcon you can run with this. Configuration Default configuration is as follows: { "Command List": [], "Upper Time In Seconds": 500.0, "Lower Time In Seconds": 200.0 } Setting a single command: { "Command List": ["say Welcome to the server"], "Upper Time In Seconds": 500.0, "Lower Time In Seconds": 200.0 } Setting more then one command: { "Command List": ["say Welcome to the server","callheli","giveall scrap 1"], "Upper Time In Seconds": 500.0, "Lower Time In Seconds": 200.0 } Works well with plugins like CustomHeliTiers if the plugin doesn't have its own spawn timer: { "Command List": ["callheli 1","callheli 2","callheli 3","callheli 4","callheli 5","callheli 6"], "Upper Time In Seconds": 500.0, "Lower Time In Seconds": 200.0 }