Join the Game4Freak Discord Get exclusive plugin sneak peeks, talk directly with VisEntities, never miss important updates, and unlock special discount codes!
Forever Ripe

Forever Ripe 1.2.1

Sign in to download
Keeps your crops ripe and harvestable indefinitely
Forgot to check your planters? No problem. This plugin prevents plants from dying if you don't harvest them in time. Plants that would normally wither after staying ripe too long will instead remain healthy and harvestable indefinitely.

Once a plant reaches the ripe state, it stays ripe forever instead of progressing to the dying stage. This means players can harvest on their own schedule without losing crops to neglect. The plugin works automatically for players with permission and can be configured to apply to all plants or only specific types.

Permissions

  • foreverripe.use -- Required for the plugin to preserve a player's plants. Only plants owned by players with this permission will be kept in a ripe state.

Configuration

JSON:
{
  "Version": "1.2.0",
  "Whitelisted Growables (leave empty to apply to all)": []
}
  • Whitelisted Growables -- Controls which plant types are preserved by the plugin. When left empty, all growable entities will be kept in a ripe state. To limit the effect to specific plants, add their short prefab names to this list.
Common plant prefab names:
  • corn.entity - Corn
  • pumpkin.entity - Pumpkin
  • hemp.entity - Hemp
  • potato.entity - Potato
  • mushroom-cluster-5, mushroom-cluster-6 - Mushrooms (both varieties)
Author
VisEntities
Downloads
300
First release
Last update

Ratings

5.00 star(s) 2 reviews

Also by VisEntities

Latest updates

  1. 1.2.1

    Fixed stageAge not being reset, causing rapid cycling from Ripe to Dying and eventual plant...
  2. 1.2.0

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

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

Latest reviews

Simple and clean plugin.

Does its job and has a nice whitelist option for fine tuning should you have the need.
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