Added a new chat command /rs.test, which allows admins to spawn a test shelter at their current location. This command is primarily for testing purposes.
Added a new config option Shelter Health, that allows to customize the health of raidable shelters. Note: This setting applies to both the shelter and its door, as their health values are synchronized.
Introduced a debug mode to help troubleshoot and visualize the reasons behind shelter spawn failures, including player state (e.g., swimming, near monuments) and environmental factors (e.g., rocks, roads).
Note: Debug information is drawn only to players with admin privileges. Enable this mode only when necessary!
Introduced a spawn chance percentage for each interior entity in shelters. Note: The spawn chance is evaluated individually for each instance of the entity.
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.
