Consistent Wind Power

Consistent Wind Power 1.1.0

Sign in to download
Keeps windmill and solar panel output stable no matter the weather, height, or sun position
In vanilla Rust, windmills and solar panels produce varying amounts of power based on environmental factors. Windmills depend on wind speed and height placement, while solar panels rely on sun position and weather conditions. This plugin eliminates that inconsistency by allowing server admins to set fixed power output values for both types of renewable energy sources.


Permissions

  • consistentwindpower.use -- Grants access to consistent power output for windmills and solar panels owned by the player. Only required if Require Permission is enabled in the configuration.
Note: If Require Permission is set to false in the config, all windmills and solar panels will have consistent power output regardless of ownership or permissions.

Configuration

JSON:
{
  "Version": "1.1.0",
  "Windmill Power Output": 150,
  "Solar Panel Power Output": 20,
  "Require Permission": true
}
  • Windmill Power Output -- Constant power output in watts for all windmills, completely overriding vanilla wind speed and height calculations.
  • Solar Panel Power Output -- Constant power output in watts for all solar panels, allowing them to produce power 24/7 regardless of sun position or weather.
  • Require Permission -- When enabled, only entities owned by players with the consistentwindpower.use permission receive consistent power. When disabled, all windmills and solar panels get consistent power regardless of ownership.
Author
VisEntities
Downloads
49
First release
Last update

Ratings

0.00 star(s) 0 reviews

Also by VisEntities

Latest updates

  1. 1.1.0

    Fixed an issue where windmill power output was being capped at 150 regardless of config setting...
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