Recent content by kaooa

  1. kaooa

    Teleport Sleeper Bodies to Lobby on Player Disconnect

    i fixed this myself, by adding a onplayerconnected that would respawn the player, did this using a standalone plugin but the standalone causes the gear not to be given on the respawn lol might be an idea for you to add a onplayerconnected idk
  2. kaooa

    Teleport Sleeper Bodies to Lobby on Player Disconnect

    i get what you mean, I mainly said it because I am still having the problem that on player connect, it puts them on a respawn screen instead of just automatically respawning them
  3. kaooa

    Teleport Sleeper Bodies to Lobby on Player Disconnect

    also what do you think of adding a rule "TeleportSleeper2Lobby" ? for when people leave in a minigame, and instead of "nosleepings" like "invisiblesleepers" that will just make sleeper go into vanish
  4. kaooa

    Redirect Players to Another Server

    Every server does a daily restart, we call know that. (1) A great idea I've seen on many other servers is automatically redirecting players to another server during the daily restart. This helps maintain player activity and keeps the population up on another server owned by the same community...
  5. kaooa

    Raidable Shelters (Legacy Thread)

    do you think it would be possible to implement an feature that would allow us to set a percentage to spawn? such as... assets/prefabs/deployable/woodenbox/woodbox_deployed.prefab : spawn chance 50% assets/prefabs/deployable/furnace/furnace.prefab : spawn chance 12% campfire: spawn chance 100%...
  6. kaooa

    Boxed Player Spawn (Legacy Thread)

    Does this add to the limit that the player can place themselves or does this count to the 1/1 ? and does this work with https://umod.org/plugins/random-respawner ?
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