Mano4ka's Wishlist

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

Rust Wipe Bot
Rust Wipe Bot is a tool that automates the process of wiping your Rust server.  
It works by using the Pterodactyl or Pelican panels' Schedules feature to send commands to the bot,  which then triggers different actions on your server.  
It is also possible to send commands to the bot directly in the command prompt on the panel page.
The bot is compatible with any Pterodactyl or Pelican Rust egg, as it utilizes the panel API to perform actions  such as removing files, sending in-game messages, or executing commands on your Rust server.
Know working Rust eggs:
Rust Autowipe Rust All-in-One Pterodactyl Egg (Oxide/Carbon) One of the advantages of the bot is that it doesn't need to be restarted when you make changes to the configuration files.  
The files are loaded dynamically when a command is called. Additionally, the bot is capable of handling multiple servers  and commands simultaneously, thanks to its ability to run each command in its own thread.
The supported configuration file formats for the bot are .yml or .yaml and is located in the config folder, where you also can find a example.
It is strongly recommended to create one configuration file for each wipe schedule.
 
Available commands:
command <config file> <command to execute> - Execute a command on the server.   message <config file> <message to send>     - Send a in-game message to the server, useful for notifying players about an upcoming wipe. wipe <config file>                         - Triggers a server wipe. quit                                       - Shutdown the bot.  
How to use the bot:
1. Make a copy or edit the example configuration file inside the config folder to meet your needs.
2. Go to Schedules and create a new schedule.
3. Add a new task with the action "Send command" and add a command to the payload:
    command <name of config file> o.reload *
   or
     message <name of config file> Server will wipe in 10 minutes.
   or
    wipe <name of config file>
   Note: If more than one task is provided within the scheduler don't forget to set the time offset.
 
How to install:
1. Create a new server using the provided egg called "egg-rust-wipe-bot.json".
2. Upload the "rustwipebot.zip" archive to the server's Files section. Once uploaded, you can unarchive the zip file or trigger a reinstall in the server's Settings section.
3. Navigate to the Files section and modify the .ENV file with the panel url and a client API key.
    Note: You can create a client API key under your profile on the panel website, Account Settings -> API Credentials.
4. Start the bot. During startup, it will automatically install all the necessary dependencies.

Example of a configuration file.
# Server identifier (abbreviated UUID) server_id: abcd1234 # If the server do not shutdown properly by any reason, the bot will attempt to kill the server process. force_kill: false # Set to true if you want to reinstall the server. This should not be used unless you want to reinstall the server for any reason. reinstall_server: false # Remove specified files or folders. Supports wildcards. files_to_remove: [ server/rust/player.deaths.*.db, server/rust/player.deaths.*.db-wal, server/rust/player.identities.*.db, server/rust/player.identities.*.db-wal, server/rust/player.states.*.db, server/rust/player.states.*.db-wal, server/rust/player.blueprints.5.db, server/rust/player.blueprints.5.db-wal, server/rust/proceduralmap.*.*.*.map, server/rust/proceduralmap.*.*.*.sav, server/rust/proceduralmap.*.*.*.sav.*, server/rust/sv.files.*.db, server/rust/sv.files.*.db-wal, oxide/data/Kits_Data.json, oxide/data/NTeleportationHome.json, oxide/logs/*.log, oxide/logs/*.txt, ] # Set the server seed(s) and size to use for the world. # Add "random" as a seed to generate a random seed between 100000 and 999999, or a custom range to use like 3000-4000. # If multiple seeds are provided, the bot will randomly choose one, but it will never use the same seed unless only one seed is provided. world_seeds: - seed: 153525773 size: 1000 - seed: 3000-4000 size: 1500 - seed: random size: 2000 # Custom world URL(s) to download and install. This overrides the world seed and size. # If multiple map URLs are provided, the bot will randomly choose one, but it will never use the same map unless only one map URL is provided. custom_world_urls: [] # Set custom commands to run in the wipe command before the server stops and after the server starts. run_commands: before: [o.reload *] after: [ kit reset, ecowipe, ]  

An advanced ticket bot made with simplicity it brings to users both in use within discord and installation, The bot runs on the latest version of Discord.js and is fully customizable with 50+ features and no watermarks!
Elevate your server's support experience with our professional and advanced ticket system. Your users can seamlessly create tailored support tickets from a variety of categories, while you enjoy the ease of managing their needs through our feature-rich and user-friendly bot. Simplify support, elevate satisfaction

Features:
- Buttons, Modals, Menus - Custom Emojis - Multiple Categories - Logs of everything   - Notify if ticket creators leave - Support roles for each category - Pin Tickets - Custom channel names - Claiming System - Auto responses - Web dashboard (addon) - Ticket Review System - Archive Tickets - Questions System (per category) - Setup working hours - Fully Customizable - Self Hosted - Paypal/stripe/crypto invoices - Easily translatable - Advanced suggestions - MongoDB - Custom Commands - Addons System - Rename Tickets - Statistics - Blacklist users/roles - 1-8 Categories - Discord Timestamps - Discord Modals - Ticket Required Roles - Transcripts (HTML, TXT) - View Transcripts online  
Discord Server:
https://discord.gg/plexdev

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 }