Out Of Combat Heal

Out Of Combat Heal 1.1.0

Sign in to download
Restores player health gradually after a few minutes without taking damage
Documentation License Changelog (1) Version History Discussion
Works With
Better No Escape
This Rust plugin lets players gradually heal up after being free from damage for a set duration, much like Call of Duty's health regeneration system.




Permissions

  • outofcombatheal.use - Only players with this permission will be healed after staying out of battle.

Configuration

JSON: 
{
    "Version": "1.1.0",
    "Time Out Of Combat Before Healing Seconds": 300.0,
    "Time Gap Between Healing Ticks Seconds": 10.0,
    "Health Restored Per Healing Tick": 10.0,
    "Pause Healing If Combat Blocked (Better No Escape)": false
}
  • Time Out Of Combat Before Healing Seconds - The number of seconds a player must be out of combat (without taking damage) before healing begins.
  • Time Gap Between Healing Ticks Seconds - The interval in seconds between each healing tick once the player has started healing.
  • Health Restored Per Healing Tick - The amount of health restored to the player on each healing tick.
  • Pause Healing If Combat Blocked - When true, healing only starts after Better No Escape confirms the player is not combat-blocked. Set to false if that plugin isn't installed on your server.
Author
VisEntities
Downloads
49
First release
Last update

Ratings

0.00 star(s) 0 reviews
Donate Contribute on GitHub

Also by VisEntities

Latest updates

  1. 1.1.0

    Added optional integration with Better No Escape, players now begin healing only after they're...
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 -