Offline Raiding Weakened (Legacy Thread)

maybe add a config option to specify how long after player logs off will offline raid protection kick in. so people dont just log off to not get raided
 
I am confused. I do not see a button to start a new thread about this plugin, only to reply in this one. I might well be missing something and if so, apologies. My comment/question is different. For me this plugin is not working. I set it to 100% thinking that it would block offline raiding. When that did not work I wondered if I had it backwards so set it to 0% just in case and that did not work either. Shooting a rocket at a player base still did damage no matter what I set the percentage at. Would still take 15 rockets to destroy an armored wall. Not sure if I am missing something. Everything is up to date on the server. I love that this plugin is very basic and would be happy to donate if I can get it working
 
For me this plugin is not working. I set it to 100% thinking that it would block offline raiding. When that did not work I wondered if I had it backwards so set it to 0% just in case and that did not work either. Shooting a rocket at a player base still did damage no matter what I set the percentage at. Would still take 15 rockets to destroy an armored wall. Not sure if I am missing something. Everything is up to date on the server. I love that this plugin is very basic and would be happy to donate if I can get it working
You need to make sure certain conditions are met:
  • The building must have building privilege
  • The damaged entity must be part of an actual building, any separated building blocks are treated as standalone buildings
  • All authorized players in the tool cupboard as well as their teammates must be offline at the time of the damage
  • The damage must be exclusively from explosive sources, such as satchels, rockets, etc
 
Last edited:
I am confused. I do not see a button to start a new thread about this plugin, only to reply in this one. I might well be missing something and if so, apologies.
Currently each plugin has only a single discussion thread. I might look into allowing separate threads in the future to make things more organized, but that's part of the long-term plans
 
Back
Top
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.
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.
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. Make sure 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