Search the Community

Useful Rules Agreement Plugin. Allowing you to prevent players who do not agree with your rules from playing on the server. The ability to disable the use of the mouse, keyboard, commands, chat and voice chat until the player accepts your rules; The ability to request consent to the rules every time a player connect, or when the administrator uses a special command; The ability to request consent to the rules only once and only when the rules have been changed(date in the config file); The ability to limit the time given to make a decision, after which the player will be kicked or banned; The ability to set the number of rejections(in a row) after which the player will be banned; The ability to set an effect when opening the rules; The ability to set an effect when agreeing to the rules; The ability to enable or disable the agreement request for the rules; The ability to request agreement to the rules again using a command; The ability to customize the UI as desired(*SERVER*\oxide\data\RulesUi\). Several naming rules for elements must be followed, as explained below in the UI section; The ability to create as many pages of rules as desired(in the config file); It is not possible to agree to the rules until the player has read all the pages; The presence of 4 hooks for developers, 2 of which can be overridden. rules.ignore - Provides the ability to ignore rules agreements. rules.admin - Provides the ability to ignore rules agreements. Also includes the ability to use enable/disable and reask commands. { "Chat command": "rules", "Is it worth enabling GameTips for messages?": true, "Is it worth enabling a requirement for agreement with the rules? If disabled, the rules will not be displayed": true, "Date of the last rules update. Format: yyyy-MM-dd HH:mm": "2024-10-24 13:44", "Is it worth asking for agreement with the rules every time? If disabled, consent will only be requested again if the rules have been updated": false, "Is it worth preventing a player from using chat until they agree to the rules?": true, "Is it worth preventing a player from using commands until they agree to the rules?": true, "Is it worth preventing a player from using voice chat until they agree to the rules?": true, "Is it worth requesting agreement from all active players with the rules after the plugin is (re)loaded or enabled?": true, "Time in seconds(0-600) given to the player to respond, after which they will be kicked/banned from the server. A value of 0 disables the time limit": 0.0, "Number of rejections(in a row) of the rules after which the player will be banned. A value of 0 disables the ban": 5, "Number of rules pages. Will automatically add additional language keys if they are missing": 4, "Additional languages for key generation(except en and ru)": [ "" ], "Prefab name for the effect when requesting agreement with the rules. Leave empty to disable": "assets/bundled/prefabs/fx/invite_notice.prefab", "Prefab name for the effect upon agreement with the rules. Leave empty to disable": "assets/prefabs/misc/xmas/advent_calendar/effects/open_advent.prefab", "Width of the container for the rules text, needed for scroll view calculation": 600.0, "Height of the container for the rules text, needed for scroll view calculation": 375.0, "Version": { "Major": 0, "Minor": 1, "Patch": 4 } } EN: { "RulesNotFound": "Argument {0} not found!", "RulesAccepted": "Thank you for accepting our terms! Enjoy the game!", "RulesAcceptNotRead": "You haven't read all the pages!", "RulesEnabled": "The requirement to agree with the rules is enabled!", "RulesDisabled": "The requirement to agree with the rules is disabled!", "RulesAlreadyEnabled": "The requirement to agree with the rules is already enabled!", "RulesAlreadyDisabled": "The requirement to agree with the rules is already disabled!", "RulesOnce": "A one-time request for agreement with the rules is enabled!", "RulesEveryTime": "A one-time request for agreement with the rules is disabled!", "RulesReAsk": "All players have been sent a request for agreement with the rules, depending on the settings.", "KickReason": "You have been kicked because you declined our rules!", "BanReason": "You have been banned because you declined our rules {0} times in a row!", "PanelTitle": "Terms Of Service", "PanelLastUpdate": "Last updated on <color=brown>{0} {1}, {2}</color>", "BtnAccept": "Accept", "BtnDecline": "Decline", "BtnNextPage": ">", "BtnPreviousPage": "<", "January": "January", "February": "February", "March": "March", "April": "April", "May": "May", "June": "June", "July": "July", "August": "August", "September": "September", "October": "October", "November": "November", "December": "December", "Rules_1": "<b>1. Information</b>\n\n<b>1.1</b> - Lack of knowledge of the rules does not exempt you from responsibility.\n<b>1.2</b> - By playing on the server, you automatically agree to all the rules listed below.\n<b>1.3</b> - If you have already been caught using cheats/macros or exploiting on another server/project, and there is proof against you, we reserve the right to ban you without further investigation.\n<b>1.4</b> - The administration determines the punishment for a player based on the severity of the violation and the circumstances. Violators may receive a warning or a permanent ban (there is no temporary bans). Bans apply to all servers within the project.\n<b>1.5</b> - The administration does not compensate for in-game items lost due to your errors, technical server/hosting issues, game bugs, or contact with rule violators.\n<b>1.6</b> - The administration does not interfere in player-to-player relationships. You are solely responsible for the people you choose to play with, so if a player deceives you, there will be no punishments for them from us.\n<b>1.7</b> - You are responsible for all your accounts. If one account is banned, the ban applies to all your accounts. The same applies if one of your accounts has a game ban (EAC).\n<b>1.8</b> - Impersonating a member of the server's administration is prohibited.", "Rules_2": "<b>2. Gameplay</b>\n\n<b>2.1</b> - It is prohibited to use/store/purchase/distribute third-party software or any other means that provide an advantage over other players.\n<b>2.2</b> - Using cheat services is forbidden.\n<b>2.3</b> - Exploiting game bugs is not allowed.\n<b>2.4</b> - Exceeding the player limit in a team is prohibited:\n<b>+</b> Alliances or truces with other players are not allowed if the total number of players involved exceeds the server's limitations;\n<b>+</b> Frequent changes of allies will be considered a rule violation, as will playing with another player while your teammate is AFK or not nearby;\n<b>+</b> Changing teammates temporarily is not allowed if the replaced teammate intends to continue playing with you;\n<b>+</b> Changing a partner is allowed if your previous partner will not be in contact with you in the future.", "Rules_3": "<b>3. In-Game Chat/Voice Chat</b>\n\n<b>3.1</b> - Discussion of politics, religion, immoral, and other inappropriate topics is prohibited.\n<b>3.2</b> - Inciting national, racial, or religious hatred or insulting other players and individuals is forbidden.\n<b>3.3</b> - Posting links to third-party services and websites in the chat is not allowed.\n<b>3.4</b> - Spamming (repeatedly posting meaningless phrases or characters) or sending identical messages in a short period of time is prohibited.\n<b>3.5</b> - Selling or pretending to sell cheats/macros is not allowed.\n<b>3.6</b> - Proposing actions that lead to an unwanted server exit is prohibited. Such actions include, for example, pressing <b>alt+f4</b>, typing <b>disconnect</b> in the console, and similar actions whose meanings other players may not be aware of.\n<b>3.7</b> - The administration reserves the right to mute or block a player in the chat if they behave inappropriately or disrespectfully towards other players.\n<b>3.8</b> - Selling/buying in-game items for real currency, crypto or skins is prohibited.", "Rules_4": "<b>4. In-Game Check</b>\n\n<b>4.1</b> - In-Game checks are conducted exclusively through the <b>Discord</b> program. Every player on our project must have the ability to access it for the purpose of undergoing in-game checks.\n<b>4.2</b> - Calls for in-game checks are made only through in-game notifications and never through voice or text chat.\n<b>4.3</b> - If a player leaves the server, ignores a in-game check, or refuses to participate in it, they will immediately receive a ban.\n<b>4.4</b> - Clearing your PC before a in-game check is prohibited.\n<b>4.5</b> - Refusal to provide the necessary information for the in-game check or inappropriate behavior will result in a ban.\n<b>4.6</b> - If a player is banned as a result of a in-game check (including bans for refusal, ignoring, leaving the server, and providing incorrect contact information), their entire team will also be banned.\n\n<b>+</b> You have the full right to refuse to undergo a in-game check, but in this case, you and your allies will be banned.\n<b>+</b> Leaving the server, providing incorrect contact information, and ignoring the in-game check will also be considered a refusal.\n<b>+</b> If you agree to undergo the in-game check, you automatically allow the administration to install third-party programs necessary for checking your PC(e.g., AnyDesk, RCC, etc.).\n\n<b>Appeal Process</b>\nOne month after the ban, you have the ability to submit an appeal, but only if the ban was not for cheats or macros.\nAppeals can be submitted on our website." } RU: { "RulesNotFound": "Аргумент {0} не найден!", "RulesAccepted": "Спасибо, что приняли наши условия! Приятной вам игры!", "RulesAcceptNotRead": "Вы не прочли все страницы!", "RulesEnabled": "Требование согласия с правилами включено!", "RulesDisabled": "Требование согласия с правилами выключено!", "RulesAlreadyEnabled": "Требование согласия с правилами уже включено!", "RulesAlreadyDisabled": "Требование согласия с правилами уже выключено!", "RulesOnce": "Однократный запрос на согласие с правилами включен!", "RulesEveryTime": "Однократный запрос на согласие с правилами выключен!", "RulesReAsk": "Всем игрокам в зависимости от настроек был отправлен запрос на соглашение с правилами.", "KickReason": "Вы были исключены, так как вы отклонили наши правила!", "BanReason": "Вы были заблокированы, так как вы в {0} раз подряд отклонили наши правила!", "PanelTitle": "Условия использования", "PanelLastUpdate": "Последнее обновление <color=brown>{1} {0} {2} года</color>", "BtnAccept": "Принимаю", "BtnDecline": "Отказываюсь", "BtnNextPage": ">", "BtnPreviousPage": "<", "January": "Января", "February": "Февраля", "March": "Марта", "April": "Апреля", "May": "Мая", "June": "Июня", "July": "Июля", "August": "Августа", "September": "Сентября", "October": "Октября", "November": "Ноября", "December": "Декабря", "Rules_1": "<b>1. Информация</b>\n\n<b>1.1</b> - Не знание правил не освобождает Вас от ответственности.\n<b>1.2</b> - Играя на сервере Вы автоматически соглашаетесь со всеми нижеперечисленными пунктами правил.\n<b>1.3</b> - Если Вы уже были замечены с читами/макросами или использованием просвета на другом сервере/проекте и на вас есть пруфы - мы имеем право забанить Вас без проверки.\n<b>1.4</b> - Администрация сама выбирает наказание для игрока в зависимости от степени нарушения и обстоятельств. Нарушитель может получить как предупреждение, так и перманентный бан(временных блокировок нет). Блокировка выдаётся на всех серверах проекта.\n<b>1.5</b> - Администрация не компенсирует игровые ценности, утраченные по причине вашей ошибки, технических проблем на сервере/хостинге, багов игры или контакта с нарушителями.\n<b>1.6</b> - Администрация не вмешивается во взаимоотношения игроков, за тех с кем вы играете ответственны только Вы, поэтому в случае если игрок вас обманет — ему ничего за это не будет.\n<b>1.7</b> - Вы несете ответственность за все свои аккаунты. Получив бан на одном аккаунте - Вы получите его и на остальных аккаунтах. То же самое будет если на одном из ваших аккаунтах имеется игровая блокировка(EAC).\n<b>1.8</b> - Запрещено выдавать себя за члена Администрации сервера.", "Rules_2": "<b>2. Геймплей</b>\n\n<b>2.1</b> - Запрещено использовать/хранить/приобретать/распространять стороннее ПО или любые другие средства, позволяющие получить преимущество над другими игроками.\n<b>2.2</b> - Запрещено использование услуг читеров.\n<b>2.3</b> - Запрещено использование багов.\n<b>2.4</b> - Запрещено превышать лимит игроков в команде:\n<b>+</b> Нельзя устраивать альянсы или перемирия с другими игроками если в сумме вас больше, чем указано в ограничениях сервера;\n<b>+</b> Частая смена союзников будет считаться за нарушение правил, тоже самое касается и игру с другим игроком пока тиммейт стоит афк или не находится рядом;\n<b>+</b> Запрещена смена союзников на время, если заменяемый союзник продолжит с вами играть;\n<b>+</b> Разрешено сменить напарника, если ваш предыдущий напарник в дальнейшем не будет с вами контактировать.", "Rules_3": "<b>3. Игровой Чат/Голосовой чат</b>\n\n<b>3.1</b> - Запрещено обсуждение политики, религии, аморальных и прочих неуместных тем.\n<b>3.2</b> - Запрещено разжигание национальной, расовой или религиозной ненависти или оскорбления других игроков и других людей.\n<b>3.3</b> - Запрещены ссылки в чате на сторонние сервисы и сайты.\n<b>3.4</b> - Запрещен флуд(многократное повторение бессмысленных фраз, символов) или многократное отправление одинаковых фраз за короткий промежуток времени.\n<b>3.5</b> - Запрещено продавать или делать вид что вы продаёте читы/макросы.\n<b>3.6</b> - Запрещено предлагать сделать действия, приводящие к нежеланному выходу с сервера. К таким действиям относится например нажатие <b>alt+f4</b>, прописывание <b>disconnect</b> в консоль и прочие подобные действия, о значении которых другие игроки могут не знать.\n<b>3.7</b> - Администрация оставляет за собой право выдать мут или заблокировать игрока в чате если тот ведёт себя неадекватно или некорректно по отношению к другим игрокам.\n<b>3.8</b> - Запрещена продажа/покупка игровых ценностей за реальную валюту, крипту или скины.", "Rules_4": "<b>4. Игровая проверка</b>\n\n<b>4.1</b> - Проверки проходят только через программу <b>Discord</b>. Каждый игрок на нашем проекте, в обязательном порядке должен иметь возможность зайти в нее для прохождения проверки.\n<b>4.2</b> - Вызов на проверку осуществляется только через игровое оповещение и ни в коем случае не через голосовой или текстовый чат.\n<b>4.3</b> - Если игрок покинул сервер, проигнорировал проверку или отказался от неё, то он сразу получает блокировку.\n<b>4.4</b> - Запрещено чистить ПК перед проверкой.\n<b>4.5</b> - За отказ показывать нужную для проверки информацию или неадекватное поведение — вы будете заблокированы.\n<b>4.6</b> - Если по итогу(итогом считается и блокировка за отказ / игнор / выход из сервера и предоставление некорректных данных для связи) проверки игрок блокируется, то и вся его команда блокируется вместе с ним.\n\n<b>+</b> Вы имеете полное право отказаться проходить проверку, но в этом случае Вы и ваши союзники будут заблокированы.\n<b>+</b> Так же отказом от проверки будет считаться выход с сервера, предоставление некорректных контактных данных и игнорирование проверки.\n<b>+</b> Если Вы согласны пройти проверку - то автоматически разрешаете устанавливать сторонние программы нужные администрации для проверки вашего PC(AnyDesk, RCC и т.д).\n\n<b>Возможность разблокировки</b>\nЧерез месяц после блокировки можно подать апелляцию, но, только в случае если бан был получен не за читы или макросы.\nАпелляцию можно подать на нашем сайте." } show - Opens the rules panel. enable - Enabling Rules agreements. Permission "rules.admin" required. disable - Disabling Rules agreements. Permission "rules.admin" required. once - Enabling/disabling one-time agreement request for the Rules. Permission "rules.admin" required. reask - Reasking all players for the Rules agreement. Permission "rules.admin" required. Example: /rules show /rules enable You can customize the UI as you like(*SERVER*\oxide\data\RulesUi\). However, the following containers must always be present and their names must remain unchanged(you can change the parent, position, layout of the elements, etc.), as they are referenced by name: The name of the main container is "RulesUi"; The name of the container for title texts(header and update date) is "RulesUi_Panel_Title_Text"; The name of the container for the "Next Page" button is "RulesUi_Panel_Title_Pagination_Next"; The name of the container for the "Previous Page" button is "RulesUi_Panel_Title_Pagination_Previous"; The name of the container for the rules text is "RulesUi_Panel_Content"; The name of the container for the progress indicator is "RulesUi_Panel_Content_Progress"; The name of the container for the "Decline" button is "RulesUi_Panel_Footer_Decline"; The name of the container for the "Accept" button is "RulesUi_Panel_Footer_Accept". RulesEnabled: Called after the rules are enabled or the plugin is loaded with enabled config. RulesDisabled: Called after the rules are disabled or the plugin is unloaded. RulesAccepted: Called after the player has accepted the rules; Returning a non-null value overrides default behavior. RulesDeclined: Called before kicking or banning a player; Returning a non-null value overrides default behavior. void RulesEnabled() { Puts("The rules were enabled!"); } void RulesDisabled() { Puts("The rules were disabled!"); } object RulesAccepted(IPlayer player) { Puts($"Player {player.Name} has accepted the rules!"); return null; } object RulesDeclined(IPlayer player, int declines, int ban_attemps) { Puts($"Player {player.Name} has declined the rules! This is the {declines} declines out of {ban_attemps}!"); return null; }

Introducing MLRSC4 – The Rust Plugin That Turns the MLRS Wagon into an Explosive Hotspot! MLRSC4 offers a simple yet brilliant solution for server administrators looking to regulate access to Rust's Multiple Launch Rocket System (MLRS) in a fun and engaging way. This plugin ensures that players who enter the MLRS wagon and have the required permission will automatically have C4 spawned on them, set to explode after a predefined delay. Key Features: Automatic C4 Spawning: For players with the special permission "mlrsc4.use" who enter the MLRS wagon, C4 is automatically placed on them. Customizable Explosion Delay: Administrators can set the timer for the C4 explosion, giving them full control over when the boom happens. Simple Configuration: MLRSC4 makes it easy to decide who gets access to the MLRS and who gets a surprise explosive welcome if they attempt to use the system. Benefits of MLRSC4: Perfect for servers looking for a creative way to control MLRS usage, this plugin adds a layer of strategic planning and turns accessing the MLRS wagon into a risky yet fun endeavor. MLRSC4 is ideal for making players think twice before entering the wagon, while still providing an entertaining experience for everyone involved. Flexible Usage Options: What makes MLRSC4 stand out is its versatility. You can use the plugin in two ways: Increase the Thrill: By extending the time until explosion, you give players a chance to experience the thrill of launching rockets under pressure, with the possibility of succeeding in time. Prevent Usage: Set the timer very short to prevent the use of MLRS rockets outright. Players who enter the wagon will "go boom" immediately, serving as an effective deterrent against unauthorized use. Make the MLRS wagon an unforgettable part of your Rust server with MLRSC4. Get the plugin now and let the sparks (and C4s) fly – choose how you want to shape the gameplay! Lang-File: English and German included Config: { "NumberOfC4": 5, // The number of C4 charges that will automatically spawn when a player with the required permission enters the MLRS wagon. "ExplosionDelay": 10.0, // The delay in seconds before the spawned C4 charges explode. "Permission": "mlrsc4.use", // The permission a player must have to avoid being affected by C4 when entering the MLRS wagon. "ShowMessage": true // Determines whether a warning message is displayed when C4 is spawned and set to explode. }

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

SmartWarnings Lite simplifies and streamlines your server moderation by providing means to consistently Warn your players for misconduct. Gone are the times when you leave manual notes at sleeping players, for this plugin creates a smooth but intimidating chat warning displaying clearly to the player what they've done wrong and how to learn from it. Rule enforcement has never been easier before. If you enjoy the Free lite version of the plugin, please consider supporting the developer by upgrading to the Full version. In return you get many more useful features & fast developer support, it's a win-win. Link here: https://codefling.com/plugins/smart-warnings Commands /warn (player name or id) "reason" Dispatches a warning with a custom reason or presetRequires permission: smartwarnings.admin /warn info (player name or id, leave blank to see your own) Shows the amount of warnings, warning points and the individual warning details in chat.Requires permission: smartwarnings.admin to see other players. Default permission can only see their own warnings. /warn clear (player name or id) (id or ALL) Clear a specific warning ID by specifying the warning number, or specify ALL to clear all player warnings. Requires elevated permission: smartwarnings.admin.canclear Below command is only supported in the full version /warn clan (clan tag) "reason" Dispatches a warning with a custom reason or preset to an entire clan (Requires Clans plugin)Requires permission: smartwarnings.admin Configuration { "System Settings": { "Max Warnings": 5, "Default Warning Expiration time (Days)": 7, "Announce Warnings in Global Chat": true, "Show players who issued the warning": true, "Server Name": "MyRustServer", "Clear all Warnings on Server Wipe": true }, ////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////// ///// Below configuration is only supported in the full version @ https://codefling.com/plugins/smart-warnings ////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////// "Warning Presets": { "spam": { "Reason": "§1 - Spamming", "Points": 1, "ExpirationDays": 3.0 }, "toxic": { "Reason": "§2 - Toxic behaviour", "Points": 2, "ExpirationDays": 7.0 } }, "Autoban Settings": { "How many points until automatic ban (Set 0 for Disable)": 0, "How many warnings until automatic ban (Set 0 for Disable, Recommended: Same as Max Warnings)": 0, "How long to ban in minutes (Set 0 for Permanent)": 2880, "Clear the players Warnings on AutoBan (Default: True)": true }, "Discord Settings": { "Webhook URL - Post Warnings to Discord (Leave blank to Disable)": "", "Webhook URL - Post Autobans to Discord (Leave blank to Disable)": "" }, "AutoMod Settings": { "Mute on 2 warning points": { "PointTrigger": 2, "ExecuteCommand": "mute {0} {1}", "ClearPointsOnTrigger": false }, "Kick on 4 warning points": { "PointTrigger": 4, "ExecuteCommand": "kick {0} {1}", "ClearPointsOnTrigger": true } } } SmartWarnings Full vs Lite Below are the additional features provided by the full version of the plugin. Warn entire clans using /warn clan No need to dispatch a warning to every individual player if the whole clan has been misbehaving. The full version integrates with Clans. Create custom presets for common violations Presets can be made for example to reflect the server rules, it can be configured so that your admins can type /warn joe rule1 and it will spell out the entire rule 1 in the warning. Presets can have an Expiration date which will remove the warning, allowing non-repeating offenders to be cleared if they're well behaving in the long term. Presets can have a Warning Point weight which will give them different severity that can influence when to trigger an Automatic Ban (if enabled). Automatically Ban players with X amount of Warnings or Warning Points With this feature Enabled a player will be Automatically Banned when reaching the configured Warning amount or Warning Points. For example, configure 3 warnings to be max and enable auto ban will ban a player when the third warning has been dispatched. Supports Temporary Autobans If you're the kind of type that believes in second chances, when configured it bans the player lets them know when they're welcome back! Optional feature: Clear the player's warning when autobanned (True by default), This can conveniently be set to False if you want the player to be instantly auto banned next time a warning is dispatched. Extensive Logging both File based and Discord Configure Discord Webhook links to log Warnings and/or Autobans to Discord. Customizable Branding GUI-popup warning with Server Logo branding AUTOMOD: Fully customizable command actions on X warning points Define any custom command to be executed at X warning point. This allows you to integrate with any other plugin for example mute, jails or whatever really. For example: set to mute on 2 warning points, kick on 4 warning points, teleport to jail on 6 warning points.