Search the Community

The Offline Raid Protection plugin is a comprehensive solution designed to protect players' structures and vehicles while they are offline. It offers a range of customisable protection levels based on real-time or the length of time a player has been offline, and integrates with the Clans plugin and the in-game teams feature to determine protection status based on the online status of all clan or team members and authorised players. Key Features Configurable Protection Levels: Set protection levels based on real time or the amount of time since a player went offline. For example, a building can have 100% protection one hour after a player goes offline, and 50% protection after two hours. This feature is highly configurable. Clan/Team Integration: The plugin integrates with the Clans plugin and the in-game teams feature. The protection status of a structure or vehicle is determined by the online status of all clan or team members and authorised players. If any member or authorised player is online, protection is disabled. Penalty System: An optional penalty system is implemented to prevent abuse of the protection feature. For example, if a player leaves a clan or team, a penalty can be applied to all members and protection can be disabled for a configurable period of time. Game Tip Messages: The plugin displays game tip messages to players when they hit a protected structure or vehicle. The message includes the percentage of protection and is colour coded according to the level of protection. It supports all the languages available in Rust. Commands: Players with permission can use commands to check the protection status of other players, change the offline time of other players, and change the penalty status. Cache System: The plugin uses a caching system to optimise performance and keep the impact on the server to a bare minimum. Configuration: The plugin includes a configuration file that allows you to customise the behaviour of the plugin. Commands All commands can be configured. /orp or /ao <steam id or full name> — Check a player's offline protection status. /raidprot — Display offline raid protection information. /orp.fill.onlinetimes — Fill all players offline times. (Chat & Console command) /orp.test.offline <steam id or full name> <hours> — Change a player's offline time. /orp.test.online <steam id or full name> — Change a player's offline time to the current time. /orp.test.penalty <steam id or full name> <hours> — Change the duration of a player's penalty. A negative value or zero would disable the penalty. /orp.update.permission — Update the permissions status (offlineraidprotection.protect) for all players. Permissions All permissions can be configured. offlineraidprotection.protect — Allows a player to be protected from raids when offline. offlineraidprotection.check — Allows a player to check the offline protection status of other players. offlineraidprotection.admin — Allows a player to use all admin commands of the plugin. To grant a permission, use carbon/oxide.grant <user or group> <steamname or ID> <permission>. To revoke a permission, use carbon/oxide.revoke <user or group> <steamname or ID> <permission>. Configuration The configuration is to a large extent self-explanatory. Raid Protection Options Only mitigate damage caused by players: Choose whether or not to only mitigate damage caused directly by players. Protect players that are online: Choose whether or not to protect the bases of the players who are online. Works when "Scale of damage depending on the current hour of the real day" is configured. Scale of damage depending on the current hour of the real day: Defines the protection levels based on the current hour of the real day. The key is the hour of the day (0-23), and the value is the protection scale (0 — 340282300000000000000000000000000000000). Example: "0": 0.0, "1": 0.0, "2": 0.0, "3": 0.0 This means that the protection level is 100% from midnight to 3am. Scale of damage depending on the offline time in hours: Defines the protection levels based on the time since the player went offline. The key is the number of hours since the player went offline, and the value is the protection scale (0 — 340282300000000000000000000000000000000). The value of the hours can also be a decimal number. Example: "12": 0.25, "24": 0.5, "48": 1.0, "96": 2.0 This means that 12 hours after the player goes offline, the protection level will be 75%. After 24 hours it will be 50% and after 48 hours it will be 0%. After 96 hours, the damage is increased by 200%. Cooldown in minutes: During this time, damage levels will remain vanilla. Raids are possible. Scale of damage between the cooldown and the first configured time: During this time, the level of damage between the cooldown and the first configured time can be set to a specific value, such as 0.0. Protect all prefabs: Choose whether to protect all prefabs or only specific ones. This will protect anything in the TC range. Protect AI (animals, NPCs, Bradley and attack helicopters etc.) if 'Protect all Prefabs' is enabled: Choose whether or not to protect AI entities if "Protect all Prefabs" is enabled. May cause high hook times if set to true. Protect vehicles: Choose whether to protect vehicles or not. Vehicle authorisation always has priority. If you want to exclude certain vehicles from protection, add them to the blacklist. Protect twigs: Choose whether to protect twigs or not. Prefabs to protect: List of prefabs that will be protected. Make sure you remove the prefabs you don't want to protect, some of them are pointless. Prefabs blacklist: List of prefabs that will not be protected. Prefabs in the blacklist will always have priority to be unprotected. Timezone Options The fallback timezone is UTC if you leave it blank in the configuration, or if your configured timezone doesn't exist. The timezone identifiers are different for Windows and Linux. You can check the appendices to find your preferred timezone. Conclusion: The Offline Raid Protection plugin provides a comprehensive solution for protecting players' structures and vehicles when they are offline. This plugin is essential for any Rust server owner who wants to provide a fair and enjoyable gaming experience for their players. Acknowledgments Special thanks to @Kulltero for his valuable feedback and suggestions during the development of this plugin. Windows_Timezones.txt Linux_Timezones.txt Prefabs.txt

A webhosting always required. This website is for developers to manage their licenses It doesn't automatically license your plugins, but it talks about how to license it in the documentation. The system works with the IP address of the server where the plugin will run, not with the license key. Documentation content Already Licensed A Sample Plugin Information on how to license a plugin Information about api returns

What's The CloudFlare Automatic DDoS Protection Api; -This is a php library and Its purpose is to detect incoming requests to your site and decide whether it is a ddos attack or not, If this is a ddos attack, it will connect to your cloudflare API and activate the UnderAttack mode of your site. Example Using <?php include 'UnderAttack.php'; $underattack = new UnderAttack(); $underattack->setRequestFile('requests.json'); // Set your request log location. $underattack->setModeFile('mode.json'); // Set your mode log location. $underattack->setSeconds(5); // If there are as many requests as you enter within the second you enter, it will keep the underattack mode on for the second you enter. $underattack->setRequests(40); // If there are as many requests as you enter within the second you enter, it will keep the underattack mode on for the second you enter. $underattack->setHoldTime(600); // It will keep the UnderAttack Mode on for as long as you enter it. $underattack->setCloudflareApiKey('Your CloudFlare Api Key'); // Your CloudFlare Api Key https://dash.cloudflare.com/profile/api-tokens $underattack->setCloudflareEmail('Your CloudFlare Email Address'); // Your CloudFlare Email Address. $underattack->setCloudflareZoneid('Your App Zone id'); // Your CloudFlare App zone id. $underattack->SetIpDriver('REMOTE_ADDR'); // Ip Get Driver. $underattack->run();

The ultimate base protection plugin that allows players to pay a resource in exchange for configurable protection for their base or tugboat. This plugin has been rewritten from the ground up for performance, quality, and integrating community suggested features. Features There are many different ways you can configure this plugin to fit the needs of your server. Many features can be modified or disabled entirely through the plugin configuration file. These include: Both online and/or offline base protection Trade currency for protection or provide it for free Players can turn on/off protection Permission based protection tiers Configure what gets protected and who it is protected from Set limits on how long protection lasts Indicator(s) for displaying base protection Option for allowing raiders to bypass protection if they can drain the protection balance with damage Options for making protection more expensive for larger bases/clans and cheaper for small groups. UI that blends in seamlessly with vanilla Rust. Disclaimer This plugin will be updated at the owners discretion. Before purchasing any plugin, I recommend checking the date of the last update and refer to support tickets to see if there might be any issues with the latest Rust game version. If a game update breaks this plugin, please open a support ticket (if it doesn't already exist) and direct message me on Discord (link found below). How to Use Configure the plugin and load it Once loaded, assign yourself (or your group) one of the protection level permissions. Place a new tool cupboard, or find one that YOU have previously placed. Open the tool cupboard inventory, at the top you should see two tabs: "Upkeep" and "Protection". Select the protection tab to view the raid protection info. On this screen, you will be able to spend the configured currency in order to purchase hours of protection. By default, this currency is scrap. Use the buttons on the right to add some hours of protection, you should see that status change to show the time you are protected. Your base will now be protected for the amount of time specified. Notes You can use the Clear button to withdraw all balance, and stop protection The Pause/Resume button can be used to start/stop protection without changing the balance. The Info button will reveal a panel which displays additional information on protection. The +Max button will deposit the maximum amount of time that you can afford Quick Start Presets There is a lot of documentation for this plugin because there is a lot you can do with it! However, it doesn't have to be complicated. If you have a simple use case in mind, you can use one of these preset configurations to get what you need or use as a starting point without having to figure it out yourself! Important: You will want to assign your default permission group the raidprotection.level.1 permission for any of these configurations. Always Free Provides free raid protection for all players with the level 1 permission Protection for tugboat bases Recommended for PvE or light PvP servers Offline Only Same as the default config, but only offers offline protection Has a limit of 48 hours of protection for level 1 Includes a level 2 permission with unlimited hours of protection (VIP) Protection for tugboat bases Recommended for PvP servers Hardcore Offline only protection Two protection levels, one with a 48 hour limit and one with no limit Additional costs that scale with number of owners and building size Raiders can damage a structure and cause it to "bleed" protection balance to attempt to disable the protection with enough damage Significant delay for activating protection No protection for tugboat bases Recommended for hardcore PvP servers Upgrading Versions When a new version is released, you may need delete your config and lang files and reload them to accommodate the new changes. You do NOT need to delete the data file, unless specifically instructed. As long as you do not delete the data file, then all of your protection balances will persist, even between versions. Not all updates will require this process, but if it does, you will be notified with a message like this: To resolve this, simply delete the config and lang files and reload the plugin. You will need to manually update these files to align with what you want. As of v3.4.0 you no longer need to delete your config files when upgrading from a previous version. However, you still should check the config after the update is installed to verify no unintended changes have occurred. Protection Levels Protection levels are how you assign a particular set of rules to a player. These protection levels are added in the configuration file, and are then assigned to an auto-generated permission. Each protection level needs a unique Rank property, this rank determines the order of precedence when a player is assigned multiple protection levels. In this event, a player's protection level will always be the highest ranked protection level they are granted. Protection levels are managed in the configuration file, here is some information on some of the properties: Cost per damage protected - This amount will be deducted from the protection balance for each point of damage that was protected. So if this value is set to 1 and someone attempts to deal 100 damage to a protected structure, and that structure has 100% protection, then 100 balance will be deducted. If in that same example it was only 50% protection, then only 50 balance would be deducted. Entity resistances are taken into account as well (twig will take more damage than metal, ect). Hourly base cost - This is a fixed cost that is charged per hour of protection. Hourly cost per authorized player - This amount will be charged for each owner every hour. Can be used to charge players more if they have a larger clan. Hourly cost per floor - This amount will be charged for each floor every hour. Can be used to charge players more for protecting a larger base. Max protection time - The max number of hours protection can be applied for. If set to null, then there will be no limit. Offline protection percent - The percent of protection a structure will receive when all the owners are offline. A value of 0 will be unprotected, and a value of 100 will be fully protected. Online protection percent - The percent of protection a structure will receive when at least one owner is online. A value of 0 will be unprotected, and a value of 100 will be fully protected. Rank - A number value indicating the order of importance when a player is assigned multiple protection ranks. Higher values indicate a greater importance. For example, if a player is assigned both protection rank 1 and protection rank 2, then tool cupboards they place will be of protection rank 2 instead of 1. These ranks must be unique DO NOT create protection levels with the same rank. This value needs to be 1 or higher, it cannot be 0. Delay after taking damage - The number of seconds before protection may begin after a structure has taken unprotected damage. It is recommended to set this to a higher amount on PvP servers. Delay for offline protection - The number of seconds before offline protection kicks in after the last owner has gone offline. It is recommended to set this to a higher amount on PvP servers. Damage resets timer when owner is offline - If this is set to true, then if a raid has already started on a structure that has offline only protection, but the protection hasn't kicked in yet (due to a delay timer) then the attackers can continue to raid indefinitely as long as they continue to do damage while the owner(s) are offline. If this is set to false, then the attackers will only have a certain amount of time to continue their raid if the owner(s) are offline. Allow tugboat protection - If this is set to true, then players with this protection level may receive protection for tugboat bases. For these tugboat bases the protection panel can be accessed in the fuel inventory of the boat. The founder of a tugboat base is whomever is the FIRST player to authorize on a tugboat. Founder Limit - The number of tool cupboards that a player can be a Founder of and receive raid protection. If a player exceeds this limit, then future tool cupboards will not receive protection until enough previously placed ones have been destroyed in order to be within the limit. If a player places a tool cupboard, and they have exceeded the limit, once they are no longer exceeding the limit they can "activate" that tool cupboard in the info panel to have it gain raid protection. If this value is set to null then there is no limit. Founders and Owners When a tool cupboard is placed, the player who places it is permanently labeled as the "Founder" of that tool cupboard and building privilege. The protection level of that building privilege is derived soley from the founder's protection level, and therefore won't change unless the founder's protection level changes. Whenever a player is authorized on a tool cupboard, they will be permanently branded as an "Owner" of that tool cupboard. Owners are all the players, including the founder, who have EVER been authorized on the tool cupboard. This means that players will still be listed as an owner even if they deauthorize themselves. Owners are important because they affect how Online/Offline protection will be triggered. A base will only be granted offline protection if ALL the owners are offline, otherwise online protection (if available) will be granted if at least one owner is online. For tugboat bases, the founder is whomever is the first player to authorize themselves on the tugboat. Permissions raidprotection.admin raidprotection.level.x - these permissions are autogenerated based on your protection level settings in the config, they will show up in the server console when the plugin is loaded (unless you have Enable Console Messages set to false) raidprotection.ignore - raid protection will not count any player with this permission towards being an owner. They will not show up in the owner list and will not count toward team member count for offline protection. They also will not receive protection on bases they build even if they have a protection level assigned. This is useful for admin groups so that you don't have to remember to deauth on tool cupboards. However, if this permission is ever revoked, that player will be retroactively counted as an owner on ALL tool cupboards they are currently authed on. Commands Player Commands These commands require no permissions and can be used by any player. /pro - displays the raid protection information panel, requires authorization on the tool cupboard in the current area. /lev - displays a screen that tells the player their personal assigned protection level and explains the benefits that comes with it. Admin Commands These commands require the raidprotection.admin permission to use. /tc - displays a screen with all the available admin commands /tc help - same as /tc Use the above commands to see a full command list in game. Configuration The default config file: Here is an explanation for some of the fields: Enable Logging - Set to true to keep logs of tool cupboards protection activity. Logs will be saved to the oxide/logs/RaidProtection folder. It is recommended only to enable this only for debugging purposes, as it will take a significant amount of storage space if you have a larger server. Enable Ledger - Set to true to keep track of protection balance changes for tool cupboard. These ledger files are stored in oxide/data/RaidProtection/Ledgers. It is recommended to keep this enabled, as it will help you roll back balances if a player has an issue. This does not take up as much storage space as logging does as it only keeps track of balances. Enable Console Messages - Set to false to disable the info messages upon plugin reload. Commands - You can change the prefix for the commands this plugin uses here. Chat Message Icon ID - A steam id for the portrait of chat messages. Protection Tabs Offset - This value will adjust the vertical placement of the Protection Tabs in the tool cupboard menu. Positive values will move it up, negative values will move it down. Useful for making it so those tabs don't conflict with other UI plugins that use that area. Image Settings - Links for the images the plugin uses. Indicator Settings - Settings for the indicator that (by default) appears in the top right when you attack a protected structure. You can change its size and position or disable it. Plugin Integration - Set any of these to true if you want this plugin to take advantage of the features of another supported plugin. Custom Status Framework Settings (Ignore if you do not have Custom Status Framework integration enabled) Popup Attack Indicator - If set to true, a status will briefly appear when a player attacks a protected structure. Persistent Status For Owners - If set to true, a status will appear while a player is in a protected area that they are an owner for. Slight performance cost when enabled. Persistent Status For Non Owners - If set to true, a status will appear while a player is in a protected area that they are NOT an owner for. Slight performance cost when enabled. Popup Status When Hammer Equipped - If set to true, a status indicating the protection level of the area they are in will appear while they are holding a hammer. This will appear regardless of if you are an owner of that area or not. Protection Settings Admin owners removed when deauthorized - Normally, you cannot remove an owner even if they deauthorize. But if this setting is enabled, it allows admins to remove themselves as owners when they deauthorize from a tool cupboard. They can also achieve this with commands. Allow balance withdraw - If set to true, then players will see a "Clear" button in the tool cupboard panel that allows them to withdraw any protection balance. Allow max deposit - If set to true, there will be a "+Max" button that will purchase the maximum number of protection hours a player can afford. Award remaining balance when cupboard is destroyed - If set to true, whomever destroys a tool cupboard will be awarded whatever amount was in the protection balance. Currency item - The item that will be used as currency for protection, this will only be overridden if you are using Server Rewards or Economics for your currency. Protected entities - If any of these are set to true, then that type of entity will be covered under Raid Protection. If you are using other protection plugins like TruePvE, then you will want to configure these to not overlap with what other plugins are protecting. Protected from - If these are set to true, then damage from that type of source will be protected. By default Authed Players is set to false, which means that players will be able to damage their own structures, but enemy players cannot. Protection levels - See the section about protection levels for information. Protect twig - If set to true, then twig building blocks will receive raid protection. If set to false, then twig building blocks will not receive raid protection, even if placed by an owner of the base. Ledgers As of Raid Protection v3.2.0, you can optionally configure ledgers to be enabled. When enabled, the plugin will keep logs protection balance changes for all tool cupboards. These logs will be saved to oxide/data/RaidProtection/Ledgers. There is a ledger file for each tool cupboard, and it's filename will make the entity ID of that tool cupboard. You can use the /tc id command to see what the ID of a tool cupboard is (see commands section). The benefit of ledgers is that each balance change has a specific GUID identifier attached to it that can be used to restore a tool cupboard's balance to that exact state in the event that a player has an issue. An example of a ledger file might look like this: Ledger file for tool cupboard with ID 2250729 [ "05/26/2023 16:17:56,ad87f16e-52eb-4689-887f-ecc53cd3ff13,0,Withdraw", "05/26/2023 16:18:20,108e54c0-98c4-46df-9eb3-e17192c37bb3,0,CollectionStopped", "05/26/2023 16:18:23,a2f03162-200c-47ce-948e-b0c703435e51,0,CollectionStarted", "05/26/2023 16:18:28,5c83390e-bbd2-4049-8ec9-8f2951746159,0,Withdraw", "05/26/2023 16:19:29,cd892a3f-249b-4cad-8949-abf904656288,20,Added", "05/26/2023 16:19:31,6e710dfc-23c2-4375-8c4f-07017d4d44c6,40,Added", "05/26/2023 16:19:31,bc51f8c7-3f3a-4abc-8fd2-8bb4c47fe454,60,Added", "05/26/2023 16:20:25,f08cfa34-a623-4de3-9027-7c3acb3e3ec3,60,CollectionStarted", "05/26/2023 16:20:52,a849be59-899c-4779-bba6-2f5f1b0ffb8d,59.93055,CollectionStopped" ] The format of each row goes as follows, from left to right separated by commands. Date and Time of balance activity GUID identifier, used by the /tc restore command to roll back a balance The protection balance of the tool cupboard at that given time A brief descriptive reason as to what changed about that balance For example, using the ledger file listed above, if we wanted to rollback the tool cupboard to before the collection started (the last "Added" one), we could run the following command. /tc restore 2250729 bc51f8c7-3f3a-4abc-8fd2-8bb4c47fe454 Running this command will set the balance of the tool cupboard with ID 2250729 back to its balance of 60. As of v3.2.3 you can also mass restore all tool cupboards to a specific time or date. For example, using the ledger file listed above, if we wanted to rollback the tool cupboard to the time 16:19:00. We could run the following command. /tc ledger rollback 16:19 This will rollback ALL TOOL CUPBOARDS to the first ledger entry that comes BEFORE the given time. In this case that entry would be GUID=5c83390e-bbd2-4049-8ec9-8f2951746159 at time 16:18:28 because that is the latest entry before 16:19:00. Thus the balance will be 0. Rollbacks can also accept a date in addition to a time. For example, if you wanted to rollback to noon the following day you could run the following command. /tc ledger rollback "5/25/2023 12:00" Notice that there is no ledger entry for this tool cupboard that goes back that far. In this case, the balance of the cupboard will be set to ZERO. Please note that if you include a date and time the value MUST be enclosed in quotes (see the example above). Tugboat Bases As of v3.3.0, Raid Protection can optionally be allowed for tugboat bases. This is configurable per protection level. Tugboat bases can utilize all the features of a normal tool cupboard base. You can access the protection panel for tugboat bases in the fuel inventory in the drivers seat. For tugboat bases, the founder of the base is considered to be the FIRST player to authorize on the tugboat. Plugin Integration Clans This plugin provides built-in support for Clans. If a player is in a Clan, it will automatically treat all clan members as owners. This of course means that the owners will not be removed even when a member is kicked from a clan. True PVE This plugin is compatible with True PVE as long as both plugins are configured in a non-conflicting way. For example, if you use True PVE to provide protection to players, then in your Raid Protection config file under the Protected entities section you should set Authed Players and Unauthed Players both to false to avoid hook conflict errors. If you do see hook conflicts, see the section of this documentation about how to resolve hook conflict errors. Zone Manager This plugin is compatible with ZoneManager without any extra configuration. ZoneManager will take priority if the zone has the "undestr" flag. Custom Status Framework If you have CustomStatusFramework installed and want to take advantage of the status indicators (that appear in the bottom right) in your Raid Protection config file under the Plugin Integration section set Custom Status Framework to true. Simple Status Simple Status is a plugin that is still being developed, and will be an alternative, more performance friendly option to Custom Status Framework. This plugin is not yet available, but as of v3.4.0, configuration options have been added to support this plugin when it releases. Preview of indicators: Economics and Server Rewards If you wish to use economics balance or server rewards points as a currency instead of an item, you can set ONE of these to true in the plugin integration section of the config. It is important to set ONLY ONE of these to true, or else both will be disabled and you will get a warning in the console. Protection panel with Economics: NoDecay This plugin is compatible with NoDecay without any extra configuration. Notify If you want to use Notify as your source of indicators you can enable the flag for it in the Raid Protection config. Abandoned Bases If you enable Abandoned Bases in the integration config, then bases that are labeled as Abandoned will not receive raid protection. Raidable Bases Bases spawned by Raidable Bases will be ignored by Raid Protection. They should not show up in ledgers and players cannot add balance to them. Skill Tree If Skill Tree is enabled in the integration config then it will prevent players with the lockpicking skill from picking locks in raid protected areas. Other Plugins Should be compatible with most other plugins given they don't use the onEntityTakeDamage hook. If they do use this hook, it just means you have to change your configuration settings, see the hook conflicts section for more info. Images By default, all my images I use in this plugin are hosted on imgur. The problem with imgur is that it can only handle so many requests at once, so sometimes you might see an error in your console like: Error: HTTP/1.1 429 Too Many Requests To avoid this, I recommend hosting the images yourself, all the links are available in the config file. Carbon As of 8/19/2023 I can confirm that this plugin is compatible with Carbon. Please open a support ticket if you experience any Carbon related issues. Hook Conflicts If you're getting messages in the server console that looks similar to this: OnEntityTakeDamage resulted in a conflict between the following plugins: NoDecay - True (Boolean), RaidProtection (False (Boolean)) That means that another plugin is conflicting with Raid Protection. In most cases this is an easy fix, and it just means that you need to update your Raid Protection config file to not protect the same entities that another plugin is already protecting. So for example, if you have a plugin already that makes it so player's cannot attack each other, then there is no need for Raid Protection to do that job, and therefore in the Protected entities section of the config you should set Authed players and Unauthed players to false to avoid conflicts. Previous Versions You may have seen the free version of this plugin available on uMod. That version (2.X.X) will stay available for free on umod, but is no longer supported. If you are upgrading from the free version, you must first delete the config/lang/data files before installing v3.0.0 and above. If you do not delete these files, you will likely run into issues, as despite having the same name, the plugin has been completely rewritten, and therefore is completely incompatible with the free version. Developer API /* * Returns 0 if entity unprotected and 100 if entity fully protected */ private float GetProtectionPercent(BaseEntity entity) /* * Returns a list of the owners of the structure associated with the given entity */ private List<BasePlayer> GetOwners(BaseEntity entity) /* * Returns the player who is the founder of the structure associated with the given entity. Can be null. */ private BasePlayer GetFounder(BaseEntity entity) /* * Returns the protection balance of the structure associated with the given entity */ private float GetProtectionBalance(BaseEntity entity) /* * Returns the hours of protection remaining of the structure associated with the given entity */ private float GetProtectionHours(BaseEntity entity) Discord If you want to report a bug, require support, have a suggestion or want to be notified when I release an update you can join my plugin development discord with this link: Plugin Development Discord Link Donate Writing and maintaining these plugins takes a tremendous amount of work. Donating is one way to give some positive feedback which helps me continue making them! Buy me a coffee here! FAQ Please check out this section before opening a support ticket, it may save us both some time! Q: I don't see the status indicators in the bottom right. A: The status indicators come from another plugin called CustomStatusFramework, you must install it and enable it in the config file to get the indicators. Q: I have protection time, but I am able to damage my own structure. By default "Authed players" are able to damage their own structures. You can change this in the config file. Q: The add hours buttons aren't showing for me in the tool cupboard panel. A: The hours buttons will not show if the protection has 0 cost. Q: I have a max protection time set, but it says "protected for forever" A: If the protection cost is 0, then there cannot be a max protection time. Q: I deauthorized myself from the tool cupboard, but I am still listed as an owner. A: Owners are not removed after deauthorization. Only admins can remove owners. Q: How are overlapping tool cupboards handled? A: If a player has a base with overlapping tool cupboards, then each cupboard will need its own protection. Which entities are protected depend upon which tool cupboard governs that entity. Q: Can player's exploit offline only protection by deauthorizing? A:Deauthorizing will not help players looking to exploit offline only protection because they will still be considered an Owner even if they deauthorize. Q: Can a player exploit offline only protection by never authorizing? A: If a player is never authorized on a cupboard, then they will not count toward being online, and therefore offline protection can occur. However, players cannot add or manage protection balance unless they are authorized, and therefore the protection balance will run out, especially if a max protection time is set. Q: I have protection for horses on, but now the horses never poop A: If horses don't lose health, they will never eat and therefore never poop, this is a side effect of protection for horses. Q: Why does protection say "pending" in the bottom right? A: Pending either means that you have offline only protection or your structure has recently taken damage and therefore protection is delayed. See the tool cupboard protection panel for more info. Q: I'm seeing conflict warnings in my console between Raid Protection and True PvE A: Please refer to the sections of documentation for TruePvE and Hook Conflicts Q: I'm seeing Image failed to download! Error: HTTP/1.1 429 Too Many Requests A: Refer to the Images section of the documentation.

This is a powerful tool that allows you to customize the protection of wearable items in the game. With this plugin, admins can create their own items with their own protection values and customize the protection of existing items. This means that players can adjust the protection to their playing style, which gives them an advantage in combat. One of the distinguishing features of the plugin is its ability to allow players to take damage from NPCs on PVE servers depending on the equipment worn. This adds a new level of realism to the game, as players must carefully consider their defense when interacting with NPCs. It also encourages players to invest time and resources into building better gear, as better gear means better protection. The ability to customize protection values, create custom items, and enable NPC damage on PVE servers makes it an indispensable tool for any Rust server. Features Appearance of item protection for players on PVE servers from NPC damage Detailed adjustment of protection for any wearable item Item setup files are all separately in their own file and folder, making it easy to customize items Setting up a defense for a player without everything The ability to create your own items, with their own protection, name and skinid Permissions customizableprotection.give for give command customizableprotection.icon.show customizableprotection.icon.hide Console Commands cp.give <custom item name> - Give yourself a custom item cp.give <steamid> <custom item name> - Give the player a custom item cp.create - Add a custom item based on the image of another item cp.reload - Quick reloading of items File hierarhy: • CustomizableProtection ↳ • Custom ↳ example1.json ↳ example1.json ↳ • Default ↳ attire.banditguard.json ↳ attire.bunny.onesie.json ↳ attire.bunnyears.json ↳ attire.egg.suit.json ↳ attire.hide.boots.json ↳ attire.hide.helterneck.json ↳ attire.hide.pants.json ↳ attire.hide.poncho.json ↳ attire.hide.skirt.json ↳ ... etc. Custom item settings: { "Shortname": "partyhat", "Unique SkinId": 111, "Name": "Cap of Fortune", "Description": "Even though it looks silly, it can save!", "UI Settings": { "Name Color (or use <color></color> in name)": "1 1 1 1", "Frame Color": "0.94 0.75 0.15 1" }, "Protection": { "Hunger": 0.0, "Thirst": 0.0, "Cold": 0.0, "Drowned": 100.0, "Heat": 0.0, "Bleeding": 0.0, "Poison": 0.0, "Suicide": 0.0, "Bullet": 0.0, "Slash": 0.0, "Blunt": 0.0, "Fall": 100.0, "Radiation": 0.0, "Bite": 0.0, "Stab": 0.0, "Explosion": 0.0, "RadiationExposure": 100.0, "ColdExposure": 100.0, "ElectricShock": 0.0, "Arrow": 0.0, "OxygenExposure": 100.0 } } Default item settings: { "Hunger": 0.0, "Thirst": 0.0, "Cold": 0.0, "Drowned": 0.0, "Heat": 0.0, "Bleeding": 0.0, "Poison": 0.0, "Suicide": 0.0, "Bullet": 10.0, "Slash": 15.0, "Blunt": 15.0, "Fall": 0.0, "Radiation": 0.0, "Bite": 45.0, "Stab": 10.0, "Explosion": 0.0, "RadiationExposure": 2.0, "ColdExposure": 25.0, "ElectricShock": 0.0, "Arrow": 10.0, "OxygenExposure": 0.0 } Default Config: { "Icon Position (0 - Off | -1 - left by 1 slot, 1 - right by 1 slot | ..)": -1, "Lock values at normal values": true, "Protection Multipliers": { "Common": 1.0, "Types": { "Hunger": 1.0, "Thirst": 1.0, "Cold": 1.0, "Drowned": 1.0, "Heat": 1.0, "Bleeding": 1.0, "Poison": 1.0, "Suicide": 1.0, "Bullet": 1.0, "Slash": 1.0, "Blunt": 1.0, "Fall": 1.0, "Radiation": 1.0, "Bite": 1.0, "Stab": 1.0, "Explosion": 1.0, "RadiationExposure": 1.0, "ColdExposure": 1.0, "ElectricShock": 1.0, "Arrow": 1.0, "OxygenExposure": 1.0 } }, "Default Protection": { "Hunger": 0.0, "Thirst": 0.0, "Cold": 0.0, "Drowned": 0.0, "Heat": 0.0, "Bleeding": 0.0, "Poison": 0.0, "Suicide": 0.0, "Bullet": 0.0, "Slash": 0.0, "Blunt": 0.0, "Fall": 0.0, "Radiation": 0.0, "Bite": 0.0, "Stab": 0.0, "Explosion": 0.0, "RadiationExposure": 0.0, "ColdExposure": 0.0, "ElectricShock": 0.0, "Arrow": 0.0, "OxygenExposure": 0.0 } }

Players with permission will have temporary protection from other players and NPCs. Permissions: noobprotection.use - permission for temporary protection of players. 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>. Command: Chat commands; /protectoff - command to forcefully disable protection (can be changed in the configuration file). Console commands; resetProtectData - updates all players' defense time and set to the default value. Configuration: Player protection time (in seconds) - Time to protect the player and his buildings. Enable protection for buildings owned by the player - All buildings owned by the player will not receive damage from other players. Update protection time after death - After a player dies, the timer will be updated and set to the default value. NPCs ignore player with protection - NPCs will ignore the player with protection until the player damages them. Respawn player at the location of the last death - The player will respawn in the same location where he last died. Allow respawn at last death location after protection ends - Even after the protection time ends, the player will respawn in the same location where he last died. Minimum lifetime for respawning at the location of the last death - The player's lifespan after the last death. If the lifetime is less than specified in the variable, then the player will respawn in a random place. It is necessary for cases when the player is in an area where he is immediately killed.

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

XRaidProtection - night protection of buildings from raids. - Optimization of the interface for different monitor resolutions. - There is a lang ru/en/uk/es/fr/pt-PT/pt-BR. - Sound effects when interacting with protection. - Setting the protection time range. - Setting the protection percentage. - Customize GUI/chat messages. [ Custom setting for each type of protection ] - Setting up a list of protected prefabs in addition to building blocks, doors, large walls and gates (they are protected by default). - Support for the IQChat plugin. - Setting up protection in the first N days after the wipe. - Setting the protection percentage for privileges. [ The highest in the list of permissions is valid ] - Setting protection activity on certain days of the week. [ Example: weekdays only ] - Possibility to allow twigs to be broken during protection. - Notification of players in the chat about the activation and deactivation of protection. - The ability to always display the UI when protection is active/inactive. - The ability to include vehicle protection. - The ability to configure a different percentage of protection for each day after a wipe. -> Overview - YouTube <- Commands /protect - view protection status. Config { "Messages in chat and GUI": { "Interval between messages. Min - 10 sec": 30 }, "Setting the protection duration": { "Start protection | Hour": 22, "Start protection | Minute": 0, "End protection | Hour": 7, "End protection | Minute": 0, "Timezone - UTC+0:00": 0, "Protection activity check timer (.sec)": 120, "Use local computer/hosting time. [ Requests to an external time service and time zone will be disabled ]": true }, "General settings": { "Sound effect": "assets/bundled/prefabs/fx/invite_notice.prefab", "Protection percentage for all players. 1.0 - 100%": 0.5, "Protection percentage for all vehicles. 1.0 - 100%": 0.5, "Protected all vehicles": false, "Enable sound effect": true, "Protection activity only in the first days of the wipe": false, "How protection will work in the early days of the wipe - [ True - all day | False - only in the specified time range ]": false, "How many first days after the wipe will be active protection": 3, "Percentage of protection by day, only at ( Protection activity only in the first days of the wipe ). If the list is empty or no day is specified, the protection percentage will be taken from ( Protection percentage for all players. 1.0 - 100% )": { "1": 1.0, "2": 0.7, "3": 0.5 }, "Enable GUI message": true, "Enable chat message": false, "Allow breaking twigs during defense": true, "Enable protection for players with permission when the main protect is not active": false, "Enable protection against damage from helicopters, MLRS, submarines, etc. [ Excluding rot damage ]": true, "0 - Protection only for players with permission, 1 - Protection for all players, 2 - Protection for players with permission and for all players": 1, "What days of the week protection can be active - [ Does not apply to protection in the early days of the wipe ] - [ Sun - 1, Mon - 2, Tue - 3, Wed - 4, Thu - 5, Fri - 6, Sat - 7 ]": [ 1, 2, 3, 4, 5, 6, 7 ] }, "GUI settings": { "AnchorMin [ When damage is dealt ]": "0.5 0", "AnchorMax [ When damage is dealt ]": "0.5 0", "OffsetMin [ When damage is dealt ]": "-194.5 80", "OffsetMax [ When damage is dealt ]": "175.5 110", "Use icons [ When damage is dealt ]": true, "AnchorMin [ Status is always displayed ]": "0.5 0", "AnchorMax [ Status is always displayed ]": "0.5 0", "OffsetMin [ Status is always displayed ]": "-194.5 -6", "OffsetMax [ Status is always displayed ]": "175.5 24", "Use icons [ Status is always displayed ]": false, "Text color": "1 1 1 0.4", "Text size": 12, "Always display UI when protection is active": true, "Always display UI when protection is inactive": true }, "List of prefabs that will be protected": [ "cupboard.tool.deployed", "wall.frame.shopfront.metal" ], "Setting permissions - [ Permisssion | The percentage of protection by permission. 1.0 - 100% ]": { "xraidprotection.elite": 0.9, "xraidprotection.perm": 0.8, "xraidprotection.vip": 0.7 }, "Wipe date": "01/01/2023", "Time": "2023-01-01T00:00:00.00+00:00" }

The Patrol Helicopter only attacks hostile players or players on the Airfield. Config File My plugins are designed to adapt to your needs through a rich configuration file. { "Plugin Settings": { "Set player as hostile for an amount of time when attacked by a Patrol Helicopter (float, 0.0 = disabled)": 0.0, "Are players on Airfields hostile for the Patrol Helicopter? (boolean)": true, "Are wounded players still considered as hostile for the Patrol Helicopter? (boolean)": false, "Are incapacited players still considered as hostile for the Patrol Helicopter? (boolean)": false }, "System Settings": { "Show optional logged messages in the console (boolean)": true } } Scalable Designed and Optimized for Performance The plugins are developed with a primary objective to be very performant and scalable, thus limiting plugin-related performance losses and limited functionalities or upgrades. Premium Ready My plugins use an advanced system offering the possibility for administrators to create as many profiles as they wish in order to offer them to their players through a Premium pack. Multilingual My plugins are designed to be usable in different languages. English and Français are available by default. Administrators can add their own language. Colorblindness Friendly Interfaces are carefully designed to be as readable as possible by all players. Secured Database The plugins' database is backed up at multiple level and on a regular basis to ensure data integrity if a crash occurs. About Mælep: https://maelep.be Warranty and Updates The customers benefits from a 28-day warranty from the date of the last sell of the plugin. This warranty covers bugs related to the script and, as far as possible, bugs related to Rust and uMod updates. Terms of Service of Mælep The Mælep's plugins are in no way affiliated to Facepunch, uMod or Codefling. He should not be considered as a developer endorsed by Facepunch, uMod or Codefling. Any contribution or purchase made on this website is donated to Mælep. For more information, support or a purchase history, please use the support section available on the page of the plugin. Payment to Mælep is payment for the digital items contained in the purchase. This transaction is final and there is no refund. If you are banned for breaking the rules of Codefling, you will not be refunded. Requests for refunds due to delays, Rust and uMod update flaws or any other problems are submitted at the discretion of Mælep.

Horse lock is a simple plugin that locks horses to players for a certain amount of time as set in the configuration. Once a rider dismounts, they have a set time to mount again before the horse is unlocked to use by anyone. If an unauthorised player attempts to mount the horse before that time they will be denied. However, If a horse is kept within a players building privilege, that horse will remain protected from unauthorised use indefinitely (or until building privilege is gone). Other config options allow friends, team and clan members to ride players horses and the horse can be configured to rear up if an unauthorised player attempts to mount a protected horse (just for fun). This is a great plugin for PVE servers, but equally it can come in useful on PVP servers too. No permissions and very few config options to worry about, so it couldn't be easier to set up. Default Config: { "Options": { "Use Friends Plugin (Friends Can Mount)": false, "Use Clans Plugin (Clan Can Mount)": false, "Use Teams Plugin (Team Can Mount)": false, "Custom Chat Icon (Default = 0)": 0, "Time Horse Locked After Dismount (Seconds)": 900.0, "Make Horse Rear When Unauthorised Player Attempts to Mount": true, "Use Chat Prefix": true, "Chat Prefix": "[Horse Lock]: " }, "Plugin Version": { "Major": 1, "Minor": 0, "Patch": 1 } }

Description The goal of this plugin to block the unwanted ladders and extra twig frames on player bases from random players, who has no right to build on the given place. This plugin is ideal for PVE servers, where the Player bases are not raidable. This plugin is working with the Raidable Bases plugin together, so the ladders and twig frames are allowed while the Raidable Bases are the targets. Localization English language file generated by default, texts supported by the language files. Donation: Check my other plugins as well or if you feel you would like to support me with the Donate link on the right side. Configuration Disable plugin feature true/false Permission antiladderandtwig.bypass - bypass plugin feature

Global Offline Raid Protection is a plugin that was made to stop the pesky offline raiders! This plugin allows the server to scale explosive damage down during a certain time frame, to prevent people from the good old 3 AM offline! Now let your players go to sleep in peace, and have them enjoy a good nights rest. Permission globalofflineraidprotection.admin - Allow use of commands Commands /gettimezone - Gets servers current timezone. /toggleraidprotection - Manually toggles the raid protection. Config { "System Time to Deactivate Raiding": "03:00 AM", "System Time to Reactivate Raiding": "09:00 AM", "Amount to scale explosive damage (0-1) (0 - No Damage, 0.5 - Half Damage, 1 - Normal Damage)": 0.5, "Send message when raiding in deactivated hours?": true, "Send message when connecting in deactivated hours?": true, "Reset raid protection value to default on server wipe?": true } Language { "ScaledDown": "<color=#d4af37>[Offline Raid Protection]</color> Explosions damage have been <color=green>reduced</color> by {0}%, until {1} {2}", "ScaledUp": "<color=#d4af37>[Offline Raid Protection]</color> Explosions damage have been <color=green>reinstated</color> back to full damage, until {0} {1}", "PlayerMessage": "<color=#d4af37>[Offline Raid Protection]</color> Damage has been <color=red>scaled down</color> {0}% as you are raiding in offlining hours!", "PlayerMessageConnect": "<color=#d4af37>[Offline Raid Protection]</color> All Explosive Damage has been <color=red>scaled down</color> {0}% as you are raiding in offlining hours! Explosive damage will be reinstated at {1} {2}.", "Timezone": "<color=#d4af37>[Offline Raid Protection]</color> Current Server Timezone: {0}.", "NoPermission": "<color=#d4af37>[Offline Raid Protection]</color> You do not have permission to use this command." }

Control raid protection using rcon: enable_raid: RAID is enabled, all damage is allowed disable_raid: RAID is disabled, no damage is allowed When RAID is disabled a small UI shows on the top left corner. Using a scheduler plugin like this you can disable RAID during certain periods of time. Example config for Scheduler which: Restarts the server daily Re-enables the raid protection after the restart except if the server was wiped Disables the raid protection everyday at 12:00 Enables the raid protection everyday at 00:00 except on wipe day { "UTC": true, "Cron": [ { "Minute": "@restart", "Hour": "*", "Day": "*", "Month": "*", "DoW": "*", "Command": "!wipe disable_raid" }, { "Minute": "45", "Hour": "5", "Day": "*", "Month": "*", "DoW": "*", "Command": "restart 300 \"Daily reboot\"" }, { "Minute": "0", "Hour": "0", "Day": "*", "Month": "*", "DoW": "0,2,3,4,5,6", "Command": "disable_raid" }, { "Minute": "0", "Hour": "12", "Day": "*", "Month": "*", "DoW": "*", "Command": "enable_raid" } ] }

We all been there, where we accidentally got kicked or killed with some wierd admin loot on us. Or teleported to the wrong coordinates and got ourselves kicked from InsideTerrainViolation broadcasted to the whole server. This simple plugin gives admins an extra layer of protection against accidental bad interactions in rust game play by: Disable Anti-Hack Violations for admins (flyhack, inside terrain hack etc.) Disable player corpse for admins Automatically kill admins on disconnect. Disable admins from (mostly accidentally) inviting other players to their team Disable admins from dropping loot (when you drop loot it will simply dissapear instead) Disabled turrets/npc/bradley/patrol heli from targeting admins Disabled hostile status for admins (safezone sentries and scientists wont see you as hostile) All of the above features can be disabled in config as well as via the permission system. Missing something? If i've missed some valuable protection feel free to leave a comment or contact me on Discord at: malm0

Want to include raid schedules into your community server without blocking damages ? This is the perfect plugin for you ! Features - Set custom schedules for each day of the week, you can also set your timezone - Receive an alert on discord (using webhooks) each time a player is destroying another player entity out of the schedules - Run a custom command when a raid alert is triggered, commonly used to auto-ban raiders - Define which type of construction you want to protect - Ignore twig constructions if you want Permissions - tp2raider : Allow user to teleport on the latest raider detected by typing /tp2raider Dependencies None Language It supports different languages, EN by default, feel free to add your own translation. Support This plugin won't get you blacklisted from community by Facepunch. Join my discord if you need support or have any question => https://discord.gg/RZ8h7e2D6E Demo

Description The goal of this plugin to block the possibility to steal from other player planterboxes. It is ideal plugin for PVE servers to allow player to freely build anywhere without fear to lost the grown things. Only the owner (who put it down) of the planterbox have access to the grown vegetables/items, and the team members, Friends and Clan members. Permissions planterboxdefender.admin - to bypass the plugin restriction Dependencies Optional Clans (Clans or Rust:IO Clans) and Friends plugin dependency, in case of usage of them. Localization English language file generated by default, texts supported by the language files. Donation: Check my other plugins as well or if you feel you would like to support me with the Donate link on the right side.