Search the Community

SmartWarnings simplifies and streamlines your server moderation by providing means to consistently Warn your players for misconduct. Gone are the times when you leave manual notes at sleeping players, for this plugin creates a smooth but intimidating pop-up window displaying clearly to the player what they've done wrong and how to learn from it. From version v2.5.0 you can now extend highly customizable actions to trigger based on your custom warnings. The imagination is the limit! Rule enforcement has never been easier before. Features Easily dispatch warnings to players and clans with a simple chat command /warn cookiemonster "leave the jar alone you bastard" Booom done! /warn clan "C00KiEZ" "no cookiemonsters allowed in the jar!!" Maybe their collective brain power is needed to understand! Announces Warnings in public Global Chat (Enabled by default, can be toggled in config) Give your Players a sense of transparent justice by displaying the dispatched warning to everyone in public. This is beneficial as players will learn what not to do from other's mistakes! Offline Players can receive warnings, no problem! Displays a pop-up window with the warning IMMEDIATELY if they are online, or as soon as the player wakes up from sleep upon connecting. Create custom presets for common violations. Presets can be made for example to reflect the server rules, it can be configured so that your admins can type /warn joe rule1 and it will spell out the entire rule 1 in the warning. Presets can have an Expiration date which will remove the warning, allowing non-repeating offenders to be cleared if they're well behaving in the long term. Presets can have a Warning Point weight which will give them different severity that can influence when to trigger an Automatic Ban (if enabled). Automatically Ban players with X amount of Warnings or Warning Points (Disabled by default, can be toggled in config) With this feature Enabled a player will be Automatically Banned when reaching the configured Warning amount or Warning Points. For example, configure 3 warnings to be max and enable auto ban will ban a player when the third warning has been dispatched. Supports Temporary Autobans (Disabled by default, can be toggled in config) If you're the kind of type that believes in second chances, when configured it bans the player lets them know when they're welcome back! Optional feature: Clear the player's warning when autobanned (True by default), This can conveniently be set to False if you want the player to be instantly auto banned next time a warning is dispatched. Extensive Logging both File based and Discord! Every move is logged in the oxide/logs/SmartWarnings folder so that you can have full traceability. Optional feature: Configure Discord Webhook links to log Warnings and/or Autobans to Discord. Persist Warnings across wipes, when you don't want to be forgiving! Set "Clear all warnings on wipe" to false and warnings will not be cleared when a new wipe is detected. NOTE: This requires that you exclude/do not remove the oxide/data/SmartWarnings_Playerdata.json file, if you're using tools to auto wipe and it gets deleted, so will the warnings. Customizable Branding Set your Server Name and custom Warning Pop-up Icon to make this plugin match your server's style! (NEW in v2.5.0) Transparency of the pop-up window can now be customized in the config! (NEW in v2.5.0) VANILLA SAFE mode: Warning display in Chat instead of GUI pop-up Warnings will be dispatched through chat and freeze the player until they acknowledge the warning. No use of GUI allows it to be vanilla safe! Acknowledge notification is fully customizable! (NEW in v2.5.0) AUTOMOD: Fully customizable command actions on X warning points Define any custom command to be executed at X warning point. This allows you to integrate with any other plugin for example mute, jails or whatever really. For example: set to mute on 2 warning points, kick on 4 warning points, teleport to jail on 6 warning points. NOTE: AutoMod actions are triggered incrementally by total warning points added to the player. This means if you configure Mute on 1 point and Kick on 3 points and give the player a warning worth 4 points, the player will be both kicked and muted. AutoMod feature can conveniently be configured together with AutoBan feature, but keep in mind to set the point/warning thresholds to line up properly. I.e. automod actions should not be on higher point level than autoban, because then player will be banned already before any actions are executed. (NEW in v2.5.5) Battlemetrics Bans & Warnings integration AutoBans will sync with Battlemetrics, duration, reason and note will be added to give context to what banned the player. Warnings will add note to the player in Battlemetrics, so you can easily track their warning history even through the BM console! Warnings will add a flag to the player in Battlemetrics, so you can easily differentiate players in the list who have warnings and not through the BM console! Click here for guide how to set up Battlemetrics integration. (NEW in v2.5.8) MySQL Database Support (allows Multi Server Warning Sync) You can now configure the plugin to use a MySQL Database as its data source. This will allow Warnings to be synced across multiple Rust servers if they are configured towards the same MySQL database. Planned future features Your ideas & feedback? Commands /warn <player name or id> "reason OR preset" Dispatches a warning with a custom reason or preset Requires permission: smartwarnings.admin /warn info <player name or id, leave blank to see yourself> Shows the amount of warnings, warning points and the individual warning details in chat. Requires permission: smartwarnings.admin to see other players. Default permission can only see their own warnings. /warn clear <player name or id> <id or ALL> Clear a specific warning ID by specifying the warning number, or specify ALL to clear all player warnings. (NEW in v2.5.0) Requires elevated permission: smartwarnings.admin.canclear /warn clan <clan tag> "reason OR preset" Dispatches a warning with a custom reason or preset to an entire clan (Requires Clans plugin) Requires permission: smartwarnings.admin /warn unfreezeall Unfreezes all players who are currently frozen due to not acknowledging any warnings, really only needs to be used in any emergency scenario where the player would not be unfrozen normally (Please report these scenarios, this command is purely proactive and will be removed when its not needed anymore) Requires permission: smartwarnings.admin Configuration { "Warning Presets": { "spam": { "Reason": "§1 - Spamming", "Points": 1, "ExpirationDays": 3.0 }, "toxic": { "Reason": "§2 - Toxic behaviour", "Points": 2, "ExpirationDays": 7.0 }, "sign": { "Reason": "§3 - Inappropriate signage", "Points": 2, "ExpirationDays": 7.0 }, "grief": { "Reason": "§4 - Griefing", "Points": 4, "ExpirationDays": 7.0 }, "group": { "Reason": "§5 - Group Limit violation", "Points": 5, "ExpirationDays": 7.0 } }, "System Settings": { "Max Warnings": 5, "Default Warning Expiration time (Days)": 7, "Announce Warnings in Global Chat": true, "Show players who issued the warning": true, "Server Name": "MyRustServer", "Clear all Warnings on Server Wipe": true, "Use MySQL database": false, "Warning Popup - GUI Enable - Set to false to use only chat (SAFE FOR VANILLA SERVER)": false, "Warning Popup - GUI Icon": "https://i.imgur.com/oImKq4X.png", "Warning Popup - GUI Opacity": 0.85, "Optional: Send anonymous analytics data about plugin usage": true, "Config Version": { "Major": 2, "Minor": 5, "Patch": 8 } }, "MySQL Database Settings": { "MySQL Host": "", "Port": 3306, "Database": "", "Username": "", "Password": "" }, "Battlemetrics Settings": { "API Token": "", "Organization ID": "", "Server ID": "", "Banlist ID": "" }, "Autoban Settings": { "How many points until automatic ban (Set 0 for Disable)": 0, "How many warnings until automatic ban (Set 0 for Disable, Recommended: Same as Max Warnings)": 0, "How long to ban in minutes (Set 0 for Permanent)": 2880, "Clear the players Warnings on AutoBan (Default: True)": true }, "Discord Settings": { "Webhook URL - Post Warnings to Discord (Leave blank to Disable)": "", "Webhook URL - Post Autobans to Discord (Leave blank to Disable)": "" }, "AutoMod Settings": { "Mute on 2 warning points": { "PointTrigger": 2, "ExecuteCommand": "mute {0} {1}", "ClearPointsOnTrigger": false }, "Kick on 4 warning points": { "PointTrigger": 4, "ExecuteCommand": "kick {0} {1}", "ClearPointsOnTrigger": true } } } Language Configuration The plugin allows a comprehensive customization of all text output for your needs. Edit the oxide/lang/en/SmartWarnings.json { "NO_PERM": "You don't have permission to use this command.", "NO_MATCH": "Could not find a match for player name or steamid", "GUI_BUTTON_ACKNOWLEDGE_WARNING": "I ACKNOWLEDGE THIS WARNING AND WILL FOLLOW THE RULES", "GUI_HEADER": "You have received a warning", "GUI_ISSUEDBY": "<color=#FFFFFF>Warning issued by {0} at {1}</color>", "GUI_ISSUEDAT": "<color=#FFFFFF>Warning issued at {0}</color>", "GUI_WARNING_TEXT": "<color=#cc0000>Repeated violations may lead to temporary or permanent banishment from this server.</color>\n\n<color=#d9d9d9>You should review the server rules immediately by typing /info in chat and clicking on the RULES tab.\nTo remove this pop-up, acknowledge this warning by clicking the button below.\nIf you feel this was an incorrect warning please reach out to our Staff via Discord.</color>", "CHAT_ACKNOWLEDGE_TEXT": "<color=#00FF00><size=12>Warning Acknowledged: You're now unfrozen and free to go.\n</size></color><size=9>Please review the server rules by typing /info in chat to avoid getting warned in the future.</color>\n\nIf you feel this was an incorrect warning please reach out to our Staff via Discord.</size>", "ANNOUNCE_WARNING_TEXT": "<color=#DC143C>{0} has been warned!\nFurther violations will lead to disciplinary action.</color>\n<color=#A9A9A9>Reason: {1}", "ANNOUNCE_WARNING_ISSUEDBY": "\n\n<size=10>Warning Issued by: {0}</size></color>", "REASON": "REASON", "AUTOBAN_PERMANENT_MESSAGE": "AutoBanned: You were permanently banned due to reaching max warnings.", "AUTOBAN_TEMPORARY_MESSAGE": "AutoBanned: You are banned until {0} due to reaching max warnings." } For example to change is the detailed warning text: You can edit the GUI_WARNING_TEXT row in the language file. Dependencies & Integrations Requires: DiscordMessages for Discord webhook functionality. Integrates with EnhancedBanSystem, autoban feature will detect if the plugin is installed and issue a ban with it, if not it will use the native Rust ban functionality. OPTIONAL: Plugin Usage Analytics The plugin optionally sends analytics about your server (Oxide version, Plugin version, Plugin configuration, Server Name, OwnerID and ModeratorID) to gauge usage of the plugin and to improve support. You can toggle this feature in the configuration.

What is it? This is a logger for multiple categories with nice gui. Usage If you want to know what's going on your server this logger will surely help you achieve that. Permission zlogs.use -- Gives you permission to use the command 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 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 been trying to aim for the most important data logging, but this definitelly isn't FINAL version of plugin in future I am planning on making the GUI better - by clicking on log displaying menu, ability to wipe category from in-game etc... Every category can be disabled in config and plugin won't display the logs in menu and won't log for the disabled category anymore. By clicking on a certain log it teleports you to the position where it happend(admin permissions needed to use teleport command!), by using the log teleport it also writes it into command category where you can see it was ZLog teleport. I've been testing any performance issues and tried to fix most of them, also by distributing this plugin to other server owners, and with maximum about 4,5k+ logs in 1 category everything seemed fine. I am also OPEN to any suggestions for more categories! Localization: { "NoPerms": "You don't have permission to use this!", "pdataSucc": "Successfully loaded playerDeaths.json", "pdataFail": "Failed to load playerDeaths.json. Creating new playerDeaths.json", "itemSucc": "Successfully loaded itemDropsPicks.json", "itemFail": "Failed to load itemDropsPicks.json. Creating new itemDropsPicks.json", "connSucc": "Successfully loaded playerConns.json", "connFail": "Failed to load playerConns.json. Creating new playerConns.json", "commandSucc": "Successfully loaded commands.json", "commandFail": "Failed to load commands.json. Creating new commands.json", "animalSucc": "Successfully loaded animalKills.json", "animalFail": "Failed to load animalKills.json. Creating new animalKills.json", "exploSucc": "Successfully loaded explosives.json", "exploFail": "Failed to load explosives.json. Creating new explosives.json", "chatSucc": "Successfully loaded chat.json", "chatFail": "Failed to load chat.json. Creating new chat.json", "heliSucc": "Successfully loaded heli.json", "heliFail": "Failed to load heli.json. Creating new heli.json", "tcSucc": "Successfully loaded tc.json", "tcFail": "Failed to load tc.json. Creating new tc.json", "npcSucc": "Successfully loaded npc.json", "npcFail": "Failed to load npc.json. Creating new npc.json", "triggerSucc": "Successfully loaded triggers.json", "triggerFail": "Failed to load triggers.json. Creating new triggers.json", "vendingSucc": "Successfully loaded vending.json", "vendingFail": "Failed to load vending.json. Creating new vending.json", "newJson": "New .json was created recently, please wait few seconds.", "logsDisabled": "These logs are disabled in the config!", "noLogs": "There are no logs to be displayed yet!", "labelPAGES": "Page {0} / {1}", "bttnPDATA": "Player Deaths", "bttnITEMS": "Items Picks & Drops", "bttnCONNS": "Connections & Disconnections", "bttnCOMMANDS": "Commands", "bttnANIMALS": "Animal Kills", "bttnEXPLO": "Explosives", "bttnCHAT": "Chat", "bttnHELI": "Heli", "bttnTC": "Tool Cupboard", "bttnNPC": "NPC Kills", "bttnTriggers": "Triggers/Warnings", "bttnVending": "Vending Machines", "pdeaths": "{0} {1} was killed by {2} - {3}", "pdeaths2": "{0} {1} was killed by {2}", "itemPickup": "{0} {1} picked up {2}(x{3})", "itemCollect": "{0} {1} collected up {2}({3} x{4})", "itemDrop": "{0} {1} dropped {2}(x{3})", "playerConn": "{0} {1} has connected", "playerDis": "{0} {1} has disconnected({2})", "playerCommand": "{0} {1} has used {2}", "playerKillAnimal": "{0} {1} has killed a {2} with {3}", "exploUse": "{0} {1} has thrown {2}", "playerChat": "{0} [{1} Chat] {2} said: {3}", "heliSpawn": "{0} a patrol heli has spawned at: {1}", "heliDown": "{0} a patrol heli has been shot down at: {1} by {3}", "tcSpawn": "{0} {1} has placed TC at: {2}", "tcDestroyed": "{0} {1} has destroyed TC at: {2}", "tcAuth": "{0} {1} has authorized TC at: {2}", "tcClear": "{0} {1} has cleared TC authorizations at: {2}", "tcDeAuth": "{0} {1} has deauthorized TC at: {2}", "npckill": "{0} {1} has killed {2}", "itemSpam": "{0} {1} has dropped {2} items in less than {3} seconds", "itemPickSpam": "{0} {1} has picked {2} items in less than {3} seconds", "vendingBuy": "{0} {1} has bought {2}(x{3}) for {4}(x{5})" } Configuration: { "Player Deaths 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 }, "NPC Kills logs?": { "WebhookURL": "", "Enabled?": true }, "Vending Machine logs?": { "WebhookURL": "", "Enabled?": true }, "Item drop spam detection:": { "Enabled?": true, "WebhookURL": "", "Items needed to detect:": 5, "Time(seconds)": 8.0, "Ignored items(shortnames like: ammo.rifle etc..):": [ "wood", "horsedung" ] }, "Item pick spam detection:": { "Enabled?": true, "WebhookURL": "", "Items needed to detect:": 5, "Time(seconds)": 8.0, "Ignored items(shortnames like: ammo.rifle etc..):": [ "wood", "horsedung" ] } }

Friends Plugin for Rust Server "Friends" is a robust and flexible plugin designed to enhance the in-game friends system in Rust. It will help streamline the interaction between friends, simplify the process of authorization, and access to important game elements, and manage damage between friends. Key Features: Damage Control: An integrated feature of damage blocking among friends helps prevent accidental damage. This feature can be easily enabled or disabled by command. Enhanced Friends Authorization System: The plugin allows activating friends' authorization for a wide range of elements, including: Turrets SAM site Code locks Key locks Cupboards Upon removal from the friends' list, the player will automatically be deauthorized from all the listed elements. Remote Friend Invitation: With a special command, you can invite a player to be friends, even from afar. Authorization Settings Flexibility: Choose between two authorization methods for code locks - guest authorization ("guestPlayers") or full authorization ("whitelistPlayers"). Compatibility and Optimization: The "Friends" plugin is optimized for maximum performance and is compatible with many other plugins. Extensive API: The plugin offers a comprehensive API for developers, providing flexibility and the possibility of further customization. Detailed Logging System: "Friends" includes a logging system, providing transparency and control over activities. Optimize your gameplay with the "Friends" plugin for Rust server. It will help improve your gaming experience, simplify interactions with friends, and make your server safer and more manageable. Commands: /team - Additional info /team invite/add <Nickname> /team ff - Friendly fire Default Configuration: { "Chat commands": [ "team", "ff", "friend" ], "Maximum number of friends": 3, "Time to accept team invite (in seconds)": 20.0, "Enable friend authorization for turrets?": true, "Enable friend authorization for SAM sites?": true, "Enable friend authorization for code locks?": true, "Enable friend authorization for key locks?": true, "Enable friend authorization for cupboards?": true, "Authorization method for code locks (guestPlayers - guest authorization, whitelistPlayers - full authorization)": "guestPlayers", "Enable logging system ?": false, "Chat prefix (IQChat)": "<color=#5cd6skykey>[Friends]</color>\n" } API for Developers HasFriend(ulong playerId, ulong friendId) //Checks if the specified user is a friend of the player. HasFriends(string playerS, string friendS) //Checks if the player has friends by their string identifiers. IsFriend(ulong playerId, ulong friendId) //Checks if the specified user is a friend of the player. AreFriends(ulong playerId, ulong friendId) //Checks if the specified players are friends. AreFriends(string playerS, string friendS) //Checks if the specified players are friends by their string identifiers. IsFriends(string playerS, string friendS) //Checks if the player has friends by their string identifiers. GetFriends(ulong playerId) //Returns the player's friends list. GetFriendList(string playerS) //Returns the player's friends list by the string identifier. GetFriends(string playerS) //Returns the player's friends list by the string identifier. IsFriendOf(ulong playerId) //Returns a list of players who are friends of the specified player. IsFriendOf(string playerS) //Returns a list of players who are friends of the specified player by the string identifier. GetFriendList(ulong playerId) //Returns the friends list of the specified player.

This is an option addon to ULTIMATE RCON+! This enabled more logging features for the bot still providing the most optimal performance over things that use the Discord DLL. FEATURES - Server feedback UI - UI to edit all the config values - Logging for - Cargo - Cargo Plane - Brad - Ch47 - Heli - Groups added and removed from players - Perms added and removed from players - More advanced kill logs and ability to disabled NPC, Animal, or player kills Permission: ultimaterconplus.admin Command: /urplus Need support or want updates about what is coming to the bot? Join the support discord here https://discord.gg/RVePam7pd7

IMRG plugins are currently not for sale. Additionally the "IMR Tools Package" are (or soon to be) unlisted. Those who've already bought our plugins are welcome to still submit support request if necessary. Once we've more time to allocate to Codefling plugins will be relisted again as well as more added. Advanced Combat Logging is a plugin that improves upon the combatlog feature in Rust for both players and admins in a number of key ways. For reference, combatlog is a command players use regularly to see the "combat logs" of their fights, and this plugin takes that many steps further by upgrading the information shown to display the actual steamID and player name of the players involved in the fight (which the normal combat log doesn't show), in addition to allowing customization of the log with such things like the amount of combat interactions or how long ago the combat happened, who it is or isn't shown to, and which type of interactions to log (players, animals, scientists, etc). For admins, it also creates fully customizable persistent server log files with no performance impact with records of combat logs of fights that took place on the server so they can be reviewed later for balance, hacker/scripter investigation, seeing what you missed, and much more! Features • Improves upon the existing combatlog feature for both players and admins • Takes the guesswork out of the logs to include actual steamID and player name for complete accuracy rather than vanilla combatlog which shows neither • Creates customizable log files for server owners so they can conveniently review all combat logs on their server even when they're not actively around and using the command • Through review of the generated log files, allows admins to compare and contrast logs at their own pace to look for patterns of potential hackers, scripters, other foul play, or other things • VIP Ready to allow specific players or groups of players to see better combat logs than normal players and many other options • Lets admins choose which type of combatlogs will be recorded per permission group by specifying the short prefab names (for example, players, specific animals, specific scientists, etc) as well as other possibilities • Can block all or specific players from using the combatlog feature as well if so desired • Great performance • Highly customizable Depends On IMR Tools Package: https://codefling.com/tools/imr-tools-package Always make sure you have the IMR Tools Package installed first when running any plugins by IMR Games. Installation - Make sure you have the IMR Tools Package installed, as explained above. - Put this plugin in your oxide plugins folder. - It will generate a config and lang file. - When in use, will also generate log files in the standard oxide logs directory. - Customize and enjoy! Console Commands combatlog - Brings up the custom combat log in the console combatlog steamid - Brings up the custom combat log in the console for that specific player (admin only) Permissions All permissions in this plugin are completely customizable in the config file. There can be as little or as many permission groups as you like depending on what you want to do. The only requirement is that the beginning of the permission use the plugin name which is imrgadvancedcombatlogging. Permission groups also follow a "priority" system, with the permissions listed first taking higher priority if a player happens to have multiple. Included in the default config are the following permission group examples just to demonstrate a few things you can do: - Example 1: Players with this permission cannot use the combatlog command. Useful if you want to block specific players or even all non-VIP players from using it - Example 2: Permission for admins that unlocks all features of the plugin - Example 3: VIP permission for players with upgraded combatlog features plus the ability to use combatlog - Example 4: Permission that lets players use the command with basic features - Example 5: Permission that lets players only see combatlogs related to animals These are just examples, but the plugin can be used in many ways! Config { "File Log Settings": { "Only Log If Player Has Been Hurt By Another Player Recently": false, //Limits combat logs to only situations where players were hurt by other players. "Max Combat Lines": 60, //Maximum line entries of combat interactions per log to show. "Max Combat Time Lines Seconds": 600.0, //Maximum time in seconds to show a combat interaction, ending in the death of a player and going back that many seconds of combat interactions. "Show Improved Identifiers": true, //Upgrade the standard vanilla combat log with steamID and actual player names. This makes it possible to identify each target involved in combat specifically for a much clearer picture of who was doing what. "Prefab Short Name Whitelist": [ //Short prefab names for which types of combat interactions to log. For example, if including only player, then only PVP interactions will be logged. If adding animal shortnames, then PVP and animal combat interactions will be logged. If this is left empty, then every combat interaction will be logged, including players, animals, scientists, etc. "player" ] }, "Console / RCON Settings": { "Block Combat Log Command": false, //Prevent anyone from using the combatlog command via Console/RCON. "Line Delay Seconds": 0.0, //How many seconds must pass after a combat interaction has occurred before it will show up with the command. "Max Combat Lines": 9999999, //Example of pretty much unlimited combat interactions being visible per combat log. "Max Combat Time Lines Seconds": 9999999.0, //Example of pretty much any length of combat interactions being visible per combat log. "Show Improved Identifiers": true, "Prefab Short Name Whitelist": [] }, "Settings (By Permission)": { "imrgadvancedcombatlogging.blocked": { //Permissions that do different things based on the configuration settings in each permission group. Server owners can make as many permission groups as they like with whatever custom settings they prefer. "Block Combat Log Command": true, "Line Delay Seconds": 0.0, "Max Combat Lines": 0, "Max Combat Time Lines Seconds": 0.0, "Show Improved Identifiers": false, "Prefab Short Name Whitelist": [] }, "imrgadvancedcombatlogging.admin": { "Block Combat Log Command": false, "Line Delay Seconds": 0.0, "Max Combat Lines": 999999, "Max Combat Time Lines Seconds": 9999999.0, "Show Improved Identifiers": true, "Prefab Short Name Whitelist": [] }, "imrgadvancedcombatlogging.vip": { "Block Combat Log Command": false, "Line Delay Seconds": 0.0, "Max Combat Lines": 60, "Max Combat Time Lines Seconds": 600.0, "Show Improved Identifiers": true, "Prefab Short Name Whitelist": [] }, "imrgadvancedcombatlogging.normal": { "Block Combat Log Command": false, "Line Delay Seconds": 10.0, "Max Combat Lines": 30, "Max Combat Time Lines Seconds": 120.0, "Show Improved Identifiers": false, "Prefab Short Name Whitelist": [ "player" ] }, "imrgadvancedcombatlogging.animals": { "Block Combat Log Command": false, "Line Delay Seconds": 10.0, "Max Combat Lines": 50, "Max Combat Time Lines Seconds": 120.0, "Show Improved Identifiers": false, "Prefab Short Name Whitelist": [ "chicken", "stag", "boar", "wolf", "bear", "polarbear", "simpleshark" ] } } } Lang { "Blocked": "You don't have permission to use combatlog" //Message players will receive if they try to use the combatlog command and they're either specifically blocked from using it or they don't have permission to use it. }

This plugin is very simple. It logs to discord and to console items on a watch list that are related to making anything explosive related. This can include sulfur, all the way up to C4. If you don't want to use Discord, you can go ahead and just leave the discord webhook field alone. Default Config: { "Discord Webhook": "https://support.discord.com/hc/en-us/articles/228383668-Intro-to-Webhooks", "Enable Debug?": false, "List of items to watch for and log": [ "explosives", "ammo.rocket.hv", "ammo.rocket.fire", "ammo.rocket.mlrs", "ammo.rocket.basic", "rocket.launcher", "ammo.rocket.sam", "ammo.rocket.smoke", "ammo.rifle.explosive", "explosive.satchel", "explosive.timed", "sulfur", "sulfur.ore" ], "List of prefabs to watch (DO NOT CHANGE!)": [ "autoturret_deployed", "coffinstorage", "small_stash_deployed", "furnace", "furnace.large", "box.wooden.large", "woodbox_deployed", "locker.deployed", "dropbox.deployed", "vendingmachine.deployed", "researchtable_deployed", "repairbench_deployed", "mixingtable.deployed" ] }

What is it? This is a simple plugin, that lets you monitor all bed and bag renames. Usage People are changing bag names to racist or inappropriate names? With this plugin you can take care of these people by checking who did it! Just install & punish! Discord WebHook Just create a webhook for your channel, paste it into the config, reload the plugin and it's done! Localization {0} - X Y Z Position {1} - Player name {2} - Player ID {3} - Old Bed/Bag name {4} - New Bed/Bag name { "SleepingBagRename": "{0} {1}({2}) renamed sleeping bag from {3} to {4}", "BedRename": "{0} {1} ({2}) renamed bed from {3} to {4}" } Config { "Discord webhook url": "Your discord webhook URL", "log to discord?": true } Where's the log folder? Since the 1st log it should automatically create a folder and you can find logs here: oxide/logs/BedNameLogs/bednamelogs_renames-xxxx-xx-xx.txt