Herbs
rz_herbs is a complete herb and plant harvesting system for RedM, designed to be lightweight, performant, and fully configurable.
The script supports both SQL-based persistence and config-only mode, making it suitable for small and large servers alike.
Add full plant interaction to your server with a fully configurable, multiplayer-synced herb system.
Version
Current version: loading...
Overview
With rz_herbs you can:
- Harvest & eat all supported Red Dead Redemption 2 plants
- Define custom spawn locations
- Assign multiple rewards per plant
- Apply custom effects when items are used
- Support harvesting on foot and on horseback
- Sync plants correctly in multiplayer
Performance & Sync
rz_herbs is designed for very low resmon usage.
- Plants are spawned and synced only within render distance
- Client-side render cache
- No global loops or broadcast events
Performance notes
- Average client usage: ~0.00–0.02 ms
- Tested with 40+ plants
Supported Frameworks
- VORP
- Custom framework adapter (Other frameworks can be added via adapter functions)
Installation
- Download the resource
- Place it in your resources folder:
rz_herbs
- Add this ensure in your server.cfg after core and inventory
ensure rz_herbs- Configure files inside:
/public/config.lua/public/eateffects.lua
- Restart the server
Requirements
VORP
- vorp_core
- vorp_inventory
Custom Framework
- Custom inventory trigger
- Custom character system
Required for all
- OneSync enabled
- oxmysql (optional if SQL disabled)
Configuration
The main configuration file controls rendering, persistence, interaction logic and framework support.
config.lua
Plant Spawn & Coordinates
Plants can be spawned using:
- predefined coordinates
- random zones
- SQL persistent positions (optional)
Each plant keeps its own state and is synced only to nearby players.
coords.lua
Eat Effects System
Each plant can apply a custom effect
eateffects.lua
Framework Adaptation
rz_herbs is framework-agnostic.
All framework logic is isolated inside adapter files. You can edit or replace them without touching the core script.
Included adapters:
- VORP (ready to use)
- Custom template (for any other framework)
VORP Adapter
The VORP adapter is already functional.
You may edit it only if:
- your VORP build is customized
- your inventory logic differs
vorp_cl.lua
vorp_sv.lua
Custom Framework Adapter
If you are not using VORP, you must implement the Custom adapter.
The placeholder functions must return the same data expected by the script.
custom_cl.lua
custom_sv.lua
Updating
Updating script depends on what files are changed.
- Core logic updates can usually be applied by replacing the resource
- Config updates may require manual changes
- Framework adapters should be reviewed if your framework is customized
Always compare updated files before overwriting your existing configuration.
