Herbs V2

Paid edition · RedM · VORP included · Other frameworks via public bridges

Collect plants, choose rewards and create your gathering areas. You do not need to be a developer to configure Herbs: with VORP, manage the main settings through the in-game menu using this guide. To change framework or add effects from other scripts, see the editable files and dedicated guides below.

Already using another framework? A developer can connect your core and inventory through the editable public bridges. This applies to existing frameworks as well as custom-built ones; the supplied integration is for VORP.

▷Preview coming soon

Photos and videos will be available in this gallery.

RZ shop

Version

Read the installed version in fxmanifest.lua. V2 uses the rz_herbs_v2 entry in RZ Releases, separate from the free edition.

Overview

• 41 plant types, with customizable names, blips and rewards.
• Global or per-plant settings for blips, horseback collection, respawn and supported consumption effects, within RedM's native limits. Some plants cannot be eaten; Saltbush only allows eating.
• Groups with multiple positions and plant choices based on probabilities.
• Positions and groups already supplied as in V1; edit them or add more in game.

Installation

1. Download your package from the Cfx.re Portal.
2. Put the rz_herbs resource folder inside resources, optionally in a category such as [rz]: for example resources/[rz]/rz_herbs.
3. Start your core, inventory and oxmysql before Herbs. VORP is the default integration; change it through the public bridges.
4. Add to your server.cfg:

ensure oxmysql
ensure vorp_core
ensure vorp_inventory
ensure rz_herbs

You need RedM with OneSync and a working database connection for oxmysql.

First start — Show Herbs in the RZ menu's script list.

Moving from V1

Stop V1 and remove it from active resources; move it elsewhere if you want to keep a copy. Replace it with V2 named rz_herbs: the two editions cannot run together.

V2 needs configuring: starting groups and coordinates already match V1, but your personal changes are not imported. Choose rewards and adjust settings in game. You can use items already in your inventory.

Requirements

VORP

• vorp_core, vorp_inventory and registered reward items.

Other frameworks

• A developer must adapt public/bridge_server.lua to your core and inventory; see Framework Integration below.

Required for all

• RedM with OneSync, oxmysql and a working database connection.
• Cfx entitlement for the protected package.
• Owner setup and permissions for editing from the RZ menu.

Configuration

Open /rz → Herbs for this script's settings.

MENU GUIDE →

General

Box	Settings
Base	Gameplay text language, script enabled, debug
Plants	Horseback collection, additional effects, rendering distance and respawn time
Global blips	Visibility, icon and color
Discord logs	Webhook and collection/eating logs enabled

Rendering distance ranges from 5 to 100; respawn from 1 to 1440 minutes. Debug is for troubleshooting. Additional effects are off by default.

General settings — Show Base, Plants and Global blips.

Global or custom

Plants follow global settings by default. Choose Custom to make an exception. Example: blips off for all plants, but on for Yarrow. Use global for all removes exceptions for that setting.

Plants

Select or search for a plant to change its name, blip, horseback collection, respawn and rewards. The effects box only appears for edible plants.

A customized plant — Show Yarrow with a custom blip and an inherited setting.

For owner setup and staff access, follow Access and Discord logs.

Spawn & Coordinates

1. Open Positions and create a group with a recognizable name.
2. Set its group chance and add plants; confirm each choice.
3. Capture positions in game where plants should appear. Move or remove them as needed. Click Save all to apply the group.

Plant group — Show two plant choices with chances and several positions.

How chances work

Group: chance that something spawns at each position, on startup and after collection. If the respawn roll fails, the point stays empty until positions are rebuilt, for example after a restart or a saved group edit; it is not retried every minute.

Plants: determine which plant is chosen when a position spawns one. Percentages adjust to your choices: values of 1 and 3 mean 25% and 75%.

For fixed points with one plant: set the group to 100%, add one plant and your positions.

Rewards

Rewards are empty by default: choose your inventory items.

1. Open a plant → Collection rewards.
2. Select an item, minimum/maximum quantity and chance; add the row.
3. Repeat for any other rewards, then click Save all to apply the changes.

Each reward has an independent chance: two at 50% can give neither, one or both. A 100% chance does not bypass inventory limits. The notification lists items actually received.

No item received?

Check configured rewards, the exact item name and inventory capacity/limits. A plant is still collected even without rewards.

Multiple rewards — Show two items with quantities and chances.

Optional plant items — VORP

To add plant items, you can run public/herbs-vorp.sql in your database. This is optional: existing inventory items work too, and importing does not set up rewards for you. Instructions are in the SQL file and package README.

Consumption Effects

In public/eateffects.lua, add functions from other scripts for hunger, thirst, stress or your preferred effects. There is a function for each edible plant: insert your system's call and enable the effect in the menu.

The setting enables additional effects, not RedM's native Eat prompt. Herbs already sends the eating notification; do not duplicate it in the effect.

Consumption effect — Show an edible plant's effect setting and help.

Multiplayer & Respawn

Joining players see the current plant state. When someone collects or eats a plant, other players receive the update; the same available plant does not award collection to two players at once.

Low resmon: in the author's test among 41 plants, the highest observed value was 0.02 ms. This is the result of that test, not a guaranteed limit for every server.

Respawn uses each plant’s effective setting and is checked once per minute. Saved settings, groups, coordinates and rewards remain in the configuration database: back it up before updating. Individual plants’ collection state and cooldowns are held in memory and reset when the resource restarts.

Framework Integration

VORP integration is supplied. Other frameworks require adapting the real core/inventory calls in the public bridge; they are not selected automatically.

File	Purpose
public/bridge_server.lua	Adapt frameworks and inventories other than VORP
public/bridge_client.lua	Change the notification system
public/eateffects.lua	Connect effects from other scripts
public/notifications.lua	Change notification wording

BRIDGE GUIDE →

Languages & Notifications

Open public/notifications.lua and edit the quoted text in the English en or Italian it block. There are no placeholders to manage: names and quantities are added automatically.

For example, changing found = "You found:" can show “You found: x1 Yarrow”. The found_suffix and eaten_suffix fields only add final punctuation and can stay empty.

Save the file and restart only rz_herbs. To replace the notification system, follow the dedicated guide.

In-game notifications — Show collection with several items and a message after eating.

Discord Logs

In General → Discord logs, enter your webhook and enable Herbs logs to record collection and eating.

Herbs log — Show script, plant and interaction outcome. Blur personal identifiers.

Updating

1. Back up the resource, edited public files and configuration database.
2. Stop rz_herbs and obtain the complete updated package from Cfx.
3. Replace the resource with the complete package, including its supplied .rz bundle and interfaces. Never edit generated .rz files or update only public/.
4. Compare and reapply bridge, notification and effect customizations to the new public files; do not overwrite them blindly with the old folder.
5. Preserve the configuration database and follow release notes for any migration. Existing saved rewards must not be reset as an update step.
6. Restart and check menu access, saved settings, collection, rewards, consumption and multiplayer sync.

Keep rz_update_product "rz_herbs_v2" in the supplied manifest. The checker announces updates; it does not install them. For V1 → V2, use Moving from V1.

Troubleshooting

Problem	Check
Resource does not start	Entitlement, dependencies, database connection and resource name
Cannot edit the menu	Owner setup and granted permissions in the access guide
No plants visible	Saved/enabled settings, positions, group chance, render distance and cooldown
No rewards	Rewards are empty by default; add items, save and check inventory limits
No extra consumption effect	Supported edible plant, enabled effect and public/eateffects.lua integration
Wrong notification	Script language, public/notifications.lua and client notification bridge

Include version, framework, steps and relevant console errors in a Discord ticket.