Metabolism Control

Metabolism Control 1.0.0

Override player metabolism stats like health, calories, and hydration
Documentation License Version History Discussion
This Rust plugin lets you fully control player metabolism stats like health, calories, and hydration. You can create different profiles for specific permission groups, each with their own values and maximum limits, and even freeze specific stats to stop them from draining.




Permissions

  • metabolismcontrol.<suffix> - Grant this to a player/group to use the matching profile (example suffixes: vip, elite).
  • metabolismcontrol.vip - Example profile permission from the default config.
Each profile uses its own permission name, which the plugin automatically registers (for example, vip becomes metabolismcontrol.vip).
Click to expand...

Configuration

JSON: 
{
  "Version": "1.0.0",
  "Apply On Connect": true,
  "Apply On Respawn": true,
  "Default Values (used if no profile matches)": {
    "Calories (set to -1 to stop decreasing)": 500,
    "Hydration (set to -1 to stop decreasing)": 250,
    "Health": 100,
    "Maximum Calories (set to 0 to ignore)": 0,
    "Maximum Hydration (set to 0 to ignore)": 0,
    "Maximum Health (set to 0 to ignore)": 0
  },
  "Update Current And Maximums On Reload (false = max only)": false,
  "Profiles": [
    {
      "Enabled": true,
      "Permission (e.g., vip or metabolismcontrol.vip)": "vip",
      "Priority (higher wins)": 10,
      "Values": {
        "Calories (set to -1 to stop decreasing)": 500,
        "Hydration (set to -1 to stop decreasing)": -1,
        "Health": 100,
        "Maximum Calories (set to 0 to ignore)": 0,
        "Maximum Hydration (set to 0 to ignore)": 0,
        "Maximum Health (set to 0 to ignore)": 0
      }
    },
    {
      "Enabled": true,
      "Permission (e.g., vip or metabolismcontrol.vip)": "elite",
      "Priority (higher wins)": 20,
      "Values": {
        "Calories (set to -1 to stop decreasing)": -1,
        "Hydration (set to -1 to stop decreasing)": -1,
        "Health": 110,
        "Maximum Calories (set to 0 to ignore)": 0,
        "Maximum Hydration (set to 0 to ignore)": 0,
        "Maximum Health (set to 0 to ignore)": 120
      }
    }
  ]
}
  • Apply On Connect - When a player connects, apply the best-matched profile (or the defaults).
  • Apply On Respawn - When a player respawns, apply the best-matched profile (or the defaults).
  • Default Values- Fallback values used when the player has no matching permission profile.
    • Calories - Set current calories; use -1 to freeze at the last seen value (no decrease).
    • Hydration - Set current hydration; use -1 to freeze at the last seen value (no decrease).
    • Health - Set current health after max is considered.
    • Maximum Calories - Sets the player's maximum calories if above 0.
    • Maximum Hydration - Sets the player's maximum hydration if above 0.
    • Maximum Health - Sets the player's maximum health if above 0.
  • Update Current And Maximums On Reload- What to do to online players when the plugin reloads or after a server restart finishes loading:
    • true - update both current values and maximums.
    • false - only update maximums (keeps the player's current health/calories/hydration as-is).
  • Profiles- List of permission-based overrides. The highest Priority matching profile wins.
    • Enabled - Turn the profile on/off.
    • Permission - Permission suffix; will be normalized to metabolismcontrol.<suffix>.
    • Priority - Used to break ties when multiple profiles match.
    • Values - Same fields as in Default Values and applied when this profile wins.
Author
VisEntities
License duration
Unlimited
Price
7.99 USD
First release
Last update

Ratings

0.00 star(s) 0 reviews
Donate

Also by VisEntities

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 -