Search the Community

A plugin for collecting game statistics with database support, compatible with both SQL and web API methods. This functionality empowers website owners to display the desired statistics from the database on their sites. Moreover, it offers the capability to send data via API, which proves highly beneficial in scenarios where your gaming server and database reside on separate machines and the database restricts connections beyond localhost. Please note that an instruction manual will be included in the downloaded file and it is imperative for users to read it thoroughly. Collecting(The full list is available below in the section Collected Data) : Server information; Team information; Clan information; Feedback(F7) information; Report(F7) information; Player information. Sending data through: direct MySQL; via API(POST query) to MySQL. extendedstats.admin - Provides access to command estats. { "Chat command": "estats", "Is it worth enabling GameTips for messages?": true, "Unique ID of the current server": 0, "Database upload method(Disabled, WebAPI, MySQL)": "WebAPI", "Interval in seconds at which an attempt to load changes into the database will occur": 300.0, "Is it worth logging messages to the console when uploading to the database?": true, "API - Service URL": "https://localhost/ExtendedStats/index.php", "API - Service access key": "GlBRw-elM6v-gjko3-cxSDk-Tsy7B", "API - Timeout": 5.0, "MySQL - Host": "localhost", "MySQL - Port": 3306, "MySQL - Database name": "db_playrust", "MySQL - Username": "root", "MySQL - Password": "root", "Database table name - Servers": "db_servers", "Database table name - Teams": "db_teams", "Database table name - Clans": "db_clans", "Database table name - Feedbacks": "db_feedbacks", "Database table name - Reports": "db_reports", "Database table name - Players": "db_players", "Database table name - Players Balances": "db_players_balances", "Database table name - Players Stats": "db_players_stats", "Database table name - Players Farms": "db_players_farms", "Database table name - Players Gambling": "db_players_gambling", "Database table name - Players Kills": "db_players_kills", "Database table name - Players Explosions": "db_players_explosions", "Database table name - Players Raids": "db_players_raids", "Is it worth clearing saved statistics when a wipe is detected?": true, "Is it worth clearing the database when a wipe is detected?": true, "List of statistic categories to clear when a wipe is detected. Leave empty to recreate defaults": [ "players", "teams", "clans", "feedbacks", "reports" ], "List of language keys for creating language files": [ "en" ], "Wipe ID": null, "Version": { "Major": 0, "Minor": 1, "Patch": 6 } } EN: { "CmdMain": "Available commands:\n\n<color=#D1CBCB>/estats</color> <color=#D1AB9A>upload</color> - Initialize a forced data upload to the database\n<color=#D1CBCB>/estats</color> <color=#D1AB9A>save</color> - Save data to a local file on the server\n\n--------------------------------------------------", "CmdDBNotSelected": "Database connection method not selected!", "CmdAlreadyUploading": "You can't initialize a data upload to the database because there is already an active upload!", "CmdUpload": "You have successfully started a forced data upload to the database.", "CmdSave": "Saving data to a local file on the server:\n\n<color=#D1CBCB>/estats save</color> <color=#D1AB9A>clans</color> - Save all clans to a local file on the server\n\n--------------------------------------------------", "CmdSaveNotEnough": "Not enough records to save!", "CmdSaveClans": "Successfully saved {0} clans!" } RU: { "CmdMain": "Доступные команды:\n\n<color=#D1CBCB>/estats</color> <color=#D1AB9A>upload</color> - Инициализация принудительной загрузки данных в базу данных\n<color=#D1CBCB>/estats</color> <color=#D1AB9A>save</color> - Сохранение данных в локальный файл на сервере\n\n--------------------------------------------------", "CmdDBNotSelected": "Метод подключения к базе данных не выбран!", "CmdAlreadyUploading": "Вы не можете инициализировать загрузку данных в базу данных, так как уже существует активная загрузка!", "CmdUpload": "Вы успешно начали принудительную инициализацию загрузки данных в базу.", "CmdSave": "Сохранение данных в локальный файл на сервере:\n\n<color=#D1CBCB>/estats save</color> <color=#D1AB9A>clans</color> - Сохранение все кланы в локальный файл на сервере\n\n--------------------------------------------------", "CmdSaveNotEnough": "Не достаточно записей для сохранения!", "CmdSaveClans": "Успешно сохранено {0} кланов!" } Admin commands. Permission "extendedstats.admin" required: upload - Initialize a forced data upload to the database; save - Save data to a local file on the server: clans - Save all clans to a local file on the server; Example: /estats upload /estats save clans ServerData: ServerName ServerIdentity ServerIP ServerPort QueryPort ServerDescription ServerHeader ServerURL ServerTime ServerTags GameTags MaxPlayers ServerEntities ServerFPS ServerAvgFPS ServerUptime ServerMap MapSize MapSeed FirstSave LastSave WipeID ServerVersion ServerProtocol RconPort RconPassword TeamData: TeamID TeamName CreatorID LeaderID TeamMembers ClanData: ClanID ClanName ClanNameNormalized CreatorID CreatedTime ClanLogo LogoColor Motd MotdTimestamp MotdAuthor ClanRoles ClanMembers Score FeedbackData(Since the corresponding Oxide hook has shifted, not all types of feedback are processed) : ID UserID Subject Type Message Time ReportData: ID UserID TargetID TargetName Subject Type Message Time PlayerData: Info: UserID DisplayName Flags Language GroupsList TeamID ClanID BanReason Connection: PlayedTime - requires the PlaytimeTracker/PlayTimeRewards plugins IdleTime - requires the PlaytimeTracker/PlayTimeRewards plugins Connections Ping FirstConnectionIP LastConnectionIP FirstConnectionDate LastConnectionDate Balance: Balance - requires the Economics plugin Points - requires the ServerRewards plugin BankBalance - requires the BankSystem plugin IQBalance - requires the IQEconomic plugin Experience Reputation - requires the ReputationMaster plugin Statistics: TimeAlive - updates only after the player's death TimeSleeping - updates only after the player's death DistanceWalked - updates only after the player's death DistanceRun - updates only after the player's death TimeWilderness - updates only after the player's death TimeInBase - updates only after the player's death TimeInMonument - updates only after the player's death TimeSwimming - updates only after the player's death TimeFlying - updates only after the player's death TimeBoating - updates only after the player's death TimeDriving - updates only after the player's death Wounded WoundsInflicted WoundAssisted WoundRecovered DamageInflicted DamageTaken - updates only after the player's death Healed - updates only after the player's death ShotsFired - updates only after the player's death ShotsHit RentedAptPenthouses RentedAptStandards RentedAptBasements RentedShops OutbidShops BreakInAptPenthouses BreakInAptStandards BreakInAptBasements BreakInShops HalloweenVisits XmasVisits DeepSeaVisits ExcavatorStarts HeavyFusesInserted BearTrapInflicted BearTrapSteps MineInflicted MineSteps HandcuffsApplied Handcuffed PhoneCalls PhoneCallsTimeout MissionsStarted MissionsSucceeded MissionsFailed DeployedsList MonumentsList - requires the MonumentsWatcher plugin Farming: Barrels UnderWaterCrates ShreddedEntities DetectResourceFlags GreenDoors BlueDoors RedDoors FishAttempts Guts Supplies ExcavatorSupplies TropicalSupplies Chinooks Surveys ChickensHatched ChickenEggs BeehiveXP Blueprints CraftList GatherList RecycleList BuyerPurchaseList BuyerSpentList SellerSalesList SellerRevenueList CratesList FishList Gambling: BWG_Spins BWG_WinSpins BWG_SpendScraps BWG_WinScraps Slot_Spins Slot_WinSpins Slot_SpendScraps Slot_WinScraps Poker_Games - Placeholder Poker_WinGames - Placeholder Poker_SpendScraps - Placeholder Poker_WinScraps - Placeholder BlackJ_Games BlackJ_WinGames BlackJ_StandoffGames BlackJ_SpendScraps BlackJ_WinScraps RPS_Wins RPS_Losses RPS_Draws Kills: Kills FriendlyKills Deaths Suicides Beehives Chickens FarmChickens Snakes Boars Stags Horses Wolves Bears Polarbears Panthers Tigers Crocodiles Sharks PlayerNPCs Scientists Zombies Patrols Bradleys KillVehicles: PedalBikes MotorBikes Cars RowBoats RHIBs SubmarinesSolo SubmarinesDuo Tugs MiniHelis AttackHelis ScrapHelis Balloons Trains TrainWagons TrainCabooses Snowmobiles Ballistas BatteringRams Catapults SiegeTowers HitParts KillParts KillWeapons Explosions: Rockets RocketsHV RocketsIncendiary RocketsSmoke RocketsMissile RocketsMLRS Torpedoes ExplosiveAmmo Ammo40mmExplosive Ammo40mmSmoke GrenadesF1 GrenadesMolotov GrenadesFlash GrenadesSmoke GrenadesBean SatchelCharges C4Explosives PropaneBombs FireBombs CannonBalls MortarShells MortarFragShells Raids: Cupboards Doors Windows Foundations Ceilings Walls Doorways WindowFrames Stairs Hatches ExtWoodenGates ExtWoodenWalls ExtStoneGates ExtStoneWalls ExtIceWalls ExtIceShortWalls RaidedConstructionsList RaidedDeployableConstructionsList RaidableBases

DynamicData — Wipe Progression Automation Automate your wipe. Evolve your server. Stop replacing plugin data files by hand every few hours or days. DynamicData automatically deploys prepared JSON data profiles as your Rust wipe progresses. You decide what should change and when; DynamicData follows the timeline, copies the correct file and reloads the target plugin when needed. Start the wipe with accessible settings. Increase difficulty and rewards after 12 hours. Unlock advanced content on day two. Save heavier changes for the next restart. Once the profiles are prepared, every wipe follows the same progression without an administrator watching the clock. Simple filename-based scheduling There is no complicated calendar to configure. The schedule is written directly into each filename: ```text Settings.json Settings12h.json Settings2d.json [email protected] [email protected] ``` These files all update the same destination, `Settings.json`: - `Settings.json` — applied at the beginning of the wipe - `Settings12h.json` — applied 12 hours after the wipe - `Settings2d.json` — applied two days after the wipe - `[email protected]` — ready after four days, then applied on the next restart - `[email protected]` — applied on the next cold server start Days, hours, minutes and seconds can be combined, for example `1d12h30m`. Keep your existing folder structure DynamicData mirrors nested folders into `oxide/data`. ```text oxide/data/DynamicData/RaidableBases/Profiles/Settings12h.json ``` is deployed as: ```text oxide/data/RaidableBases/Profiles/Settings.json ``` Use the same base filename for stages that must replace one another. Use different filenames when the target plugin needs several separate data files. What can you automate? DynamicData is not tied to one specific plugin. It is ideal for any data-driven plugin whose JSON files can be updated and reloaded during a wipe, including: - raid profiles and difficulty progression - loot tables and reward pools - kit rotations and tier unlocks - NPC and event profiles - economy or shop data - custom server plugins Build an early-, mid- and late-wipe experience using the plugins you already own. Reliable unattended operation - Automatically detects the current wipe timeline - Supports live stages and restart-only stages - Handles several files and destinations due at the same time - Reloads a target plugin only when it is already loaded - Remembers completed stages after reloads and rescans - Tracks applied content per wipe and source file - Validates JSON before replacing live data - Restores the previous file if the target plugin fails to return after reload - Rate-limits deployments to avoid a burst of plugin reloads - Uses deterministic jitter to spread scheduled work - Detects newly added or edited profiles automatically - Preserves nested data folders - Requires no third-party plugin Preview before you launch Administrators can inspect the timeline from the server console or RCON: ```text dyndata.list dyndata.simulate 2d dyndata.simulate all dyndata.rescan dyndata.pause RaidableBases dyndata.resume RaidableBases ``` `dyndata.simulate all` shows the full planned wipe without applying future stages. Individual target plugins can be paused while files are edited or tested. Access is available to server console, RCON, auth level 1+ administrators, or users granted: ```text dynamicdata.admin ``` Quick installation 1. Copy `DynamicData.cs` into `oxide/plugins/`. 2. Let Oxide compile and load the plugin. 3. Create `oxide/data/DynamicData/<TargetPlugin>/`. 4. Add your valid JSON profiles with their time suffixes. 5. Run `dyndata.simulate all` to verify the timeline. The target folder name must match the target plugin's runtime name and root data folder. For example, the `RaidableBases` folder targets the loaded `RaidableBases` plugin and `oxide/data/RaidableBases/`. Requirements - Rust dedicated server - Oxide/uMod - No mandatory third-party dependencies DynamicData validates JSON syntax, but every plugin has its own data structure. Test new profiles on a development server before using them in production. Why server owners use DynamicData Your server no longer has to feel identical from wipe day to the final evening. Create a controlled progression, give players new reasons to return and remove repetitive file management from your weekly routine. Prepare the timeline once. Let every wipe evolve automatically.

What is it? Zone Command Blocker is a tool which prevents using specific commands (in data folder) in specific zones Permissions: zonecommandblocker.bypass - None of your command will be blocked in any zone zonecommandblocker.clear - Access for the /zcb.clear command Commands: /zcb.clear - Clears/wipes the data folder which contains zones with saved permissions etc.. Features: Zone Command Blocker will make your life easy and will on load take all zones and add them into it's data file where you can just add blocked commands Multiple blocked commands - Supports multiple blocked commands for specific zone Data file: Data of all reports and staff's statistics are being saved into a data file. Path: Your_Server\oxide\data\ZoneCommandBlocker\ZoneCommandBlocker.json Localization: { "CommandBlocked": "This command cannot be used in zones!", "DataFileClear": "Cleared data folder" }

What is it? ZLogs is a comprehensive logging solution for Rust servers, designed to keep admins informed and in control. With a sleek GUI, extensive category coverage, and advanced customization, ZLogs ensures you never miss a crucial server event. Whether it’s player interactions, combat logs, or tool cupboard activity, ZLogs provides detailed insights to maintain transparency and order. Usage Keep your server operations smooth and well-documented with ZLogs. Monitor every key activity with categorized logs, from player connections to combat events. Stay informed with Discord notifications for critical actions like heli spawns or team changes. Effortlessly browse logs with a user-friendly interface featuring search functionality, light/dark mode, and auto-deletion options for old logs. ZLogs puts powerful server management tools right at your fingertips. Permission zlogs.use -- Gives you permission to use the command zlogs.resetall -- Gives you permission to wipe all data files zlogs.heli.spawn -- Gives player a permission to get notified in chat when heli spawns(must be set in config) zlogs.heli.down -- Gives player a permission to get notified in chat when heli gets shot down(must be set in config) Chat Command /zlogs -- Opens the GUI /zlogs.resetall -- Completely wipes all ZLogs datafile (zlogs.resetall permission required) Discord Logging: In config you can set a webhook for each category to have the important info right on your discord Data All the datas are being saved into data folders and each category has it's data file Path to data files: Your_Server\oxide\data\ZLogs Features & some info: I've decided to completely rewrite ZLogs because of some performance mistake I've made and also to add more features and generally make the plugin better. New version brings you also new features like Auto log deletion which can be set in config, more detailed logging, nicer UI, dark and light mode for the UI, search option and more.. Localization: { "Log Explosive": "{0} has used {1}!", "Log Animal": "{0} has killed a {1}", "Log Connect": "{0} has connected to the server", "Log Disconnect": "{0} has disconnected from the server", "Log Command": "{0} has used command: {1}", "Log Chat": "{0} wrote: {1}", "Log Combat": "{0} has killed {1}", "Log Vending": "{0} has bought: {1} for: {2}", "Log HeliSpawn": "Patrol heli has spawned", "Log HeliDeath": "Patrol heli has been destroyed by: {0}", "Log ItemPick": "{0} has picked up a {1}", "Log ItemDrop": "{0} has dropped a {1}", "Log TCPlace": "{0} has placed a TC", "Log TCDestroy": "{0} has destroyed a TC", "Log TCAuth": "{0} has authed a TC", "Log TCDeAuth": "{0} has deauthed from TC", "Log TCClear": "{0} has cleared a TC", "Log TeamCreate": "{0} has created a team", "Log TeamInvite": "{0} has invited {1} to team", "Log TeamReject": "{0} has rejected invite", "Log TeamPromote": "{0} has been promoted to leader", "Log TeamLeave": "{0} has left the team", "Log TeamKick": "{0} has kicked {1} from the team", "Log TeamAccept": "{0} has accepted team invite", "Log TeamDisband": "{0} has disbanded team", "Log TriggerPick": "{0} has picked up {1}+ items over {2} seconds", "Log TriggerDrop": "{0} has dropped {1}+ items over {2} seconds", "Notify HeliSpawn": "A patrol heli has spawned at: {0}", "Notify HeliDown": "A patrol heli has been shot down at: {0} by {1}", "CUI Categories": "Categories", "CUI Settings": "Settings", "CUI Animal": "Animal Logs", "CUI Chat": "Chat Logs", "CUI Combat": "Combat Logs", "CUI Command": "Command Logs", "CUI Connection": "Connection Logs", "CUI Explosive": "Explosive Logs", "CUI Heli": "Heli Logs", "CUI Item": "Item Logs", "CUI Team": "Team Logs", "CUI TC": "Tool Cupboard Logs", "CUI Trigger": "Trigger Logs", "CUI Vending": "Vending Logs", "CUI TargetPlayerInfo": "Target Player Information", "CUI PlayerName": "Player name: {0}", "CUI SteamID": "SteamID: {0}", "CUI Status": "Status: {0}", "CUI StatusAlive": "Alive", "CUI StatusDead": "Dead", "CUI StatusNull": "?", "CUI Ping": "Ping: {0}", "CUI NotConnected": "Not connected", "CUI TPto": "Teleport to", "CUI TPhere": "Teleport here", "CUI AnimalInfo": "Animal Information", "CUI AnimalName": "Animal name: {0}", "CUI AnimalDeathPos": "Animal death pos:\nx: {0}\ny: {1}\nz: {2}", "CUI LogInfo": "Log Information", "CUI LogID": "Log ID: {0}", "CUI LogDate": "Log Date: {0}", "CUI LogRemoveIn": "Log will be removed in: {0}", "CUI ChatInfo": "Chat Information", "CUI ChatType": "Channel type: {0}", "CUI Initiator": "Initiator Information", "CUI Victim": "Victim Information", "CUI Distance": "Distance: {0}m", "CUI Weapon": "Weapon: {0}", "CUI ConnectionInfo": "Connection Information", "CUI ConnectionIp": "IP: {0}", "CUI ConnectionType": "Type: {0}", "CUI ExplosiveInfo": "Explosive Information", "CUI ExplosivePos": "Explosive pos:\nx: {0}\ny: {1}\nz: {2}", "CUI ExplosiveName": "Explosive name: {0}", "CUI HeliInfo": "Heli Information", "CUI HeliPos": "Heli pos:\nx: {0}\ny: {1}\nz: {2}", "CUI HeliAttacker": "Destroyed by: {0}", "CUI ItemInfo": "Item Information", "CUI ItemName": "Item name: {0} x{1}", "CUI ItemPos": "Item pos:\nx: {0}\ny: {1}\nz: {2}", "CUI ItemType": "Type: {0}", "CUI TeamInfo": "Team Information", "CUI TeamType": "Type: {0}", "CUI TeamKicked": "Kicked player: {0}", "CUI TcInfo": "Tool Cupboard Information", "CUI TcType": "Type: {0}", "CUI TcAttacker": "Attacker: {0}", "CUI TcPos": "TC pos:\nx: {0}\ny: {1}\nz: {2}", "CUI TriggerType": "Type: {0}", "CUI DetectTime": "Detect time: {0} seconds", "CUI DetectAmount": "Detect amount: {0} items", "CUI TriggerInfo": "Trigger Information", "CUI VendingItem": "Bought item: {0} x{1}", "CUI VendingPrice": "Price: {0} x{1}", "CUI VendingPos": "Vending pos:\nx: {0}\ny: {1}\nz: {2}", "CUI VendingInfo": "Vending Information", "CUI Search": "Search:", "CUI ColorMode": "Color Mode: {0}" } Configuration: { "Combat logs?": { "WebhookURL": "", "Enabled?": true }, "Item Picks & Drops logs?": { "WebhookURL": "", "Enabled?": true }, "Connection and Disconnection logs?": { "WebhookURL": "", "Enabled?": true }, "Command logs?": { "WebhookURL": "", "Enabled?": true }, "Animal Kills logs?": { "WebhookURL": "", "Enabled?": true }, "Explosives logs?": { "WebhookURL": "", "Enabled?": true }, "Chat logs?": { "WebhookURL": "", "Enabled?": true }, "Heli Logs?": { "WebhookURL": "", "Enabled?": true, "NotifyOnHeliSpawn?": true, "NotifyOnHeliDown?": true }, "Tool Cupboard logs?": { "WebhookURL": "", "Enabled?": true }, "Vending Machine logs?": { "WebhookURL": "", "Enabled?": true }, "Item drop spam detection:": { "Enabled?": true, "WebhookURL": "", "Items needed to detect:": 15, "Time(seconds)": 8.0, "Ignored items(shortnames like: ammo.rifle etc..):": [ "item_shortname", "item_shortname" ] }, "Item pick spam detection:": { "Enabled?": true, "WebhookURL": "", "Items needed to detect:": 15, "Time(seconds)": 8.0, "Ignored items(shortnames like: ammo.rifle etc..):": [ "item_shortname", "item_shortname" ] }, "Team logs?": { "WebhookURL": "", "Enabled?": true }, "Auto-Delete logs after x amount of hours(0 will disable this feature)": 0.0 }

What is it? A nice user-friendly warning system Usage When someone is breaking rules or trolling others just warn them, you can also set a command that will be executed through server console that will get executed upon reachin certain amount of warnings (can be configured in cfg) Permissions warnmenu.use -- Gives you full control to operate the WarnMenu Chat command /warn -- Opens the WarnMenu /warn "Name/SteamID" "Warning reason" -- Warns the specified player with your reason /warnmenu.save -- Force the plugin to write the data from memory to the data file /wmessage <NameOrID | * > <message> - Shows a gametip message (Doesn't count as a warning) to specific player or to all players when you put * instead of the name Data files All Data files can be located at: \oxide\data\WarnMenu\warns There you can find all the warnings for each player Features WarnMenu features * Online Tab - In this tab you can easily select any online player that you want to warn * Search All Tab - Once you open this tab, there you can see all the players and browse in them * Find player Tab - When you click on the button you will be able to search for a specific player using his Name or SteamID Warn Types * CUI-Based - A CUI warning message will pop-up on player's screen when he gets warned * Chat-Based - A chat message will pop-up in player's chat when he gets warned Executable commands * On reaching certain amount of warnings, you can make the server execute a command on a player(configurable in cfg) F.e.: "1": "say {0} just reached 1 warning! SHAME on him!", "3": "kick {0} Kicked for reaching 3 warnings", Localization { "Syntax": "Commands:\n/report (Opens Reporter GUI)", "CUI Online": "Online Players", "CUI Player": "Player: {0}", "CUI SteamID": "SteamID64: {0}", "CUI Warnings": "Warnings: <color=#8f1919>{0}</color>", "CUI NewWarn": "New\nWarning", "CUI WarningID": "Warning ID: {0}", "CUI WarnedBy": "Warned by: {0}", "CUI Date": "Date: {0}", "CUI Reason": "Reason: \n{0}", "CUI Remove": "Remove", "CUI Close": "close", "CUI Warn": "Warn", "CUI WarnAddMenuPlayer": "Warning for\n<color=#d43939>{0}</color>", "CUI SearchAll": "Search All", "CUI SelectPlayer": "Select a player to warn:", "CUI Find": "Find player", "CUI Find2": "Select", "CUI Find3": "Find player:\n(steamID/Name)", "CUI CantFindPlayer": "Couldn't find the player\nsearching argument: {0}", "CUI FoundPlayer": "Found player: {0}", "CUI Refresh": "Refresh", "CantFindPlayer": "Couldn't find that player", "WarnMessage": "Warned: <color=#8f1919>{0}</color>\nReason: {1}", "JoinMessage": "{0} has joined with <color=#8f1919>{1}</color> warnings", "WarnReceive": "You have received a <color=#8f1919>warning</color>\nBy: {0}\nReason: {1}", "CUI WarnReceive": "<color=#8f1919>Warning</color>\nreceived", "CUI WarnReceive2": "By: {0}\nReason: {1}" } Configuration { "Announce on join with warnings?(to admins)": true, "Execute commands on reaching count:": { "Enabled?": true, "(Format: 5 : mute {0}) where 5 is number of warns and {0} is player's id": { "5": "say {0} just reached 5 warnings! SHAME on him!", "7": "example.command {0}", "10": "example.command {0}" } }, "Warn message settings": { "Text-based warn message?": true, "CUI-based warn message?": true, "How long until CUI message gets removed (secs)": 5.0 } }

Simple kill/death ratio counter. User interface is fully customizable, each panel can be disabled. For each screenshot shown there is config file available. Simple customizable KDR UI interface Togglable interface Multi-User custom interface support High Performance Plugin Plug and Play - No dependencies or Linq Got any ideas or questions ? Join the Cobalt Studios Discord @ https://discord.gg/cobaltstudios Player Commands: /hkd or /togglekdr - disables/enables kdr UI /skd or /switchkdr - rotates through multiple custom KDR UIs from the config Args - Optionally use an integer to skip to a specific UI - Example - /skd 2 Admin Commands: /kdrwipe - wipes all kdr data Player Permissions: simplekdr.use - allows use of all player commands simplekdr.hidden - hides the kdr UI when a player logs in or uses the /hkd command Admin Permissions: simplekdr.wipedata - allows the use of /kdrwipe command Credit to M&B Studios the original author of this plugin.

This plugin is an re-write of the free Google Analytics plugin on uMod (https://umod.org/plugins/analytics) that works with GA4. Works with Google Analytics 4 Developer API for use in other plugins Event queueing system to prevent rate-limiting Fast and performant { "Debug": false, // Enables debug logging in the console. "Measurement ID": "", // The measurement ID in your GA dashboard. "API Secret": "", // Your API Secret from your GA dashboard. "Client ID": "My Rust Server", // The server identifier in the events. "Send Data Interval": 3.0, // How often queued events are processed. "Analytics": { "player_join": true, "player_leave": true, "player_pvp_death": true, "player_chat": true, "player_command": true, "report_receive": true, "player_buy_vending": true, "player_kit_redeem": true } // Enable and disable events (you can also add events from other plugins here). If an event isn't in this list, it will be enabled by default } Plugin developers can integrate events into their plugins using our API. API Methods: API_QueueAnalytic(Dictionary<string, Dictionary<string,object>> events, ulong? userId = null) Example of queueing an event: GAPlugin.Call("API_QueueAnalytic", new Dictionary<string, Dictionary<string, object>>() // A list of events. { { "kit_redeem", // The event name. new Dictionary<string, object>() // Event parameters. { { "kit_name", kitName } } } }, userId // The user ID of a player (optional, should be set for events that involve a player). );

What is it? Reporter is the ultimate administration tool designed to enhance player satisfaction and ensure smooth server management. By providing your players with an easy way to report issues and your admins with powerful tools to address them, this plugin bridges the gap between players and staff. With its sleek UI and robust features, Reporter is a must-have for any server owner who values an active, happy community. Usage? Empower your players to report issues effortlessly through a polished and intuitive UI. Admins can manage live reports in real-time, teleport to report creators, claim reports, and resolve them with ease. Ensure transparency and efficiency in server moderation while keeping your playerbase satisfied. Permissions: reporter.use - Basic permission to allow open menu and create New report. reporter.admin - Admin permission to allow view to Live Reports and ability to see/manage pop-up report reporter.sadmin - SuperAdmin permission to allow view to Reports history and see stats of your staff team Commands: /report - Opens the UI menu /report.tp {id} - Teleports you to the creator of specified report /report.claim {id} - Claims specified report /report.finish {id} - Finishes specified report /report.clearall - ! Requires SAdmin permissions and will wipe your data folder - causing to delete all reports and staff's statistics ! Discord logging: Enable/disable and set webhookURL for report claim/create/finish/tp Data file: Data of all reports and staff's statistics are being saved into a data file. Path: Your_Server\oxide\data\Reporter\Reporter.json Config file: You can set here settings for discord notification F.e. Enable/Disable, embed color of the notification, WebhookURL Path: Your_Server\oxide\config\Reporter.json Localization: ["Syntax"] = "Commands:\n/report (Opens Reporter GUI)", ["SyntaxConsole"] = "Can't open GUI in console", ["claimMsg"] = "You have claimed a report\nID: {0}\nBy: {1}", ["finishMsg"] = "You have finished a report with ID: {0}", ["statusUnclaimed"] = "Unclaimed", ["statusClaimed"] = "Claimed", ["statusFinished"] = "Finished", ["reported"] = "Successfully reported", ["fillField"] = "<color=#c93232><--Fill this field</color>", ["noReports"] = "There are not any reports yet", ["noStaff"] = "There are not any staff stats yet", ["playerNotFound"] = "Couldn't find player", ["alreadyClaimed"] = "Report is already claimed", ["labelPAGES"] = "Page {0}/{1}", ["alreadyFinished"] = "This report is already finished", ["CUI newReport"] = "New report", ["CUI liveReport"] = "Live reports", ["CUI historyReport"] = "Reports history", ["CUI staffStats"] = "Staff stats", ["CUI close"] = "Close", ["CUI claim"] = "Claim", ["CUI finish"] = "Finish", ["CUI claimed"] = "Claimed", ["CUI tp"] = "TP", ["CUI next"] = "Next", ["CUI previous"] = "Previous", ["CUI newPopReport"] = "New Report -- ID: {0}", ["CUI reportBy"] = "Reported by <color=#4ccf49>{0}</color>", ["CUI reportedPlayer"] = "Reported player <color=#e00a0a>{0}</color>", ["CUI subject"] = "Subject of report: <color=#e0a00a>{0}</color>", ["CUI liveReportClaimed"] = "<color=#e0a00a>{0}</color> Report: {1}", ["CUI liveReportUnClaimed"] = "<color=#1bc2d1>{0}</color> Report: {1}", ["CUI historyReportFinished"] = "<color=#4ccf49>{0}</color> Report: {1}", ["CUI liveReportClaimedBy"] = "<color=#e0a00a>--Claimed by {0}</color>", ["CUI finishedBy"] = "<color=#4ccf49>--Finished by--\n{0}</color>", ["staffName"] = "Staff's Name", ["staffID"] = "Staff's ID", ["staffFinished"] = "Finished reports", ["Category"] = "Category", ["Message"] = "Message", ["dcCreate"] = "{0} has created report: {1}", ["dcClaim"] = "{0} has claimed report {1} by - {2}", ["dcFinish"] = "{0} has finished report {1} by - {2}", ["dcTp"] = "{0} has teleported to report {1} by - {2}", ["dcCatCreate"] = "Report Create", ["dcCatClaim"] = "Report Claim", ["dcCatFinish"] = "Report Finish", ["dcCatTp"] = "Report TP", Configuration: { "Claim report - discord": { "WebhookURL": "", "Enabled?": true, "Embed Color:": "16538684" }, "Finish report - discord": { "WebhookURL": "", "Enabled?": true, "Embed Color:": "16538684" }, "Create report - discord": { "WebhookURL": "", "Enabled?": true, "Embed Color:": "16538684" }, "TP to report - discord": { "WebhookURL": "", "Enabled?": true, "Embed Color:": "16538684" } }

What is it ZPunisher is a utility for punishing cheaters or bad players a better/funnier way Permissions zpunisher.use -- Gives you access to all commands Commands zpunisher -- Opens a GUI where you can choose a player and then punish him zpunisher {playerNameOrID} -- Opens punish menu with already selected player zpunisher.freeze {playerNameOrID} -- Freezes the player zpunisher.unfreeze {playerNameOrID} -- Unfreezes the player zpunisher.lag {playerNameOrID} -- Start lagging the player zpunisher.stoplag {playerNameOrID} -- Stops lagging the player zpunisher.kill {playerNameOrID} -- Kills the player zpunisher.rocket {playerNameOrID} -- Starts rocketing the player zpunisher.stoprocket {playerNameOrID} -- Stops rocketing the player zpunisher.ignite {playerNameOrID} -- Ignites the player zpunisher.extinguish {playerNameOrID} -- Extinguishes the player zpunisher.stop {playerNameOrID} -- Stops all effects on the player All these commands except the main one with GUI can be used even in console Features Target's info: Target's Name Target's ID Target's IP Address Target's Ping Target's Status (Alive/Dead) Target's XYZ pos with TP button Refresh button Freezer: Once you execute this command on the player he won't be able to move untill you stop the effect Lagger: Once you execute this command on the player his game will start lagging soon untill he won't be able to do anything/untill his game crashes Rocketboy: Once you execute this command on the player an hv rockets are gonna start spawning in him Simple Kill: Once you execute this command on the player he will die Igniter: Once you execute this command a fire will spawn on a player and will follow it untill it disappears Stop All Effects Button: You think that the player had enough? Or have you forgot which effects you gave him? No worries just click the button and all the effects are gone! Localization: { ["noPlayer"] = "There's not such a player", ["stopAllSyntax"] = "Syntax: /zpunisher.stop player", ["stoppedAll"] = "Stopped all effects on: {0}", ["freezeSyntax"] = "Syntax: /zpunisher.freeze player", ["startFreeze"] = "Starting to freeze: {0}", ["unfreezeSyntax"] = "Syntax: /zpunisher.unfreeze player", ["stoppedFreezing"] = "Stopped freezing: {0}", ["lagSyntax"] = "Syntax: /zpunisher.lag player", ["startLag"] = "Starting to lag: {0}", ["stopLagSyntax"] = "Syntax: /zpunisher.stoplag player", ["stoppedLag"] = "Stopped lagging: {0}", ["killSyntax"] = "Syntax: /zpunisher.kill player", ["killMsg"] = "You have killed: {0}", ["rocketSyntax"] = "Syntax: /zpunisher.rocket player", ["startRocket"] = "Started rocketing: {0}", ["stopRocketSyntax"] = "Syntax: /zpunisher.stoprocket player", ["stopRocket"] = "Stopped rocketing: {0}", ["igniteSyntax"] = "Syntax: /zpunisher.ignite player", ["startIgnite"] = "Ignited: {0}", ["extSyntax"] = "Syntax: /zpunisher.extinguish player", ["startExt"] = "Poured water on: {0}", ["infoTitle"] = "Target's Info:", ["infoName"] = "Name: {0}", ["infoID"] = "ID: {0}", ["infoIP"] = "IP Address: {0}", ["infoPing"] = "Ping: {0}ms", ["infoStatusAlive"] = "Status: <color=#52bd36>Alive</color>", ["infoStatusDead"] = "Status: <color=#c70000>Dead</color>", ["infoPos"] = "XYZ Position: {0},{1},{2}", ["infoTPBttn"] = "TP", ["infoRefresh"] = "Refresh", ["choosePl"] = "Choose a player:", ["dsc"] = "..........Description..........", ["freezer"] = "Freezer", ["freezerDsc"] = "Once you execute this command on the player he won't be able to move untill you stop the effect", ["enable"] = "Enable", ["disable"] = "Disable", ["kill"] = "Kill", ["lagger"] = "Lagger", ["lagDsc"] = "Once you execute this command on the player his game will start lagging soon untill he won't be able to do anything/untill his game crashes", ["lagPS"] = "P.S. If you enable this on yourself you must disable it via console - zpunisher.stoplag {Your nick}", ["rocketer"] = "Rocketboy", ["rocketerDsc"] = "Once you execute this command on the player an hv rockets are gonna start spawning in him", ["ignite"] = "Ignite", ["pw"] = "Pour Water", ["killTitle"] = "Simple Kill", ["killDsc"] = "Once you execute this command on the player he will die", ["igniterTitle"] = "Igniter", ["igniterDsc"] = "Once you execute this command a fire will spawn on a player and will follow it untill it disappears", ["stopAllEffects"] = "Stop All Effects!", ["previous"] = "Previous", ["Next"] = "Next" }