All Plants Gone

Return to plugin
HunterZ

HunterZ

Running 1.2.0 with Carbon. Config has empty whitelist. Filled 4 railroad.planter.prefab planter boxes with berry plants. Logged on a bit under 20 hours later, and all but 2 plants had completely disappeared. The remaining 2 plants were ripe.

Edit: Is it possible that somehow it's letting plants die on server restart?
 
Last edited:
Recent First Highest Voted
It's likely something else on your server causing them to die. I actually ran a test for a week after a similar report, and the plants didn't die, in that case it turned out another plugin was interfering (Plants in Planter Box Die After One Day)

I haven't seen any recent Rust updates that changed growable plant behavior either, so I'd recommend checking your other plugins, ConVars, or even if someone on your team harvested them without realizing 👀
 
Upvote 0 Downvote
You must log in or register to reply here.
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 -