Forever Ripe

Forever Ripe 1.2.0

Sign in to download
Stops plants from dying by keeping them in a ripe state all the time
This Rust plugin prevents plants in planter boxes from dying by keeping them in a ripe state all the time. It's useful for players who might forget to harvest their plants before they die. This works for any plant that can grow, including hemp, potatoes, and even berries, basically any plant that goes through different stages of growth.



Permissions

  • foreverripe.use - Only plants planted by players with this permission stay ripe and don't die.

Configuration

JSON:
{
  "Version": "1.2.0",
  "Whitelisted Growables (leave empty to apply to all)": []
}
  • Whitelisted Growables - List of short prefab names (e.g. corn.entity). If empty, the plugin applies to all growables.
Author
VisEntities
Downloads
184
First release
Last update

Ratings

5.00 star(s) 1 reviews

Also by VisEntities

  • Patrol Heli Crash Dont Retire
    Patrol Heli Crash Dont Retire
    Forces patrol helicopters to crash instead of leaving the map at the end of their lifetime
  • No Raid Debris
    No Raid Debris
    Disables debris that block building during raids
  • Legacy Airdrops
    Legacy Airdrops
    Brings back legacy airdrops where cargo planes drop multiple airdrops instead of just one

Latest updates

  1. 1.2.0

    Plugin now protects all growables if the config list is empty, or only listed ones if specified.
  2. 1.1.0

    Fixed plants dying from health loss. Introduced foreverripe.use permission.

Latest reviews

I left plants overnight in RL and were still there, seems to work as intended, great work.
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