Search the Community

Allows you to restrict certain commands and actions for admins, monitor their activities, and prevent admin abuse. Features Command Blocking: Prevents specified commands from being executed by certain admins. Action Blocking: Disables interactions like looting, building, or interacting with vehicles, cupboards, and more. Team Management: Manage the admins team and their permissions. Anti-Abuse: Detects abusive behavior with configurable actions such as kick or ban. Action Logging: Logs movements and interactions. Permissions adminrestrictions.limitactions - limit the admin actions. adminrestrictions.ignore - ignores a specific admin. Configuration { "Commands Block": { "Enable commands blocking": false, "Commands list": [ "server.stop", "server.hostname", "server.description", "server.restart", "server.quit", "server.url", "kickall", "ownerid", "moderatorid" ], "Log without blocking": false, "Print to Console": false, "Log to File": false }, "Actions Block": { "Enable actions blocking": false, "Actions": { "Damage": { "Block Action": false, "Enable Discord Logging": false }, "Loot": { "Block Action": false, "Enable Discord Logging": false }, "Pickups": { "Block Action": false, "Enable Discord Logging": false }, "Building": { "Block Action": false, "Enable Discord Logging": false }, "Player Assist": { "Block Action": false, "Enable Discord Logging": false }, "Gathering/Farming": { "Block Action": false, "Enable Discord Logging": false }, "Locked Entity Usage": { "Block Action": false, "Enable Discord Logging": false }, "Cupboard Interaction": { "Block Action": false, "Enable Discord Logging": false }, "Codelock Interaction": { "Block Action": false, "Enable Discord Logging": false }, "Stash Interaction": { "Block Action": false, "Enable Discord Logging": false }, "Vehicles Interaction": { "Block Action": false, "Enable Discord Logging": false }, "Turret Interaction": { "Block Action": false, "Enable Discord Logging": false }, "Hack Locked Crate": { "Block Action": false, "Enable Discord Logging": false }, "Bed/Sleeping Bag Renaming": { "Block Action": false, "Enable Discord Logging": false }, "Oven Toggle": { "Block Action": false, "Enable Discord Logging": false }, "Recycler Toggle": { "Block Action": false, "Enable Discord Logging": false }, "Mixing Table Toggle": { "Block Action": false, "Enable Discord Logging": false }, "Diesel Engine Interaction": { "Block Action": false, "Enable Discord Logging": false }, "Excavator Interaction": { "Block Action": false, "Enable Discord Logging": false }, "Vending Machine Interaction": { "Block Action": false, "Enable Discord Logging": false }, "Entities Target": false, "Lift Usage": { "Block Action": false, "Enable Discord Logging": false }, "Buttons Interaction": { "Block Action": false, "Enable Discord Logging": false }, "Switches Interaction": { "Block Action": false, "Enable Discord Logging": false }, "Explosives Usage": { "Block Action": false, "Enable Discord Logging": false }, "Ent Kill": { "Block Action": false, "Enable Discord Logging": false }, "Ent Lock": { "Block Action": false, "Enable Discord Logging": false }, "Ent Unlock": { "Block Action": false, "Enable Discord Logging": false } }, "Print to Console": false, "Log to File": false }, "Team Management": { "Enable team management": false, "Force admins to be in one team (overwrites all the below)": false, "Team Permissions": { "Can create team": false, "Can leave team": false, "Can invite to team": false, "Can be invited to team": false } }, "Anti Abuse": { "Enable anti-abuse": false, "Action on Detection (0 = None, 1 = Kick, 2 = Ban)": 0, "Teleport to building block zone": false, "Teleport to cargo": false, "Teleport Damage": false, "Print to Console": false, "Log to File": false }, "Actions Logger": { "Enable action logger": false, "Actions": { "Movements": false, "Door Interactions": { "Door Opened": false, "Door Closed": false, "Door Knocked": false }, "Box Looting": { "Loot Started": false, "Loot Ended": false, "Item Added": false, "Item Looted": false } }, "Ignore player-owned entities": false, "Print to Console": false, "Log to File": false }, "Discord Logging": { "Enable discord logging": false, "Webhook": "" } } Note: Anti-Abuse will disable damage and teleport the player back to his previous location upon detection.

About The Fun Gun Unleash chaos and fun by shooting vehicles out of the snowball gun! Prerequisites A snowball gun in hand (no ammo required). Permissions TheFunGun.CarGun.Use TheFunGun.RhibGun.Use TheFunGun.BoatGun.Use TheFunGun.SnowGun.Use TheFunGun.RandGun.Use TheFunGun.SharkGun.Use TheFunGun.TugGun.Use TheFunGun.MiniGun.Use TheFunGun.SideCar.Use TheFunGun.Pedal.Use TheFunGun.Motor.Use TheFunGun.BypassCooldown Chat Commands /cargun - Enables the car gun (sedan). /rhibgun - Enables the RHIB gun. /boatgun - Enables the rowboat gun. /snowgun - Enables the snowmobile gun. /sharkgun - Enables the shark gun (shoots shark corpses). /minigun - Enables the minicopter gun. /sidecar - Enables the motorbike with a sidecar. /motor - Enables the motorbike without a sidecar. /tuggun - Enables the tugboat gun. /pedalgun - Enables the pedal bike gun. /randgun - Enables the random gun (spawns random vehicles). Caveats Be cautious when setting the despawn timer in the configuration. High values may result in vehicles staying on the server longer, which can lead to spam or server lag. A low despawn timer is recommended. Configuration { "Despawn Timer": 5.0, "Velocity": 75.0, "Cooldown": } Localization { "randGunEnable": "<color=#ffc34d>TheFunGun</color>: Random Gun <color=#36802d>Enabled</color>", "randGunDisable": "<color=#ffc34d>TheFunGun</color>: Random Gun <color=#ff6666>Disabled</color>", "noPermission": "<color=#ffc34d>TheFunGun</color>: You do not have permission to use this command", "Cooldown": "<color=#ffc34d>TheFunGun</color>: You are on a {0} second cooldown." } Customizable localization entries for each gun are available in the config file. Special Thanks A huge thank you to unboxingman for assisting in the development of this plugin! Support Dark Side Developement

Video : Showcase Video Features : - Randomized loot respawn intervals, configurable for each monument. Example: "launch site": "5-10" (in seconds) - Default respawn time is set between 30-60 minutes but can be fully adjusted through the configuration. - Automatically removes monuments that no longer exist after a server wipe, keeping the configuration clean and up-to-date. Supported Crates : Supported Monuments : All Game Monuments Additional Settings : "Direct container removal without dropping loot": false, "Enable When Player Dont Finish Looting Containers Will Drop Loot On Ground": true,

Adds re-spawnable vehicles with command. About Vehicle Spawnper Plus With this plugin, you can: • Define spawn points for different vehicles anywhere in your server's world. • Set custom intervals for spawning vehicles, allowing you to control the frequency of vehicle respawns. • Specify random interval for spawning vehicles, adding an element of unpredictability to your server's spawnpoints. Whether you're looking to establish vehicle spawn zones, simulate dynamic vehicle distribution, or simply enhance the gameplay experience on your Rust server, this plugin gives you the flexibility and control to do so with ease. Commands (ONLY ADMIN); • /addvehiclespawn <name> <x> <y> <z> <vehicleName> <interval> ► You can create a spawn point with static time and vehicle. • /addvehiclespawnr <name> <x> <y> <z> <vehicleName> <intervalMin> <intervalMax> ► You can create a spawn point with random interval. • /deletevehiclespawn <name> ► You can delete spawn points with this command. • /showvehiclespawns ► Prints out spawn points in f1 console. ➡ "<name>" This defines your spawn points name which you can use in /deletevehiclespawn. ➡ "<x> <y> <z>" This is positions for vehicles to be spawned you can use console command "client.printpos" to see where you're standing at. ➡ "<vehicleName>" You need to use the short name for the item you want to be spawned, available vehicles are "minicopter", "scrapheli", "tugboat", "rowboat", "rhib", "motorbikesolo", "motorbikeduo", "bikesolo", "bikeduo", "subsolo" and "subduo". ➡ "<interval>" This defines the respawn time in seconds. ➡ "<intervalMin>", "<intervalMax>" you can adjust those values for how much time later the item will be respawned for random time. Ex; 1 10, Item will respawn every 1 to 10 seconds. Here is the default config file; { "Spawn1": { "Interval": 300.0, "IsRandomInterval": false, "RandomIntervalMax": 180.0, "RandomIntervalMin": 600.0, "SpawnPosition": { "x": 100.0, "y": 10.0, "z": 50.0 }, "VehicleName": "minicopter" }, "Spawn2": { "Interval": 300.0, "IsRandomInterval": true, "RandomIntervalMax": 600.0, "RandomIntervalMin": 180.0, "SpawnPosition": { "x": 100.0, "y": 10.0, "z": 50.0 }, "VehicleName": "scrapheli" } }

This plugin adds logs of players action and convenient control panel for viewing them. Features Logs KIlls + Destruction of buildings (detailed description of the killed / destroyed, distance and what killed 'weapon, damage type etc.') Death (detailed description of the killer, the distance and how player was killed 'weapon, damage type etc.') Respawn (location of respawn and on the sleeping bag or not) Teams (create, invite, accept, leave) Loot (crates, personal boxes, wounded players and all other "lootable" entities) Authorization (in code locks, tool cups, turrets) Construction (everything that builds) Transport (the moment of boarding the transport) Convenient and functional control panel Convenient search for online players Search by name or steam ID throughout the database The ability to conveniently select the date and time, as well as view individual categories of logs Teleport to the log location and its visualization (available only for admins) The history of searching and viewing profiles Save of all the nicknames of the player with whom he logged into the server The first and last connection The database is optimized as much as possible, the data is split, which allows you to store a large number of logs for a long time The ability to clear the database on wipe and players who have not logged on server for a long time, in automatic mode The ability to turn off the log globally and turn it on for certain players The plugin is fully localized for EN and RU languages Permission admineye.usemenu - for open and use panel Command /ae - for open panel Time Zones Time zone its different time between 0 UTC and player time UTC. You need add to configuration all time zones of your admins in seconds. How do it? Go to site UTC Time Standart select city, then you will get the difference in hours behind its + ahead its - Then you need multiply hours to second ( -6 * 3600 ) Done - its difference between zones. Write in config "Washington" : -21600 Then administrator must select (only once) his zone in menu "Time Zones", else plugin use default time zone config Discord At first you must create and copy discord Webhook, then paste url at config (you can use different channels) if you want change color, choose Colors, copy 0xNNNNNN, then paste Here, copy number and paste at config ^_^ Future plans Add console commands for search logs Add discord support for send logs (implemented) Add more logs I am waiting for your suggestions for improvement in the discussions Video Config { "Main settings": { "Enable delete all data on wipe": false, "Delete old players data every X hours [0 - off](It works on server startup or plugin reload)": 40, "After how many days the player's data is considered old": 14, "Time zone difference in seconds (set automatically by server zone)": 10800.0, "Time zone of counties (in seconds)": { "New York": -18000, "Moscow": 10800, "Berlin": 3600, "Paris": 3600, "Canberra": 39600, "London": 0, "Beijing": 28800, "Rome": 3600, "Washington": -21600 }, "Permission for use menu": "admineye.usemenu" }, "Log settings": { "Enable logging of kill for all": true, "Enable logging of death for all": true, "Enable logging of respawn for all": true, "Enable logging of team for all": true, "Enable logging of loot for all": true, "Enable logging of auth for all": true, "Enable logging of buildings for all": true, "Enable logging of mount for all": true, "Discord webhooks for logs": { "kills": { "Webhook url": "", "Color": 15105570 }, "deaths": { "Webhook url": "", "Color": 15548997 }, "respawns": { "Webhook url": "", "Color": 2067276 }, "teams": { "Webhook url": "", "Color": 3066993 }, "loots": { "Webhook url": "", "Color": 3447003 }, "auths": { "Webhook url": "", "Color": 9807270 }, "builts": { "Webhook url": "", "Color": 15658993 }, "mounts": { "Webhook url": "", "Color": 10181046 } } }, "Config version": { "Major": 1, "Minor": 2, "Patch": 0 } }

Teleport sleepers to a random position within a range of coordinates Choose between 3 types of target areas - Circle, Square, Zone [Features] ✯ Can manually set Min/Max range for (X,Y,Z) teleport location (square area) ✯ Can set radius range for teleport location (circle area) ✯ Can set Zone ID for teleport location (Zone Manager Required) ✯ Can use Zone radius for teleport location (Zone Manager Required) ✯ Can Set auto height option so players spawn at ground level ✯ Option to adjust offset height above ground ✯ Can set to auto scan/teleport sleepers on plugin loading or player disconnect ✯ Chat/Console command to scan/teleport sleepers ✯ Option to ignore players within authorized TC range ✯ Chat command to show your current (X,Y,Z) location ✯ Option to teleport players back to previous location on reconnect ✯ Chat command to return all sleepers to previous location [Commands] - Default Chat/Console Commands All commands require server admin permissions [Chat] ✯ /scansleepers - scans for sleepers outside of coordinates and teleports them ✯ /scansleepers true - scan all sleepers and force teleports them ✯ /returnsleepers - returns all sleepers to their old location ✯ /scanme - posts your current (X,Y,Z) location in chat and console ✯ /marker <#> - Set marker (#) to your current location (1 - 4 required) ✯ /marker save - Saves current settings and markers ✯ /marker show - Lists all 4 (X,Y,Z) markers in chat ✯ /marker range - Lists current min/max (X,Y,Z) settings for teleport ✯ /marker update - Generates min/max (X,Y,Z) values from markers 1 - 4 if available ✯ /stsetting <setting> <value> - changes the selected setting to the value you enter [Settings] on - enables sleeper teleporter (no value needed) off - disables sleeper teleporter (no value needed) save - saves settings/markers (no value needed) kill - requires value (on/off) - If on this will kill sleepers outside of TC range instead of teleporting them kill delay - requires value (#) - sets the delay in seconds before a sleeper is killed disconnect - requires value (on/off) - turns on/off teleport player on disconnect reconnect - requires value (on/off) - turns on/off teleport player back on reconnect autoheight - requires value (on/off) - let the plugin determain height by terrain height - requires value (#) - adds x value to the height when teleporting tcblock - requires value (on/off) - blocks players within auth TC range from being teleported areatype - requires value (circle/square) - sets the target area to use radius or all 4 markers radius - requires value (#) - sets the target area radius around marker #1 retry - requires value (#) - sets the teleport retry limit when target location is blocked or invalid zone - requires values: [Zone Manage Options] * on/off - set teleport location to use ZoneManager * id - requires value (#) - sets the zone id to use from zone manager * radius - requires value (on/off) - on use zone radius or off use config radius [Console:] ✯ scansleepers - scans for sleepers outside of coordinates and teleports them ✯ scansleepers true - scan for sleepers and force teleports them NOTES: * If using circle area type only marker 1 will be used and radius must be set * If using square area type you must set all 4 markers * Report all issues or bugs in our discord Sleeper Teleporter Setup Instructions: You must have server admin auth to use commands. These instructions are shown using the default commands, if you change the chat commands the prefix will be that command. Choose the area type for teleport location you want to use. A) Square B) Circle C) Use Zone Manager Depending on your chosen area type you must follow the correct setup for the location to work properly. There are other options you can use for all area types: /stsetting tcblock on/off - blocks players within auth TC range from being teleported /stsetting disconnect on/off - teleport player to area when they disconnect /stsetting reconnect on/off - teleport player back to last location when reconnecting Area Type Options & Setup: A) Square: 1. Set the area type to square by typing "/stsetting areatype square" in chat 2. Stand in each corner 1 at a time and type the "/marker 1-4" commands for each corner. The order does not matter 3. Once all 4 markers are set then use chat command "/marker update" to allow the system to generate the min/max location values 4. Then save all current markers and settings by typing "/marker save" in chat 5. Now you must define the limits in the square area. Set the height to auto/random & height adjustment /stsetting autoheight on/off - on will detect terrain height and place player on the ground, off will use random height from the 4 markers /stsetting height # - adds x to the height to make sure players do not spawn in foundations B) Circle: 1. Set the area type to circle by typing "/stsetting areatype circle" in chat 2. Stand in the center of the area you want to use and type "/marker 1" in chat 3. Set the radius of the location "/stsetting radius #" - change # to the value you want 4. Now you must define the limits in the circle area. Set the height to auto, adjusted, or random /stsetting autoheight on/off - turn on/off auto height /stsetting height # - adds x to the height to make sure players do not spawn in foundations C) Use Zone Manager: 1. Set the area type to circle by typing "/stsetting areatype circle" in chat 2. Set use zone manager to on - "/stsetting zone on" 3. Set the zone ID for the zone to use "/stsetting zone id #" replace # with the zone ID 4. Set to use zone radius or config radius "/stsetting zone radius on/off" if off will use the radius defined using "/stsetting radius #" Config: Example only { "Settings": { "chatscansleepers": "scansleepers", "chatreturn": "returnsleepers", "chatmylocation": "scanme", "chatmarker": "marker", "chatsetting": "stsetting", "areatype": "circle", "enable": true, "moveonload": false, "moveonconnect": false, "moveondisconnect": true, "radius": 4.0, "x_min": 116, "x_max": 123, "y_min": 21, "y_max": 21, "z_min": 318, "z_max": 326, "autoheight": false, "aboveground": 1, "ignoretcplayers": true, "retry": 5 }, "Markers": { "marker1": { "x": 120.221924, "y": 21.3408051, "z": 322.4336 }, "marker2": { "x": 121.245216, "y": 21.3484211, "z": 326.7593 }, "marker3": { "x": 116.610687, "y": 21.348423, "z": 325.452423 }, "marker4": { "x": 123.968338, "y": 21.348423, "z": 320.143555 } }, "ZoneManager": { "usezone": true, "zoneID": "66592319", "usezoneradius": false } } Language: { "st_001": "My Position: {0}\n X: {1}\n Y: {2}\n Z: {3}\n", "st_002": "{0} has been moved to {1}", "st_003": "Missing marker number - /marker (#)", "st_004": "Marker #{0} has been set for {1}", "st_005": "Marker Locations:\n #1 = {0} \n #2 = {1} \n #3 = {2} \n #4 = {3}", "st_006": "Location Range:\n X = {0} - {1} \n Y = {2} - {3} \n Z = {4} - {5}", "st_007": "Missing Marker: #{0}", "st_008": "Setting/Markers Saved", "st_009": "Sleeper Teleporter is now {0}", "st_010": "Teleport player on {0} is now {1}", "st_011": "missing setting/values - /stsetting <setting> <value>", "st_012": "Auto Height is now {0}", "st_013": "Height adjustment is now {0}", "st_014": "TC Block is now {0}", "st_015": "Teleport Area Type is now {0}", "st_016": "Teleport Area Radius is now {0}", "st_017": "Teleport Retry limit is now {0}", "st_018": "Use Zone Manager is now {0}", "st_019": "Zone ID is now {0}", "st_020": "Zone radius is now {0}" }

Introducing the AutoBan plugin for Rust servers - a powerful and efficient tool for managing and controlling player behavior on your server. This plugin is designed to help server owners and administrators keep their servers running smoothly and free from rule-breaking players. AutoBan's key features include: Automatic banning of players based on the number of reports they have received: If a player exceeds a certain number of reports (configurable by the server owner), they will be automatically banned with a customizable reason message. Mass Reporting Protection: Prevents players from abusing the report system by implementing safeguards against mass reporting, including cooldown periods, limits on the number of reports a player can submit or receive within a specific time frame, and ensuring only unique reports are counted. Processing F7 (In-Game) Reports: Fully integrates with Rust's F7 report system, capturing and processing reports submitted through the in-game interface, ensuring they are counted towards a player's total reports, and sent to Discord if configured. Player-Friendly Reporting System: Allows players to choose from a list of available report reasons when reporting another player, making the reporting process more user-friendly and consistent. Customizable reason messages for bans: Server owners can customize the message shown to players when they are banned. Valid report reasons that can be set by the server owner: Define which reasons are considered valid for triggering automatic bans. Option to broadcast ban messages to the chat: Choose whether to publicly announce when a player has been banned. Ignored players list: Allows certain players (e.g., admins) to be excluded from automatic banning. Timer for broadcasting bans to administrators and console: Set a timer to periodically broadcast current bans to admins and console. Chat commands and console commands for managing reports and bans: Provides a suite of commands for administrators to manage the plugin's functionality. Permissions system for controlling who can access the plugin's features: Granular permissions allow precise control over who can report, view reports, ban, unban, etc. Detailed logging of all bans and reports: Keeps comprehensive records of all actions taken by the plugin. Discord Alerts: Sends notifications of reports and bans to specified Discord channels via webhooks. Option to send reports to a URL: Integrate with external systems by sending report data to a specified URL. Timed bans: Allows for bans to be temporary, based on a configurable time period. Usage: CHAT COMMANDS: /report <username> Initiate a report against a player. If no reason is specified, a list of valid reasons will be presented for selection. /report <username> <reason> Report a player with a specified reason. /reportreason <number> After initiating a report without a reason, use this command to select a reason from the presented list. /AB.viewreports View all current reports (requires permission). /AB.ban <user> <reason> Manually ban a player with a specified reason (requires permission). /AB.unban <user> Unban a player (requires permission). /AB.showbans View all current bans (requires permission). /AB.resetreports <userid> Reset the reports for a specific player (requires permission). CONSOLE COMMANDS: AB.getreports Display all current reports in the console. AB.getbans Display all current bans in the console. AB.resetreportsConsole <userid> Reset the reports for a specific player via console. AB.ban <userid> <reason> Manually ban a player via console. AB.unban <userid> Unban a player via console. OXIDE PERMISSIONS: AutoBan.report Allows a player to report others via the F7 menu (in-game reports). AutoBan.chatreport Allows a player to report others via chat commands. AutoBan.viewreports Allows viewing of all reports. AutoBan.ignore Excludes a player from being automatically banned (e.g., for admins). AutoBan.ban Allows a player to manually ban others. AutoBan.unban Allows a player to unban others. AutoBan.viewbans Allows viewing of all bans. AutoBan.resetreports Allows resetting reports for a player. AutoBan.tester Special permission that allows a player to report the same player multiple times (useful for testing). CONFIG: { "Max reports till user gets banned": 5, "Reason given to banned user": "You have been reported too many times, and have been banned for precautionary measures. An admin will review this suspension soon.", "Valid reasons *searches subject title and message of the report* (To make sure report is scanned, add different variations of reason; like cheat, cheater, cheating, cheats, etc.)": [ "cheating", "cheats", "hacks", "aimbot", "hacking", "esp", "teaming", "racism", "griefing", "walling", "doorcamping", "spawn killing" ], "Valid report types": [ "cheat", "abusive", "name", "spam" ], "Scan type of F7 reports": true, "Broadcast ban to chat": true, "Ignored Players *Steam ID's Only*": { "76561198000000000": "Admin" }, "Timer for broadcasting bans to admins and console": 820, "Send bans to users with the AutoBan.viewbans permission based on timer (In-Game)": false, "Send reports to URL": false, "URL to send reports to": "http://example.com", "Send reports to Discord": false, "Send bans to Discord": false, "Discord Reports Webhook URL": "http://example.com", "Discord Bans Webhook URL": "http://example.com", "Ban Timer (In hours or 'permanent')": "72", "Max reports a player can submit per hour": 3, "Max reports a player can receive per hour": 5, "Cooldown between reports from the same player in minutes": 10 }

Features This plugin prevents players from looting admins and specified groups. It checks if the looter has a specific permission ("adminlootprotection.use"), and if not, it restricts them from looting players who are admins. You can also extend this to protect other specific groups or conditions. In summary, it adds a layer of protection for admins and certain groups to prevent unauthorized looting by other players. Functions Give the respective group on your server the appropriate permission to avoid being looted: adminlootprotection.use load, run, enjoy #free4all

Allows players to open a live admin chat from Rust to Discord to get support. Please delete the "LiveAdminChat.json" language file in "/oxide/lang/en/" before updating to version 1.2.3. If you have any errors, please open a support request and I will help you asap. FEATURES: Creates a discord channel in the provided channel category Allows the Rust player and Discord admins to communicate The ability to store the live admin chat as a transcript Allows a lot of customization, including: The command a player uses to respond to the admin chat The chat prefix for messages sent to the player The Steam profile icon for messages sent to the player The default reason for closing chats Whether or not to display the admin's name when sending messages to the player The channel ID where transcripts will be sent to The Discord roles that will be mentioned when a new channel is created Whether or not to close the channel when the player disconnects from the server Setting the in game chat command to start admin chats Defining the cooldown value after the last ticket was closed Setting a custom cooldown value per player CONFIGURATION: You need to create a channel category just for LiveAdminChat. Otherwise, the bot will say "Player is currently offline; message was not sent." because its looking for valid 17 digit channel names. The channel name has to be a valid STEAM64ID in order to send messages to players. Note: You can actually use this to your advantage. If you create a channel in the category with a players STEAM64ID, you can start sending messages back and forth without them starting a chat themselves. Setup your bot according to the guide on the Discord extension plugin page: https://umod.org/extensions/discord Also make sure your Discord bot has the following permissions in your server for the channel category and transcript channel: View Channels Send Messages Read Message History Embed Links Attach Files Read Message History PERMISSIONS: liveadminchat.use - required to allow players to use the /adminchat command. liveadminchat.bypasscooldown - allows the player to bypass the chat cooldown CHAT COMMANDS: /adminchat - opens a live admin chat with Discord admins. /reply <message> - sends the response from the player to the Discord admins. CONSOLE COMMANDS: Usage: liveadminchat.setcooldown <steam64id> <cooldown_minutes> Usage: liveadminchat.removecooldown <steam64id> Usage: liveadminchat.listcooldowns DISCORD: Admins can provide a reason for closing the chat by typing the reason after !close in the channel. Anything after "!close" will be included in the reason. Example: !close Closed due to no response Admins can set the chat cooldown, in minutes, per player by using !cooldown in the chat channel. If no cooldown is specified when the chat is closed, the cooldown will be set to the "Chat Cooldown (minutes)" value from the config. Example: !cooldown 60 TRANSCRIPTS: If you want to save the player/admin chats as transcripts, add a channel ID to "Transcript Channel ID" in the config. Otherwise, if you do not want transcripts then leave it blank and they won't be created. CONFIG:

Better Vanish allows server admins or users with permission to go fully invisible to spectate/watch players. It is based on the free public version on uMod by Wulf and has been in development since 2017. However, this version was written from scratch with performance, security and optimization in mind. Key features: Vanished administrators cannot be seen by any other players or cheaters. ¹ Optimization with performance in mind. No garbage allocations. Smaller size, lightweight with only most necessary functions for being invisible. Auto-hide / Auto-noclip after joining. ² Can be used by non-admins with certain restrictions. Auto teleportation under the map or to a safe spot (if you crash or disconnect). ³ Vanished state persists between disconnects or server restarts (configurable). Invisible to the world, environment, AI, traps and so on. ⁴ Custom & Lightweight trigger subsystem. Vanished player is only enters the most important world triggers at zero overhead. Can hide and unhide other players via command. The inventory spy function will let you see and edit player's or NPC's inventories. Sound effects when entering and leaving invisibility (other players can't hear it). Supports original Vanish API & Hooks. Explanations: You must behave accurately if you don't want to get attention from potential cheaters. Do not play, shoot, or touch your inventory and outfit. Auto-noclip is valid only for admins. Non-admins cannot be teleported underground. Please use the safe points. You still may provoke AI to follow you or shoot at you if you cause damage to them. Configuration The settings and options for this plugin can be configured in the BetterVanish.json file under the oxide/config directory. The use of a JSON editor or validation site such as jsonlint.com is recommended to avoid formatting issues and syntax errors. { "Show visual indicator (true/false)": true, "Visual indicator image address": "https://i.imgur.com/dOvX4uA.png", "Visual indicator anchor min": "0.1 0.001", "Visual indicator anchor max": "0.17 0.10", "Visual indicator color": "0.7 0 0 1", "Depth of an underground teleport (upon disconnection)": 15.0, "Block all incoming damage while vanished (true/false)": true, "Block all outgoing damage while vanished (true/false)": true, "Auto vanish on connect (true/false)": true, "Auto noclip on connect (true/false)": true, "Auto noclip on vanish (true/false)": true, "Turn off noclip on reappear (true/false)": true, "Persist vanish (don't unhide upon leave & restore after restart)": true, "Use sound effects (true/false)": true, "Enable safepoints (true/false)": true, "Remove all safepoints after wipe (true/false)": true, "Config revision (do not edit)": 4 } Localization The localization for this plugin can be configured in the BetterVanish.json file under the oxide/lang/en directory. The use of a JSON editor or validation site such as jsonlint.com is recommended to avoid formatting issues and syntax errors. { "CommandVanish": "vanish", "CommandSetVanish": "setvanish", "CommandUnvanishAll": "unvanishall", "CommandInvSpy": "invspy", "VanishDisabled": "<color=#FF686B>Vanish disabled</color>", "VanishEnabled": "<color=#91D6FF>Vanish enabled</color>", "VanishDisabledOther": "<color=#FF686B>You disabled vanish on {0}</color>", "VanishEnabledOther": "<color=#91D6FF>You enabled vanish on {0}</color>", "UnvanishedPlayers": "<color=#FF686B>You unvanished {0} players!</color>", "SetVanishHelp": "Syntax: /setvanish PlayerName", "SafePointNotSet": "You haven't set your <color=#F7B267>Safe Point</color>\nType <color=#FF686B>/vanish safepoint</color> to save your current position.\nYou will be automatically teleported there upon disconnection.", "SafePointSaved": "Your current position is saved as a Safe Point!", "MultiplePlayers": "Multiple players found!\nRefine your search or use Steam ID.", "NothingInSight": "No players in sight", "NoSuchPlayer": "No such player found ({0})", "InvSpyLooting": "Looting: {0} ({1})." } Permissions This plugin uses Oxide's permission system. To assign a permission, use oxide.grant <user or group> <name or steam id> <permission>. To remove a permission, use oxide.revoke <user or group> <name or steam id> <permission>. bettervanish.allowed - allows non-admin players to use vanish and become invisible. bettervanish.allowedother - allows non-admin players to vanish other players by their name. bettervanish.perma – the bearer will be vanished automatically and won’t be able to turn off vanish himself. bettervanish.unvanish - allows non-admin players to unvanish everyone at once. bettervanish.invspy - allows non-admin players to use inventory spy to loot players and NPCs remotely. bettervanish.skiplocks - allows non-admin players to have access to locked entities (boxes, doors). Commands This plugin provides universal chat and console commands. When using a command in the chat, prefix it with a forward slash: /. vanish - Toggles vanish state. vanish safepoint - Save a Safepoint, where get teleported on disconnect (your current position). setvanish <PlayerName> - Toggles vanish state of specified player. unvanishall - Unvanish everyone at once (both online & sleepers). invspy - Let you see and edit players or Npcs inventories, <name/steamID64> or look at the target and use then "invspy " Plugin Data This plugin can store 2 data files under oxide/data: BetterVanish-SafePoints.json - Player safepoints storage. BetterVanish-PersistPlr.json - Players with persisted vanish state. Developer API bool _IsInvisible(BasePlayer player) bool _IsInsivible(IPlayer player) void _Disappear(BasePlayer) void _Reappear(BasePlayer)

This plugin makes the admin’s life easier by automatically generating maps, initiating a vote that lets users choose which map they would like to play in during the next wipe and auto wiping the server. Depends on: Image Library Wipe Info API (If your server in country that have forced wipe at Friday please use WipeInfoApi file in MapVoter/WipeInfoApi/WipeInfoApi .cs) Discord extension Update 1.5.00: Unified Plugin Types Merged all different types of the plugin into a single, unified version. Server Wipe Fix Fixed an issue where the plugin did not wipe the server after a restart. General Improvements Resolved various other issues to enhance performance and stability. Added server identity to the configuration file. If you load the plugin while the server is running, it will automatically set to the current identity. Alternatively, you can find the server identity by: - Checking the startup command for +server.identity. - Inspecting the server.cfg path: You can locate the server identity in /server/{server.identity}/cfg/. Logging Enhancements Added logging files to track auto-wipe progress. To enable this feature, set Enable Debug Mode to true in the configuration file. Update 1.4.67: Added: Single Discord message now supports up to 4 maps. Wipe countdown in Embed. Fixed: Magnify icon not showing. New config options: You must set the Embed URL if you want to use the Single Discord embed message. "Embed Url": "https://codefling.com" "Single Embed?": false Note: The single message will only display 4 maps, but you can add more. Update 1.4.64: Server administrators can list data files to be deleted after the wipe "Plugins Data wipe": { "Enable plugins data wipe on forced wipe day": true, "Enable plugins data wipe on map wipe day": true, "File names to be deleted on forced wipe day": [ "wipeinfo", "WipeInfoApi" ], "File names to be deleted on map wipe day": [ "wipeinfo", "WipeInfoApi" ] } If you utilize a game hosting service, please ensure that your host permits the modification of the startup command. Update 1.3.26 : Auto wipe now works for non Dedicated (game server or host) servers but you'll have to disable sandbox and you won't be able to auto update the server. Requirements Rust Server(s) setup in a standard way on a Windows ,Pterodactyl Panel , Open Game Panel, Ubuntu dedicated server or game/host server (Doesn't work on LinuxGSM). Administrator privileges on said dedicated server. All of your server settings in \server\my_server_identity\cfg \server.cfg except rcon.port ,rcon.web rcon.password which will be added to batch script later. Auto Wipe will launch the server without start.bat. Features: Automatically restart and update the server every first Thursday of the month. Automatically generate or select random maps from rustmaps.com filter maps on wipe day or x days before wipe using https://rustmaps.com/ & wipe-info-api and start the vote. Allows players to vote on maps through an in-game UI or Discord (if you use any plugin that links a player and a Discord user, enable “only authenticated users can vote” in the config file to avoid duplicate votes). Automatically checks if it’s wipe day using wipe-info-api and the plugin’s config. Automatically update Oxide and the server and wipes it on forced wipe. Configure the plugin through a GUI (not all settings are available on the GUI). Select maps from rustmaps.com through a GUI via a RustMaps share code. Added Custom maps via GUI (to delete map you have to delete it from data file in MapVoter/Custommapdata.json). The vote will start automatically on custom maps in data folder if custom maps usage is enabled in config. Fun kit. Automatically generates custom maps every wipe, utilizing RustMaps.com. Please note that to use this feature, a subscription to RustMaps.com is required. Update 1.4.61 In this update you can generate a custom maps every time map vote starts with same config you provided. Update 1.3.40 New UI Update 1.3.35 1- Added Fun kit. Fun kit is kit that will be enabeled before every wipe, players can redeem it using /kit <kit name> or when respawning. Players wont be able to learn BPs and unloack workbench tree nodes. How to add fun kit? 1 - create kit using kits plugin with permission example : 2 - In map voter config file edit : "Fun Kit": { "Fun kit enabled": false, "Enable Fun kit x minutes before wipe": 0, "Kit name": null, "Permission": null }, 3 - save and reload MapVoter. 2 - Map Voter will print future wipes in console when loaded How to add Custom maps : Video Permissions: MapVoter.use only allows an admin to generate maps and start a vote. MapVoter.Manager allows an admin to use all the features. MapVoter.Vote allows player to vote(you can enable or disable this in configuration). Commands /mvote : Opens the plugin’s main GUI. /startvote After selecting which maps will appear on the vote, starts the vote. MapVoter.generate <Number of maps to generate> <seed> <voting duration in minutes>. voteresult : Shows which map had won the vote. Mapvoter.reload reload the plugin. MapVoter.mapwipe <delay in seconds> <Map size > will generate a map and change startup parameters in server.cfg. MapVoter.mapwipe <delay in seconds> <Custom map url > will wipe the server with a given custom map url and change startup parameters in server.cfg MapVoter.bpwipe <delay in seconds> <Map size > will generate map and delete *.db, *.db-journal and *.sav files and changes startup parameters in server.cfg MapVoter.bpwipe <delay in seconds> <Custom map url > will delete *.db, *.db-journal and *.sav files and change startup parameters MapVoter.cancelwipe : cancels ongoing wipe. MapVoter.stopvoting : stops ongoing voting. MapVoter.update <Delay in seconds> initiates restart and updates the server & oxide. Mapvoter.CancelUpdate : Cancels restart and update. Discord commands !vote !generate <Number of maps to generate> <seed> <voting duration in minutes>. !mapwipe <delay in seconds> <Map size > !bpwipe <delay in seconds> <Map size > bpwipe <delay in seconds> <Custom map url > !cancelwipe !stopvoting !update <Delay in seconds> !cancelupdate Configuration { "Commands": { "Open MapVoter UI": "mvote", "Generate Mpas": "MapVoter.generate", "vote result": "voteresult" }, "Options": { "Map size": 3500, "Select random maps from rustmaps filter id instead of generating random maps on wipe day (true/false)": false, "How many pages the plugin looks up per search request(every page has 30 maps": 10, "Enable Discord bot (true/false)": true, "Only players with permission MapVoter.Vote can vote (true/false)": false, "Log to Discord (true/false)": true, "Discord Logs Channel Id": "", "Disable UI": false, "RustMaps API key": "https://rustmaps.com/user/profile", "staging": false, "barren": false, "Stop voting after (minutes)": 60, "avatar url": "", "Discord footer": "", "filter Id": "Visit https://rustmaps.com/ and adjust your map requirements. In the red box above the settings hit the Share button,the string at the end of the URL is the filterId.Example URL: https://rustmaps.com/?share=gEU5W6BUuUG5FpPlyv2nhQ the string at the end in this case {gEU5W6BUuUG5FpPlyv2nhQ} is the filterId." }, "Discord Settings": { "Vote Channel id": "", "Discord Apikey": "BotToken", "Discord Command Prefix": "!", "Discord Channels": [ { "Discord Channel ID": "", "Commands": [ "generate", "vote", "mapwipe", "bpwipe", "cancelwipe", "stopvoting", "update", "cancelupdate" ] } ], "Discord Command Role Assignment (Empty = All roles can use command.)": { "generate": [ "DiscordRoleName", "DiscordRoleName2" ], "vote": [ "DiscordRoleName", "DiscordRoleName2" ], "mapwipe": [ "DiscordRoleName", "DiscordRoleName2" ], "bpwipe": [ "DiscordRoleName", "DiscordRoleName2" ], "cancelwipe": [ "DiscordRoleName", "DiscordRoleName2" ], "stopvoting": [ "DiscordRoleName", "DiscordRoleName2" ], "update": [ "DiscordRoleName", "DiscordRoleName2" ], "cancelupdate": [ "DiscordRoleName", "DiscordRoleName2" ] } }, "Auto Vote": { "Auto start vote": true, "Only Authenticated users can vote through discord": true, "Start voting x days before wipe": 0, "Start voting at (HH:mm) 24-hour clock": "17:00", "Number of maps to generate": 4 }, "Auto Wipe": { "Custom Map": { "Custom map": false, "Map URL": "" }, "Map Wipe schedule": [ 7, 14, 21, 28 ], "BP Wipe schedule": [ 0 ], "Enable Auto wipe": true, "Wipe BPs at forced wipe day": true, "Forced Wipe time (HH:mm) 24-hour clock": "19:00", "Wipe time (HH:mm) 24-hour clock": "19:00" } } MapVoter.cs, which will handle wipe schedule and automatically generate maps, start voting and restart the server. How to Install 1 - Upload Mapvoter.cs. 2 - all your server configuration must be in /server/{server.identity}/cfg/server.cfg or you can change the path in config if your host use different path (/server/{server.identity}) 3- Upload Discord extension to /RustDedicated_Data/Managed. 4- change the startup command if possible to ./RustDedicated -batchmode +server.identity "rust" +rcon.port {{RCON_PORT}} +rcon.web true +rcon.password \"{{RCON_PASS}}\" or leave all the map seed, size and level URL empty. 5-create server.cfg file in server/{server.identity}/cfg/ example : server.port 28000 server.seed server.worldsize //server.levelurl server.maxplayers 100 server.gamemode vanilla server.hostname " Vanilla" server.tags vanilla,weekly server.level "Procedural Map" server.radiation true server.saveinterval 600 server.tickrate 30 server.headerImage "" server.url "" server.secure 1 server.salt 50 Perform a Dry-Run Whilst your server is online with no players, test some commands like Mapvote.bpwipe, server.cfg, and make sure that server.seed and server.worldsize has changed and all your selected files have been deleted. Contact kaysharp#2008

Manage your Rust server easier and more efficiently with the AdminMenu plugin. Track players, interact with them, edit their data and permissions, as well as change server convars and manage plugins. Features: Menu retains its state after closing, you won't lose everything you did before. Ability to fully translate the menu into any language. Large range of permissions for each action, will allow you to flexibly customize the admin menu for each group of administrators. Quick menu that allows you to perform quick actions Full list of players with the ability to filter by online, offline, admins and moderators. Also has a frame of different colors depending on the level of authorization. Wide range of information and actions for the selected player. Editing convars with search. Has a complete list of editable convars with descriptions for some of them. Extensive issue menu by category, with easy management of name, skin and amount (manual, +1, +100, +1000, +10000). Plugin management menu. It is possible to reload, unload or load a plugin easily and quickly. Updates occur in real time. Ability to create your own custom buttons that execute several commands Quick Start: You install the plugin in the plugins folder. Give yourself the adminmenu.fullaccess permission. Commands, use one of your choice, one for the player and one for the admin group: o.grant user {name/steamid} adminmenu.fullaccess o.grant group admin adminmenu.fullaccess Press the X button (swap seat button) or type adminmenu in the console. Enjoy Useful stuff: You can quickly open a player in the admin menu. To do this, point at the player and press X. You don't have to hover over the player exactly, you will be able to open players within a certain radius of the place you are looking at. CUSTOM BUTTONS Custom buttons are buttons that when pressed will execute commands on behalf of the administrator, commands can be several, below will be the details. At the moment, custom buttons can be created in two places: in the quick menu and in the menu when selecting a player. These places are separated in the config. Button Fields: "Execution as server" - Call the command on behalf of the server, not the administrator "Label" - Text that will be on the button, for each such inscription creates a field in the lang file, accordingly you can translate this text into several languages. "Commands" - Array of commands that will be executed on behalf of the administrator. Chat commands require a special entry, see examples. "Permission"- permission to display and use the button. You need to write the permission that will be after "adminmenu.". Example: if you enter the permission "test" the permission will be adminmenu.test "Position" - The location for the button, the first number is responsible for the row number, the second for the position within the row, starts from 0.There are limits of locations, if you have gone beyond the limit - the button will not be displayed. Common Tags: {adminUID} - administrator's id. {position} - administrator coordinates (underfoot) {view_position} - the position where the administrator is looking (can be used for spawning or something similar) {view_direction_forward} - forward view direction of the administrator {view_direction_backward} - the direction the administrator is looking backwards {view_direction_left} - direction of the administrator’s view to the left {view_direction_right} - administrator’s view direction to the right Tags for target only: {steamid}, {steamID}, {userID}, {STEAMID}, {USERID} - mean the same thing, namely the id of the selected player. {target_position} - target coordinates (underfoot) Example of commands: chat.say \"/{chat command}\" vanish ban {steamID} teleport {steamID} {adminUID} More information about the grant menu: The grant menu includes the full list of items including hidden items as well as custom items created by the CustomItemDefinitions library. The menu can be accessed from the navigation or from the menu of the selected player. When issuing itself has categories. Search works in any registry by any part of the name or short name. Has a page system at any stage. More information about the buttons in the Quick Menu: [Teleport to 0 0 0] - Teleport to coordinates 0 0 0. Requires adminmenu.quickmenu.teleportto000 permission [Teleport to Deathpoint] - Teleport to your deathpoint. Requires adminmenu.quickmenu.teleporttodeath permission [Teleport to Spawn point] - Teleport to a random spawn point. Requires adminmenu.quickmenu.teleporttospawnpoint permission [Kill Self] - Kill Self, kills even when immortal. Does not require permission. [Heal Self] - Fully heal yourself. Requires adminmenu.quickmenu.healself permission [Call Heli] - Call Helicopter to yourself (arrives in time). Requires adminmenu.quickmenu.helicall permission [Spawn Bradley] - Spawn bradley on yourself. Requires adminmenu.quickmenu.spawnbradley permission More information about the buttons in the menu of the selected player: [Teleport Self To] - Teleport yourself to the selected player. Requires adminmenu.userinfo.teleportselfto permission [Teleport To Self] - Teleport the selected player to yourself. Requires adminmenu.userinfo.teleporttoself permission [Teleport To Auth] - Teleportation to random authorization (TC). Requires adminmenu.userinfo.teleporttoauth permission [Teleport to Deathpoint] - Teleportation to a player's deathpoint. Requires adminmenu.userinfo.teleporttodeath permission [Heal] - Full healing, including metabolism. Requires adminmenu.userinfo.fullheal permission [Heal 50%] - Half healing. Requires adminmenu.userinfo.halfheal permission. [View Inventory] - View and edit player's inventory. Requires adminmenu.userinfo.viewinv permission [Strip Inventory] - Clear player's inventory. Requires adminmenu.userinfo.stripinventory permission [Unlock Blueprints] - Unlock all Blueprints. Requires adminmenu.userinfo.unlockblueprints permission [Revoke Blueprints] - Reset all Blueprints. Requires adminmenu.userinfo.revokeblueprints permission. [Kill] - Kill a player. Requires adminmenu.userinfo.kill permission [Kick] - Kick a player. Requires adminmenu.userinfo.kick permission [Ban] - Ban a player. Requires adminmenu.userinfo.ban permission More information about the buttons in the menu of the selected group: [Remove Group] - Remove group, has confirmation. Requires adminmenu.groupinfo.removegroup permission [Clone Group] - Clone group with the ability to copy users. Requires adminmenu.groupinfo.clonegroup permission Permissions: adminmenu.use - Ability to use admin menu with basic set. Open tab quick menu (each button has its own permission, without permissions is present only kill yourself button) and the list of players. adminmenu.fullaccess - Full access to all functions without the need for each permission, includes also adminmenu.use. It is recommended to give only to the main administrators. adminmenu.quickmenu.teleportto000 - Access to the button in the quick menu, teleportation to coordinates 0 0 0 0. adminmenu.quickmenu.teleporttodeath - Access to the button in the quick menu, teleportation to the point of your death. adminmenu.quickmenu.teleporttospawnpoint - Access to the button in the quick menu, teleportation to a random spawn point. adminmenu.quickmenu.healself - Access button in quickmenu, heal yourself completely. adminmenu.quickmenu.helicall - Access to the button in the quick menu, call a helicopter to yourself (arrives in time). adminmenu.quickmenu.spawnbradley - Access button in quickmenu, spawn bradley. adminmenu.userinfo.teleportselfto - Access to the button in the menu of the selected player, teleportation to the selected player. adminmenu.userinfo.teleporttoself - Access to the button in the menu of the selected player, teleport the selected player to himself. adminmenu.userinfo.teleporttoauth - Access to the button in the menu of the selected player, teleportation to random authorization (TC). adminmenu.userinfo.teleporttodeath - Access to the button in the menu of the selected player, teleportation to the place of death of the player. adminmenu.userinfo.fullheal - Access to the button in the menu of the selected player, full healing, including metabolism. adminmenu.userinfo.halfheal - Access to the button in the menu of the selected player, half healing. adminmenu.userinfo.viewinv - Access to the button in the selected player's menu, view and edit the player's inventory. adminmenu.userinfo.stripinventory - Access to the button in the menu of the selected player, clear the player's inventory. adminmenu.userinfo.unlockblueprints - Access the button in the menu of the selected player, unlock all drafts. adminmenu.userinfo.revokeblueprints - Access to the button in the menu of the selected player, reset all drafts. adminmenu.userinfo.kill - Access the button in the selected player's menu to kill the player. adminmenu.userinfo.kick - Access the button in the selected player's menu to kick the player. adminmenu.userinfo.ban - Access to the button in the menu of the selected player, ban the player. adminmenu.groupinfo.removegroup - Access to the button in the menu of the selected group, the ability to remove the group. adminmenu.groupinfo.clonegroup - Access to the button in the menu of the selected group, the ability to clone the group. adminmenu.convars - View and edit convars. adminmenu.permissionmanager - View and edit permissions in groups, player groups, create, delete and clone groups (requires additional permissions from these buttons). adminmenu.pluginmanager - Access to plugin management, reloading, unloading, loading plugins. adminmenu.give - Access to give resources, as well as yourself and the selected player.

Allows players to drop their entire inventory (Main, Belt, and Wear containers) via a command. Admins can forcefully drop any player's inventory. This plugin is highly configurable, allowing control over permissions, cooldowns, broadcast messages, and item drop behaviour. Permissions dropinventory.use - Grants the ability for players to use the /drop command to drop their own inventory. dropinventory.cooldown.bypass - Allows players to bypass the cooldown period when using the /drop command. dropinventory.admin - Grants access to admin commands like /drop.admin to drop the inventory of any player. Commands Player Command: /drop - Allows players to drop their entire inventory (Main, Belt, Wear containers) if they have permission (dropinventory.use). - Cooldown: Players can use the command again after the cooldown period, unless they have the dropinventory.cooldown.bypass permission. Admin Commands: /drop.admin <all | belt | wear | main> <playername/steamid> - Allows an admin to drop another player's inventory. Admins must have the dropinventory.admin permission. - Admin will receive confirmation, and the target player will be notified. Console Command: drop.admin <all | belt | wear | main> <playername/steamid> Equivalent to the chat admin command, but used in the server console. Configuration Broadcast Settings - Chat Prefix: Prefix for all messages shown in chat (e.g., <color=#FF0000>[DropInv]</color>). - Use Chat Message: Whether messages are broadcast via in-game chat. - Use Game Tip Message: Whether to use in-game game tip notifications. Drop Settings - Sound Effect: A sound effect played when items are dropped. - Drop Velocity: The velocity at which items are thrown when dropped. - Drop Main Container: Whether the main inventory should be dropped. - Drop Wear Container: Whether the wear container (armor) should be dropped. - Drop Belt Container: Whether the belt (hotbar) items should be dropped. Command Settings - Chat Command Cooldown: The cooldown time (in seconds) for players using /drop. - Player Chat Command: The command players can use to drop their inventory. - Admin Chat Command: The chat command that admins can use to drop another player's inventory. - Admin Console Command: The console command that admins can use to drop another player's inventory. Default Configuration { "Broadcast Settings": { "Chat Prefix": "<color=#FF0000>[DropInv]</color> ", "Use Chat Message": true, "Use Game Tip Message": true }, "Drop Inventory Settings": { "Sound Effect": "assets/bundled/prefabs/fx/gestures/drink_vomit.prefab", "Drop Velocity": 5, "Drop Main Container": true, "Drop Wear Container": true, "Drop Belt Container": true }, "Command Settings": { "Chat Command Cooldown": 60, "Player Chat Command": "drop", "Admin Chat Command": "drop.admin", "Admin Console Command": "drop.admin" }, "Version": { "Major": 1, "Minor": 0, "Patch": 1 } } Default Language { "Cooldown": "Drop is on cooldown. Time remaining: <color=#FF0000>{0}</color> seconds.", "DropAll": "Your Main, Belt and Wear items have been dropped.", "DropMain": "Your Main items have been dropped.", "DropBelt": "Your Belt items have been dropped.", "DropWear": "Your Wear items have been dropped.", "DropMainBelt": "Your Main and Belt items have been dropped.", "DropMainWear": "Your Main and Wear items have been dropped.", "DropBeltWear": "Your Belt and Wear items have been dropped.", "NoContainers": "No containers are enabled for dropping items.", "AdminDroppedItems": "Your items were dropped by an admin.", "AdminDroppedItemsReply": "You dropped (Player: <color=#FF0000>{0}</color>) Items.", "NoPermission": "You don't have permission to use this command.", "AdminCommandUsage": "Usage: /drop.admin <playername or steamid>", "PlayerNotFound": "Player not found or multiple players found matching the name or ID provided.", "Restrained": "You Can Not Use This Command While Restrained" }

Introducing Total Control, a comprehensive admin tool designed for Rust game servers. This plugin is built with a full GUI, providing an intuitive and user-friendly interface for server administrators. With Total Control, you can customize every aspect of your Rust server to create a unique gaming experience for your players. Here are some of the features that set Total Control apart: Settings Page (New!): The latest addition to Total Control, the Settings page introduces powerful options for customizing server-wide gameplay systems: Skip Night: Automatically skip night cycles or use a voting system where players can vote to skip night. Time Freeze: Freeze time to any time of the day you choose. Day and Night Settings: Configure the start and end of the day, set the percentage of votes required to pass a day skip, and adjust the delay for voting messages. You can also limit the number of nights players can skip before requiring a full night cycle. Custom Vote Command: Define the vote day command, with /day as the default. PvE/PvP Mode: Set basic PvE or PvP modes, which can be toggled on a timer, or be set to stay permanently on. PvE or PvP mode can be displayed on the player HUD. Raid Protection: Implement raid protection with the same flexible settings as the PvE/PvP modes, including timers and toggles. StackSize Page: A new addition to Total Control, the StackSize page allows you to set up multipliers for individual items or entire categories, offering greater control over item stacking in your server. Item Gather Rate Control: Customize the gather rate for every item in the game to balance resource acquisition and gameplay progression. Smelting and Cooking Control: Adjust the smelting speeds for furnaces, mixing tables, campfires, and oil refineries. You can also control the charcoal output amount, the cooked output amount, and the amount of fuel used. Reward System: Set up rewards for various in-game actions such as killing scientists, and players, or picking up or mining different items. Rewards can be given in the form of economics (if the Economics plugin is installed) or server rewards (if the ServerRewards plugin is installed) or even scrap. Bradley APC and Patrol Heli Rewards: Players can be rewarded for dealing damage to or destroying the Bradley APC and Patrol Heli. There’s also a setting to divide the loot among all players who dealt damage or give all the loot to the player who deals the final blow. Total Control allows you to create a Rust server tailored to your community’s playstyle. Whether you’re looking to create a hardcore survival experience or a more casual, resource-rich environment, Total Control gives you the tools to make it happen. Accessible In-Game: One of the key features of Total Control is its accessibility. Any admin with the correct permissions can alter any settings directly in the game, even if they don’t have access to server files. Simply open the UI using the /tc command and change any settings as needed. Permissions: TotalControl.OpenGui To allow access to the Ui for admin. Chat Commands: /tc To Open the Ui for any player with the correct permission

Team Tracker is your is the best admin tool for monitoring player associations and enforce team size rules. Whether you need to ban an entire team or track players abusing the system, Team Tracker has you covered. It offers live logging, team queries, and auto-banning—all in one customizable and performant package. Dynamic identification of player teams Live discord logging Query a player team at any time Automatic custom ban system Battlemetrics integration High Performance clearplayerdata - deletes a players team data/history teamcheck - Sends a discord embed with a report of group data, warnings and current team players to discord. Note: All chat commands are universal meaning they can be used via the console, rcon(for import commands) and can be customized via the configuration. teamtracker.whitelist - Whitelists a player from being included in any team alerts (Admins and Developers are automatically whitelisted) teamtracker.admin - allows the use of the checkteam and whitelist commands Proximity - configurable distance between players Sleeping bag placement - bags given or placed within building Codelock authorization - authorized players on a codelock Turret authorization - authorized players on a turret Toolcupboard authorization - authorized players on a toolcupboard Healing - healing and reviving of other players Vehicle mounting - mounting of the same vehicle at the same time Team-members - history of team members Alerts: All alert types can be customized via the plugin config. Options include: Enable - this toggles any usage of the alert type to enable or disable the alert type Log to discord - Enables discord logs Warn Players - Sends an ingame warning to a player up to 30 seconds after the offense Weighting - configures how important the alert type is. This contributes to the ban by association score value. Warnings: Warnings are logged as a type of violation. This provides discord logs and the optional in game warning display to the violator. Display Warnings to Players - option to disable in game warnings Length of time to display warning - optional length of time to display warnings Warning Text - customizable warning text Bans: Team-Tracker allows for customizable automatic bans of players, who go over the group limits. Enable Bans - allows toggeling of the ban system Ban text - text to display as the reason for a player ban Log Bans to Discord - optionally log bans to discord. Logging Only Mode: Set Enable Bans & Log Bans to Discord to true and set Local Bans and Battlemetrics Bans to False Enable Ban by Max Association - enables banning a player or a team by summing all association values to create a total weighting. Example: if the team limit is 5 players and the Max Association Weighting is 10, if a player has more than 5 players with an association weighting of more than 10 this will apply a ban. Max Association Weighting - set the max association weighting per player in a group Ban Duration - length of time to ban for Ban Team - ban all team members of a banned player Ban Associations - bans all players over Max Association Weighting in relation to a banned player Local Bans - apply bans locally An API token for your battlemetrics org is required to use the battlemetrics ban features. A token can be acquired by visiting: https://www.battlemetrics.com/developers Server ID - set the BM server ID Go to https://www.battlemetrics.com/rcon, click into the select server. Check the address bar in your browser, the address will be ending with the Server Id, for example: https://www.battlemetrics.com/rcon/servers/123456 means 123456 is the Server Id. Org ID - set an organisation ID Go to https://www.battlemetrics.com/rcon/orgs, click into the org. Check the address bar in your browser, the address will be ending with the Organization Id, for example: https://www.battlemetrics.com/rcon/orgs/edit/123456 means 123456 is the Organization Id. BanList ID - adds a ban to a specific ban list Go to https://www.battlemetrics.com/rcon/ban-lists, click "View Bans". Check the address bar in your browser, the address will be ending with the Banlist Id, for example: https://www.battlemetrics.com/rcon/bans/?filter[banList]=abcdef-123456-example-banlist-example91011 means abcdef-123456-example-banlist-example91011 is the Banlist Id. Org Wide Ban - true if the ban should be applied to all servers in your organization Auto Add - true if the ban should automatically ban new identifiers after kicking a matching player. Native Enabled - true if native bans should be issued for this ban

Drop Bags tracks items dropped into the rust world. When there are high-volume drops, they are combined into a single “drop bag.” This method enhances performance by streamlining the handling of item drops and reducing item physics. Stop server stalls and freezing from item spam Works on craft spam, dropped item spam, gutted shark spam and horse dung! Light weight and easy to use Easy config DropBags uses one light weight hook to track dropped items. Dependent on how many items are dropped in a given radius those items get placed into a drop bag. This stops mass item spam effecting your server performance. { "Area Size - How far away items can be moved into a container": 7, "Max drops before moving items to container": 36, "Time to wait before moving items": 5.0, "Vischeck - checks items are visable before moving to container": true, "Calculate despawntime from drop bag items": true, "Reset dropbag despawn time on loot": false, "Override drop bag despawn time (seconds), 0 = false": 0.0 }

The promo code plugin for Rust game provides the ability to reward players for entering a code word. This plugin includes a variety of settings and functionality for easy management and configuration of promo codes in the admin panel. Main Features Creation and Configuration of Promo Codes: Promo Code: The administrator can create unique promo codes. Item Configuration: The administrator can determine which items will be given when the promo code is activated. Item Parameters Shortname: The code word for issuing a specific item. SkinID: The skin identifier of the item. DisplayName: The displayed name of the item. Amount: The number of items given by the promo code. Flexible Settings Promo Code Duration: Ability to set an end date until which the promo code will be active. Usage Limit: Setting a limit on the number of times the promo code can be used. Command Configuration Ability to replace item issuance with the execution of a specific server command when the promo code is activated. Example Usage Admin usage Give admin permission - promocodes.admin Open UI with command (can be changed in config, default: /p) Creating a Promo Code: Create the promo code "SUMMER21". Set its expiration date to July 31. Set a usage limit of 100 times. Player usage Open UI with command (can be changed in config, default: /p) Enter promocode Press CHECK button Item Configuration Add an item: shortname - "rifle.ak", skinid - "123456", displayname - "AK-47 Elite", amount - 1. Add an item: shortname - "ammo.rifle", skinid - "0", displayname - "Rifle Ammo", amount - 100. Command Replacement Set the command "give %STEAMID% some_reward" to be executed when the promo code is activated instead of issuing items. Configuration file { "Cooldown for promocode": 65, "Commands to open UI": [ "promocode", "promo", "code", "pc", "p" ] }

"My backpack fell through the ground, again!" is a sentence that all admins hate to hear. And what will happen if no admin is online when a players backpack (or held item) glitches through the ground? Correct, it will be lost forever. This plugin checks for all items which are dropped after a players death and will smoothly bring them up to the players death position (+ a little extra so they won't fall through the ground again). Just one command, one permission permissions and the configuration is very small and simple. Configuration: "Lift glitched items slowly up instead of teleporting them instantly": (Just a small cosmetic feature) If true, the items will be slowly lifted up until they pop out of the terrain. If false, the items will be teleported instantly to the position on which the played died. --> If you experience any performance issues by the animation/coroutine, leave the setting on "false". While testing I had no performance issues unless I retrieved 50+ items simultaneously (which won't ever happen on a live server nevertheless). Permissions: glitcheditemretriever.active If a player does not have this permission, his items will not be retrieved. Why? Admins tend to throw stuff under the map and want to disable the retrieve logic for these items. Now, you can revoke the permission and throw all your stuff under the map, this plugin will not bring it up to the map. Commands: /gir.toggle Can be used by every player, toggles the above mentioned permission for the calling player. Useful for admins when they want to throw stuff under the map. Just toggle the permission (to off), throw the stuff away, toggle the permission again (to on). Notes: To make sure an item is dropped under the terrain ON PURPOSE, I added a minimum distance of 3 meters between the noclip-flying-admin-player and the terrain. If an admin wants to throw his stuff under the map WITHOUT toggling the permission first, make sure to fly more than 3 meters under the terrain. If the players position is below the terrain but not at least 3 meters, the plugin assumes that the player glitched through the terrain, dropped the items by accident and retrieves them. Roadmap: - Since the plugins name could lead to the confusion: currently it only retreives the backpack and/or the held item the player drops on his death. I will check for items that were looted by p.e. barrels and other props later. - Maybe: configurable list of items that should be retrieved or ignored by the plugin - Smoother animation - Configurable message that is sent to the player - Check if player is in a tunnel/cave, since items that are dropped in these locations, are retrieved to the terrain (which is above the tunnel/cave!)

BattleReplay is a plug-in of Rust, which provides real-time combat playback function. The plug-in will automatically record and save each player's battle log, allowing easy configuration of the detail level of the log, the cooling time between records and the recording range. Through the flexible settings in the configuration file, it provides advanced logging, asynchronous logging and error logging, and provides efficient server management and playback functions. characteristic 1. Automatic Battle Replay: This plug-in will automatically record the player's battle log, including detailed information such as attackers, targets, weapons, money, injuries, etc. Every time a player participates in a battle, the plug-in will create a replay and save the log. 2. Detailed log configuration: Plug-ins allow you to control the level of log detail through configuration files. You can enable the Advanced Log to capture more accurate combat data, such as the number of hits, changes in health, and so on. 3. Real-time combat output data: the administrator can use the command to view the player's combat log in real time. Commands /battlelog and /battlelog stats provide access to combat records and statistics. 4. Flexible configuration management: This plug-in allows you to dynamically modify the configuration through commands without having to manually edit files. 5. Error Log: Plug-ins record detailed error messages when loading configuration files, so as to ensure voice feedback when any problems occur. 6. Asynchronous recording and uploading: The process of generating and uploading battle logs is handled asynchronously, which reduces the performance impact on the server and ensures the stability under high load. 7. Performance optimization: In order to avoid performance degradation caused by too many log records, the plug-in limits the number of concurrent records and provides the function of cleaning up historical logs. 8. Player Activity Detection: This plug-in detects combat activities, such as player attacks, and triggers combat replay only when actual combat events occur, thus preventing unnecessary logs from being generated. 9. Configuration file: All settings can be customized through config.json, which is dynamically loaded and saved by plug-ins. 10. Discord notification Plug-ins support sending notifications through Discord Webhook when fighting playback starts and ends. Administrators can receive reminders about the start and stop of players' combat records in Discord. Installation and use Installation: put the BattleReplay plug-in file in the plug-in directory of the server (/ox/plugins). Configuration file modification: When the plug-in is started for the first time, it will automatically generate the configuration file BattleReplay.json, which you can do according to your own preferences. Command: /battlelog: View the battle log of the current player. /battlelog stats: View plug-in statistics, such as the number of combat logs recorded and uploaded. /setbattleconfig < option > < value >: modify plug-in configuration options, such as recording range and cooling time. /replay <playername|playerid >: Force a player to record the combat replay, even if they are not within the specified recording range. { "Check Interval (seconds)": 5.0, "Recording Distance (meters)": 100.0, "Region Size (meters)": 100.0, "Recording Cooldown (seconds)": 60.0, "Auto Recording Length (minutes)": 3, "Skip Admins": false, "Total Recorded Logs": 0, "Total Uploaded Logs": 0 } Configuration options: Recording distance: the maximum distance to record the combat log. Any combat events beyond this distance will not be recorded. CooldownTime: records the cooling time (in seconds) of the battle log to prevent multiple logs from being generated quickly and continuously. MaxSimultaneousRecordings: The maximum number of concurrent recordings allowed at any given time to prevent performance problems. LogAdvancedDetails: Enables or disables advanced logging details, such as hits, health changes, etc. FREQUENTLY ASKED QUESTIONS Q: The configuration file was not generated or failed to load? A: The configuration file will be automatically generated when the plug-in is started for the first time. If the file loading fails, the plug-in will load the default configuration and output an error log in the console. Q: How to modify the plug-in configuration? A: You can edit the BattleReplay.json file manually or use the /setbattleconfig command to dynamically modify the settings. Q: Does the plug-in support recording multiple battles at the same time? A: The plug-in will limit the number of simultaneous recordings (the default is 5) to prevent performance problems. If the coordinates of the players participating in the battle, the plug-in will give priority to the recorded content.

Troll those cheaters in style with the Rocket Man ! After exploding up in the sky their loot will drop all over the place, just like a Piñata. Use the chat command /troll.rocketman <player> or the rcon command troll.rocketman <player>. The player argument will accept a partial player name or a full Steam ID. All users with the Oxide "admin" role will get access to the command, but you may grant per user/group access using the permission oxidationtrollrocketman.use.

Advanced graphical permissions manager to easily manage player and group permissions. Features Assign/Revoke player permissions Assign/Revoke player groups Assign/Revoke group permissions Create, rename, clear and delete groups Convenient overview of given permissions per plugin Hierarchical wildcard permissions Back button for quick navigation Search/Filter function Intuitive UI No plugin dependencies Commands (Chat and Console) gperms - Opens/Closes the UI Permissions Administrators don't need any permission Players can be given access with the provided permissions: 'gperms.use' - Open the GUI (readonly, but needed for any action in GPerms) 'gperms.players' - Grant/Revoke player permissions 'gperms.playergroups' - Assign/Remove players from groups 'gperms.groups' - Grant/Revoke group permissions 'gperms.modifygroups' - Create, edit and delete groups Hints Directly granted permissions will be checked as green Inherited group permissions will be checked as blue To revoke all permissions of a plugin click the 1 level wildcard permission twice (grant all -> revoke all) Configuration perms.hidepluginprefix (true/false) - if set to false, the full permission names will be shown plugins.showwithoutpermissions (true/false) - If set to false, plugins without permissions wil be hidden players.showoriginalnames (true/false) - If set to true, the original playername will also be shown uicolor.primary (rgba) - The primary accent color uicolor.disabled (rgba) - The disabled buttons color uicolor.activetab (rgba) - The active tab color

Advanced graphical plugin manager to easily manage plugins. Features Load/Unload plugins Unloaded plugins are unloaded permanently (not reloading after restarts) Convenient error lookup for not loading plugins Intuitive and super responsive UI (no lag for small UI changes and no mouse reset) Search/Filter function Back button for quick navigation No plugin dependencies Commands (Chat and Console) gplugins - Opens/Closes the UI gplugins.load <pluginname> - Loads the given plugin and removes it from the disabled plugins list gplugins.unload <pluginname> - Unloads the given plugin and adds it to the disabled plugins list Permissions Administrators don't need any permission Players can be given access with the permission 'gplugins.use' (for UI and commands) Hints Clicking the exclamation mark icon will show the error message at the bottom The disablement of plugins after restarts will not work if gplugins is not loaded Loading a plugin in any way other then gplugins when it is disabled in gplugins will not work Configuration uicolor.primary (rgba) - The primary accent color uicolor.disabled (rgba) - The disabled buttons color

Admin Tools is an all-in-one plugin designed to make your job as a server owner/admin easier. This plugin has a wide range of features and commands that allow you to control your server easily, both in-game and via Discord. It also adds custom quality of life features exclusive to this plugin! ★ Inventory Viewing System - View an NPC or player's inventory in Discord and in-game ★ Multi-Server Support - Allows you to manage multiple Rust servers from a single bot ★ Custom Combatlog System - View a player's combatlog in Discord and in-game ★ Backpack Viewing System - View a player's backpack (uMod plugin) in Discord ★ Custom ID System - Get the ID of players on your server quick and easy, copy directly from chat ★ Warn System - Inform players of their wrongdoings and keep track of them (Warn Visuals: UI, Chat, Chat + Toast/Gametip) ★ Watchlist System - Lets you put suspicious players on a list for you to monitor, logs in-game and to discord ★ Server Command System - Reload/load/unload plugins and other console commands in Discord and in-game ★ F7 Report Logging System - Log F7 reports to discord with their combat log attached (if enabled) ★ and more! (Rest of features below) (Changed/Exclusive): * Timestamps for video in video's description - Make sure to up video quality if watching from this site. * Timestamps for video in video's description - Make sure to up video quality if watching from this site. ★ Permission System - Grant/revoke permissions to groups and players from Discord and in-game ★ Minecraft Creative System - While enabled, hold middle click to get the item you're looking at ★ Rename System - Rename the players who think they are funny (toggle in config) ★ Tempban System - Tempban players with no database required ★ Unique ID System - Find players even when they have the same or similar names -- Thanks to nivex ★ Kill, Wound, Revive & Respawn System - Kill, wound (down), revive and respawn players from Discord and in-game ★ Team Viewing System - View a player's team members from Discord and in-game Q: How do I set up the bot? A: Set Up Instructions - If you miss any permissions, can always add them to the Admin Tools role in discord after you invite the bot. Q: Does this plugin link players to Rust? A: No. You can use the free plugin DiscordCore by MJSU if you would like to link your players. Q: Does this plugin log kills/PMs/F1 Spawn/chat? A: No. Admin Tools only logs the following if enabled: F7 Reports, Bans, commands from this plugin, and players who are watchlisted. You can always view a player's combatlog from discord though. You can use the free logging plugins DiscordLogger by MONoH or DiscordChat by MJSU depending on your goal. However, personally, I recommend against using logging functionality that would be occurring very frequently due to Discord's rate limiting. Though, DIscordLogger is made in a way that combines messages if possible to prevent limiting. Q: Can this log to multiple Discord servers? A: YES. All you need to put for logging to multiple servers is the channel ID you want to log to in the list of channel IDs in the config. Q: Does this plugin ONLY work with Discord Extension 3.0.0+? A: YES. You need to download the 3.0.0+ version from GitHub, it is linked at the top (and right here) as a required dependency. Any version prior to 3.0.0 will not work with this plugin, but any version 3.0.0 and later will. Q: Will this work on a shared hosting server? A: Yes, BUT you will not be able to take advantage of the threading done within the plugin. It should still work fine, but when you're on a shared host, you may only have access to a single core/thread (not positive on which) and as a result the threading I am doing in the plugin will just be ran on the main thread. As a result some of the discord functionality (ie: image generation) may affect the server as its now running on the main thread (what the server uses to run the game on) instead of a separate thread which would normally not affect the server. The image generation stuff (backpack and inventory) is normally pretty quick depending on number of items and pictures being used/sent, and can be between 100-250ms to generate on my server, however that was while no players were on. Q: How do I fix this error Response Code: Forbidden Discord Error Code: 50001 Discord Error: Missing Access ? A: All you need to fix this issue is MFA/2FA on the account used to create the bot. This issue is caused by Discord requiring your account to have either MFA or 2FA due to the bot being in a Community Discord server. After you add 2FA/MFA this error will go away. Q: Renaming isn't working, how do I fix this? A: The issue is likely that you don't have it enabled in the config, make sure to enable it in the config, its above the warning options and the discord API options. Q: My commands aren't appearing, how do I fix this? A: You can do the following in an attempt to try and force the bot to update its commands: Discord > Server Settings > Integrations > Admin Tools Bot > Toggle one of the checkboxes it shows in either Roles & Members or Channels > Save > Undo toggle > Save again. Q: Does this work with Rustcord? A: Yes, however you need this version here by MJSU as it has been updated to work with DiscordExtension 3.0.0+ versions. Q: How do I set up Multi-Server Support? A: Do as follows: Enable the bool (true/false) config option for multi-server system. Fill and keep the list of servers order the same if possible between configs (not required, but recommended). Use the /server command in discord to swap to the server you want to start listening to/sending commands to. On first use of command, it will error in all but one server console (tries to reply to a message more than once), that is expected and doesn't do that after that first command. It is used to set it up. If you want the activity information to change when swapping servers, make sure to enable that functionality in the config. Special thanks to Nivex for creating the method used to generate unique IDs. For support, please make a support ticket or join the Cobalt Studios Discord.

AI Translation plugin is the best powered-AI translation solution for Rust Servers. Enjoy the power of AI by automatically translating all your language files, or the messages exchanged by players in the chat! ALL languages, without exception, are accepted. !! Important: The plugin requires the use of OpenAI's API, which includes fees for each request (see the dedicated section for more details) !! Free Version : A free version (but limited) is available. Easy to Use with Minimal Configuration There is almost no setup required; everything is straightforward to handle. Open AI & Request Costs You need to register for the OpenAI API to retrieve a token. Signing up and getting the token is very simple and takes just a few seconds. Translating language files will only cost a few cents for about a hundred files. It's difficult to quantify the cost of translating chat; expect around $1 for thousands of translated messages (this is a purely theoretical value). Something to consider if your language files are long: It is possible that some files may arrive incomplete. To solve this issue, you need to increase the token limit of your model (in the configuration). The limit depends on the OpenAI model used, but generally, you can go up to 4096. More information on tokens can be found here. Support Available I am available for all your questions, whether it's support here or on Discord (d.0ne_) More information at the bottom of the page. Commands ait.translateplugin <plugin> <lang1> <lang2>: Requires the plugin to have a default language file (in English). Specify all desired languages in ISO639-1 format. Example: "ait.translateplugin MyPlugin fr ru" ait.translateallplugins <lang1> <lang2>: Operates the same way but will do so for all plugins. Permission aitranslationpro.chat.use: permission that allows users to see the translation in the chat OPEN AI API Registration (2mn): 1 - Visit the OpenAI Website: Go to OpenAI's official website. Click on the "API" section in the navigation menu. 2 - Create an Account: If you don’t already have an OpenAI account, you will need to create one. Click on the "Sign Up" button. Fill in your details such as email, name, and password. Follow any additional prompts to complete the registration process. 3 - Verify Your Email: Check your email for a verification link from OpenAI. Click on the link to verify your email address. 4 - Log in to Your OpenAI Account: Once your email is verified, log in to your OpenAI account. Navigate back to the API section. 5 - Apply for API Access: Depending on OpenAI's current policies, you might need to apply for API access. Fill out any required forms or surveys. Submit your application. 6 - Access the API Dashboard: Once approved, you can access the API dashboard. This dashboard is where you can manage your API usage. 7 - Generate an API Token: In the API dashboard, look for an option to create a new API token. Click on "Create Token" or a similar button. Follow the prompts to generate a new token. 8 - Secure Your Token: Once your token is generated, make sure to copy it and store it securely. Never share your API token publicly as it gives access to your OpenAI account.

Dynamic Warps - Teleportation Plugin for Rust | Plugin de teletransportacion para Rust ENGLISH Version: 1.0.0 Author: TSG_ERIC Description Dynamic Warps is a simple and efficient plugin for Rust servers that allows administrators with auth level 2 to manage teleportation points (warps). Players can easily access these warps, enhancing the overall server experience. Features Warp Management: Create, update, and remove teleportation points. Custom Delays: Set a waiting time before teleporting. Visual Effects: Optional animations when teleporting. Accessible Commands: Players can list and use warps effortlessly. ================================================================================ Main Commands Administrators (auth level 2): /warp create [name] → Create a warp at your current position. /warp set [name] → Update an existing warp's position. /warp remove [name] → Delete a warp. /warp time [name] [seconds] → Set a teleport delay for a warp. ================================================================================ Players: /warp list → Show the list of available warps. /[name] → Teleport to the selected warp. ================================================================================ Dynamic Warps is the perfect tool to enhance your Rust server gameplay, offering a balanced and easy-to-use teleportation system. Dynamic Warps - Plugin de Teletransporte para Rust ================================================================================================================================================================ ESPAÑOL Versión: 1.0.0 Autor: TSG_ERIC Descripción Dynamic Warps es un plugin sencillo y eficiente para servidores de Rust que permite a los administradores con auth level 2 gestionar puntos de teletransporte (warps). Los jugadores pueden acceder fácilmente a estos warps, mejorando la experiencia del servidor. ================================================================================ Características Gestión de warps: Crea, actualiza y elimina puntos de teletransporte. Retraso personalizable: Configura un tiempo de espera antes de teletransportarse. Efectos visuales: Animaciones opcionales al teletransportarse. Comandos accesibles: Los jugadores pueden listar y usar los warps fácilmente. ================================================================================ Comandos Principales Administradores (auth level 2): /warp create [nombre] → Crea un warp en tu posición actual. /warp set [nombre] → Actualiza la posición de un warp existente. /warp remove [nombre] → Elimina un warp. /warp time [nombre] [segundos] → Configura el retraso del warp en segundos. ================================================================================ Jugadores: /warp list → Muestra la lista de warps disponibles. /[nombre] → Teletranspórtate al warp seleccionado. ================================================================================ Dynamic Warps es la herramienta perfecta para mejorar la jugabilidad de tu servidor Rust, ofreciendo un sistema de teletransporte balanceado y fácil de usar. ================================================================================ YOUTUBE VIDEO ================================================================================ EXAMPLE OF CONFIGURATION FILE | EJEMPLO DE ARCHIVO DE CONFIGURACIÓN { "WarpList": { "example": { "x": -757.5041, "y": 2.30591822, "z": -184.441864 } }, "TeleportDelays": { "example": 5.0 }, "EnableTeleportAnimation": true } ================================================================================