MON@H

Tired of someone shooting into your players face on your PVE server? While it deal no damage it may lead to fps loss and be really annoying. This plugin will help you to punish them. The main idea of the plugin is to punish a player attacking another. There is variety of options in config file. You need to decide what exactly you want to do with attackers to punish them. Plugin will count every hit attacker made to another player. More hits - heavier punishment, because hits counter serves as multiplier. There are 4 thresholds by number of hits attacker made: The number of hits allowed without punishment The number of hits before death is used as a punishment The number of hits before kick is used as a punishment The number of hits before ban is used as a punishment Start with setting a number of hits you may allow do deal without punishment. Notifications to stop attacking players still appear (if enabled in config). Then set initial percentage of damage that attacker will get back. For example, by default it set to 0.5, so if attacker hits another player and dealt 30 hp damage he will get 50% back = -15 hp. Additionally ServerRewards RP will be discounted (if enabled in config) by formula: Initial server reward RP amount * The number of hits attacker made. After reaching death as punishment threshold punishment include death. After reaching kick as punishment threshold punishment include kick (if enabled in config) and additionally ZLevelsRemastered levels skills amount may also be taken (if enabled in config). After reaching ban as punishment threshold punishment include ban (if enabled in config). There are 2 ways to inflict damage on an attacker - using the slap plugin (if activated in config and loaded) or simply by taking away health. Here is an example of how this plugin works with default thresholds values (5, 10, 15) and Initial percentage damage (0.5) with 50 hp damage dealt by each shot. So by default, first threshold is 5 hits without punishment. Every hit attacker made he gets notification to stop attacking players. If player will continue hitting another player and reach first threshold 5 hits, on 6th hit he will get punishment: -25 hp (-50 hp, -75 hp and so on) and -100 RP (-200 RP, -300 RP and so on). If player will continue hitting another player and reach second threshold 10 hits, on 10th hit and every hit afterwards he will get punishment: death. If player will continue hitting another player and reach third threshold 15 hits, on 15th hit and every hit afterwards he will get punishment: kick and -10 levels skills in ZLevelsRemastered. You may also change time (5 minutes default) after which hits number will be cleared and count will start from scratch. Zone Manager support. If ZoneManager include mode is set to true, only attackers in specified zones will be punished. If set to false, only attackers outside specified zones will be punished. As a bonus, this plugin may help to solve several other problems: Protect personal growables from being damaged by other players Protect personal vehicles from being damaged by other players Prevent any fireball damage There is a problem with fireball damage in rust - you can't detect the author of this type of damage. So there is no way to know whose fireball is attacking target. This type of damage is dealt only by incendiary bullets. So to prevent players from abusing this you may want to disable incendiary bullets damage entirely. ## Permissions punishattacker.use -- give player/group this permission to activate punishment system for them punishattacker.immunity -- allows player to be ignored by punishment system ## Commands This plugin provides no commands ## Configuration Enable / disable notifications / logging Set SteamIDIcon steamid to set desired account icon in chat messages Enable / disable modes/plugins support ## Localization Out of the box plugins phrases are available on : English, Russian and Ukrainian { "Format.Prefix": "<color=#00FF00>[PunishAttacker]</color>: ", "Punishment.Damage": "Attacking other player punishment damage: <color=#FFA500>{0}</color>", "Punishment.Ban": "Banned for continuously attacking other player", "Punishment.Kick": "Kicked for continuously attacking other player", "Punishment.Kill": "<color=#FFA500>{0}</color> was attacking <color=#FFA500>{1}</color> and was punished", "Warning.First": "Stop attacking players or you will be punished!", "Warning.Second": "Stop attacking players or you will be killed!", "Warning.Third": "Stop attacking players or you will be kicked!", "Warning.Fourth": "Stop attacking players or you will be banned!" } Log file example:

Tired of dying from "bots-cheaters" shots? Can't handle Bradley / Heli? Use life support to stay alive! If enabled and player has needed amount of currency - life support will heal player to maximum health instead of being dead. The most valuable thing is you keep your items and don't need to go and find your dead body. Also it can be very handy in the battle with very hard opponents (like bot-boss, Higher tier Bradley/Heli etc.) This plugin supports both Economics and ServerRewards plugins. You may set price for both of them or just any you like. If both prices are set - plugin will try to use RP's first and if there will be not enough - it will check for Coins. After you set everything up in your config file and give all permissions to all players/groups plugin will track for changes automatically, so if some player will be added to VIP for example or upgraded to Elite plugin will apply changes automatically without need to reload plugin. If you will edit config file you still will need to reload plugin. By default, life support is allowed on the entire map. If you want to restrict the use of life support, you must enable the desired options in the config file. Using cupboard so as ZoneManager zones are supported in 2 different modes: Include mode will only allow players to use life support inside specific zones/cupboard range. Exclude mode will prevent players from using life support inside specific zones/cupboard range. When cupboard range is checked, team / friend / clan members are checked automatically if enabled in config file and the required plugin is installed. It means members of team / friend / clan cupboard = players cupboard. This is handy if you want to strict players to use life support only inside cupboard range or you want to allow use it everywhere except cupboard owned by other players. ## Permissions lifesupport.blocked -- Prevents player from using plugin (Has the highest priority among other permissions) More permissions with costs and cooldown are created in config file (see Configuration section below) ## Commands This plugin provides both chat and console commands using the same syntax. When using a command in chat, prefix it with a forward slash: `/` /ls | /lifesupport - Toggle using of life support ## Configuration You can remove unnecessary default permissions and also add as many permissions as you want. For cases where the player has more than one, the permission with the higher priority will be applied. Enable / disable notifications / logging Set SteamIDIcon steamid to set desired account icon in chat messages Set commands list (default are "ls", "lifesupport") Enable / disable modes/plugins support ## Localization Plugins phrases are available on 3 languages out of the box: English, Russian and Ukrainian { "Error.NoPermission": "You do not have permission to use this command!", "Format.Coins": "Coins", "Format.Disabled": "<color=#B22222>Disabled</color>", "Format.Enabled": "<color=#228B22>Enabled</color>", "Format.Free": "free", "Format.Prefix": "<color=#00FF00>[LifeSupport]</color>: ", "Format.RP": "RP", "Info.LifeSaved": "Your life saved. Cost = <color=#FFA500>{0} {1}</color>", "Info.LifeSupport": "LifeSupport is now {0}" } ## API ### Developer Hooks CanUseLifeSupport Called when a player is about to die (or get into wounded state if enabled in options). Returning a non-null value (true is default) will prevent life support activation object CanUseLifeSupport(BasePlayer player) Example of hook usage to prevent player from life saving private object CanUseLifeSupport(BasePlayer player) { if (playerList.ContainsKey(player.userID)) { return true; } return null; } There is a free version on uMod, why do you even need this plugin? First of all, this plugin was designed to be efficient and performant. It uses unique caching system that should not consume no additional server resources Much more options and plugins native support Any plugin support will be added if requested

The purpose of this plugin is to restrict the entities that players can build. You can limit any entity based on its prefab. To get the full list of supported prefabs use limitentities.list console command. There are two types of limits available: global and building. For building limit checks, if a cupboard is placed, the limits of the cupboard owner will apply. If no cupboard is placed, the restrictions of the owner of the first block will apply. When you run the plugin for the first time, no players will be limited. To apply limits, you must assign one or more permissions from your config file to a player/group. The plugin also tracks permission changes, so you will not need to restart the plugin after giving a player new permission or adding them to a VIP group, etc. This plugin is designed to be efficient and performant even on highly loaded servers. This plugin now supports `Entity Groups`, and group names are translatable. All newly created groups are added to the language files on plugin load. You are free to create as many groups as you want or remove them all. The only thing you should keep in mind is that if you added an entity to a group, you can't add the same entity to `Limits Entities`, you must use the `Group name`. Extended Power Lights (Deluxe Christmas Lights) support added: there is a new group of limits added into config. Defaults are -1, means no limits. Set it according to your needs. Note: If you want to have "beautiful" names even on English only, please, install Rust Translation API plugin or you will have a short prefab names only. ## Permissions limitentities.immunity -- Allows player to not being limited by this plugin limitentities.admin -- Allows player to check other player limits and execute console command More permissions with limits are created in config file (see Configuration section below) ## Commands /limits <player name | steamid> (optional) -- Get current limits list for a player. If player doesn't have admin permission or player name/id is empty - current player limit will be shown limitentities.list (console only) - print all tracked prefabs list into log file. Requires admin rights (can be used in server console/RCON) ## Configuration You can remove unnecessary default permissions and also add as many permissions as you want. For cases where the player has more than one, the permission with the higher priority will be applied. Note: For better performance, grant permissions only to players you want to limit, or use an immunity permission to disable limits entirely. Enable or disable notifications and logging. Set the Building Detection Range to be used when a building is not specified (e.g., not a decay entity). Do not set this value too high — it may significantly impact performance! Enable or disable tracking (and limiting) for Power Lights (Deluxe Christmas Lights). Enable or disable tracking (and limiting) for Growable Entities. Set the SteamIDIcon to a specific SteamID to customize the account icon in chat messages. Define the commands list (defaults are limits and limit). Set the percentage (%) at which limit notifications appear. If set to 0, notifications will only show when the limit is reached. Add entity prefab names to the Excluded List to make the plugin completely ignore those prefabs. Enabling Prevent Excessive Merging of buildings may affect performance, so use it at your own risk! Use Entity Groups to combine entities and set a shared limit for the entire group. Note: The same entity cannot be listed in both Group Entities and Limits Entities at the same time. ## Localization Plugins phrases are available on 3 languages out of the box: English, Ukrainian and Russian Plugin supports Rust Translation API which allows you to have entities names on any language Rust supports There is a free version on uMod, why do you even need this plugin? First of all, this plugin was designed to be efficient and performant. It uses unique caching system that should not consume no additional server resources Much more efficient building limit control system even without cupboard placed More accurate mechanism for notification messages Allows you to prevent entities placement if limit is set to 0 Supports Rust Translation API so you can have full support of any language Rust supports Supports Entity Groups ! Supports checks to prevent excessive merging of buildings Supports Abandoned Bases plugin Supports advanced limits for Power Lights (Deluxe Christmas Lights) Supports setting advanced building detection range