Raidable Shelters

Raidable Shelters 1.7.3

Sign in to download
Spawns shelters filled with loot for players to raid
Documentation License Changelog (12) Reviews (6) Version History Discussion

1.2.0

  • Added the ability to apply random skins to shelter doors from a predefined list in the config.
  • Renamed api method API_RaidableShelter to API_IsShelterRaidable for consistency.

1.1.0

  • Deauthorize all players from the building privilege of the spawned shelter.
  • Add support for multiple skins for interior entities, enabling random skin selection each time an entity is spawned.
  • Added Notify Surrounding Players Of Shelter Spawn determining whether surrounding players should be notified when a shelter spawns. If set to false, only the player for whom the shelter spawned will be notified.
  • Added Radius For Notifying Nearby Players defining the radius within which nearby players will be notified.
  • Added Send As Toast which if disabled, notifications will be sent as chat messages.
  • Spawned shelters and their interior entities are now stored in a data file.
  • Resume removal timers for shelters upon plugin initialization, ensuring they're always removed as scheduled, even after server crashes.
  • Added localization.
  • Introduced two new hooks for interacting with shelter interior entities:
    • OnShelterInteriorEntitySpawn(LegacyShelter shelter, string prefabName, Vector3 position, Quaternion rotation): Called before an entity is spawned inside a shelter. Returning false will prevent the entity from being spawned.
    • OnShelterInteriorEntitySpawned(LegacyShelter shelter, BaseEntity entity): Called after an entity has been spawned inside a shelter.
  • Added a new API method:
    • bool API_IsShelterRaidable(LegacyShelter shelter): Checks if a given shelter is a raidable shelter based on the stored data.
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

Cart

Total -