Search the Community

For Admin who want to stay on top of decayed entities, to settle disputes or dismiss accusations, or many other uses. Effortlessly keep track of player-owned decayed entities. This plugin logs the essential details and notifies players when their entities decay. ****Note: Twig is always ignored. Features and Benefits: Detailed Logging: Captures essential information about decayed entities, including the owner's SteamID, display name, entity type, grade, location and decay timestamp. Player Notifications: Enable player notifications to keep your community informed about their decaying entities. Whenever a structure owned by a player decays, Decay Logger automatically sends them a notification, ensuring they're aware of what happened. Discord Integration: Seamlessly integrate Decay Logger with your Discord server to request logs containing a player's decayed entities. Whenever a request is made from console or from in-game chat, the plugin can send the logs for a specified player to your designated Discord channel, allowing you and your team to quickly find the logs you want to examine. Easy Configuration: Minimal configuration, define your desired chat and Discord prefixes, set a Discord webhook, adjust time zone settings, and enable or disable player notifications. Efficient Logging: Optimized data storage through an efficient caching system. Stores logs in memory and seamlessly writes them to disk in JSON format when the plugin unloads or the predetermined cache limit is reached. This intelligent approach guarantees minimal performance impact, allowing you to maintain a comprehensive record of decayed entities, regardless of whether your server has 5 players or 500. Permission: decaylogger.admin - Allows the log request to be made in chat. ***Note: Permission is automatically granted to those with Auth 2 and Auth 1 when they join, no need to grant it manually unless you are in-game when you load the plugin for the first time.*** Chat Commands: /dlog <playersteamid> - Requests the logs for the specified player to Discord. /cleardlog - Clears logs manually in chat. Console Commands: dlog <playersteamid> - Requests the logs for the specified player to Discord. cleardlog - Clears logs manually in console. Default Config: { "Chat Prefix": "<color=#32CD32>Decay Logger</color>: ", "Discord Prefix": "Decay Logger: ", "Discord WebHook": "https://support.discord.com/hc/en-us/articles/228383668-Intro-to-Webhooks", "Your time zone hours from UTC (eg: -4 or 4)": -4, "Log optional entities.": true, "Send player notifications when their entity decays.": true, "Clear Logs on wipe.": true }

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" ] } }

C4 Logger is a plugin that documents when and where users placed C4 The file is saved in the logs and the documentation looks like this [07/25/2023 14:54:34] "PlayerName" (Steam64ID) used C4 at position (-440.9276, 11.91947, -19.79667) If you have any questions or problems, join my discord https://discord.gg/D2zTWCEnrN

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

This plugin logs player connections and disconnections. Each player has their own log file corresponding to their Username and Steam ID, which includes the exact time of their connect/disconnect. Log File: The log files are located at "oxide/logs/PlayerLogs" on the server, with each file named after the player's Username and Steam ID.

This plugin allows players to submit feedback to the server owners by using the /feedback command. The feedback is saved into a log file in the oxide logs folder. Permissions: feedback.use - Allows player to submit feedback Commands: /feedback "Feedback Here" - Submit feedback to the log file. Log File: The log file is located at "oxide/logs/feedback.log" on the server.