MON@H

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 the limitentities.list console command. There are three types of limits available: global, building, and radius. For building limit checks, if a cupboard is placed, the limits of the cupboard owner will apply. If no cupboard is present, the restrictions of the first block's owner will be used. When you run the plugin for the first time, no players will be restricted. To apply limits, you must assign one or more permissions from your config file to a player or group. The plugin also tracks permission changes, so you won't need to restart it after granting a player new permissions or adding them to a VIP group, for example. This plugin is designed to be efficient and performant, even on heavily loaded servers. The plugin now supports Entity Groups, and group names are translatable. All newly created groups are automatically added to the language files when the plugin loads. You can create as many groups as you like or remove them entirely. Just keep in mind that if you add an entity to a group, you cannot also add it to Limits Entities — you must use the Group name instead. Extended Power Lights (Deluxe Christmas Lights) support has been added: a new group of limits is now included in the config. The default values are set to -1, meaning no limits. Adjust them according to your needs. Radius Limits allow you to restrict the number of specific entities within a certain radius. This feature is designed for static deployable entities (like turrets or lights) and helps prevent spam placement in concentrated areas. Note: Radius limits only work for static entities (entities that don't move after placement). This feature can be resource-intensive if used with very large radius values or too many entities, so use it judiciously. Note: If you want to have "beautiful" names even on English only, please, install Rust Translation API plugin or you will have 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 Advanced radius-based limiting system for area control