Offline Raiding Weakened

Offline Raiding Weakened 1.0.1

Sign in to download
Lowers the damage inflicted on buildings when owners are offline
Documentation License Changelog (1) Reviews (1) Version History Discussion
This plugin helps discourage offline raiding by weakening the impact of explosive damage on buildings whose owners are offline. It only works for buildings with a tool cupboard by checking if all authorized players and their teammates are offline. If everyone is offline, the damage is reduced by a percentage set in the config.



Permissions

  • offlineraidingweakened.ignore - Players with this permission will deal full damage to buildings, even if the owners are offline.

Configuration

JSON: 
{
    "Version": "1.0.0",
    "Damage Reduction Percentage": 50
}
  • Damage Reduction Percentage - Determines the percentage by which explosive damage is reduced when all owners or authorized players of a building are offline. For example, a value of 50 means that damage will be cut in half during offline raids.

Localization

JSON: 
{
    "DamageReduced": "Your damage has been reduced by {0}% because the base owners are offline."
}
Author
VisEntities
Downloads
53
First release
Last update

Ratings

2.00 star(s) 1 reviews
Donate Contribute on GitHub

Also by VisEntities

Latest updates

  1. 1.0.1

    Please wait until the Rust update goes live before downloading. Patched for the upcoming...
Read more…

Latest reviews

Kelevra
It doesn't work correctly with bugs, when you authorize more than one it doesn't work at all.
Upvote 0 Downvote
Read more…
Back
Top
Chat commands start with a /, while console commands can be entered directly in the F1 console or server console. Use find <keyword> in console to search for available commands related to the plugin. Parameters in < > are required, while [ ] are optional.
This plugin uses Oxide's permission system. Grant or revoke permissions using oxide.grant and oxide.revoke. You can assign them to individual players or groups using their Steam id or group name.
Settings are stored in the config file found under the config/ directory. You can edit this file manually, then reload the plugin to apply your changes.
Persistent data is saved in the data/ directory. This includes things like saved settings, usage stats, or player progress depending on the plugin. Deleting a data file will reset stored progress or customizations.
Language files are located in the lang/ folder. To translate messages, copy the en.json file into your target language folder (e.g. fr, de) and edit the values. Reload the plugin after changes to apply new messages.
This section lists public methods exposed by the plugin for use in other plugins. You can call these via the CallHook method. Ensure the plugin is loaded before calling its API to avoid null reference errors.
These are custom hooks that other plugins can listen for. Simply define a method with the same name and expected parameters in your plugin to handle the event. Hooks are triggered at key moments and are useful for extending or reacting to plugin behavior.
These hooks are injected into the game's code using Harmony. They let the plugin run code at key points in the game's internal logic. You can return values to block or modify behavior. Use with caution — these are powerful and can affect core mechanics.
Cart

Cart

Total -