The Berry Plants Page

Overview

The Berry Plant page is the dedicated editor within the PBS Editor for viewing and modifying all Berry Plant PBS data in your project. It provides a structured interface to inspect and edit every Berry Plant entry without needing to work directly with raw PBS files.

All default parameters defined by Essentials are presented in a clear and consistent layout, making it easy to understand and manage Berry Plant data at a glance. In addition, any fields introduced through plugins or custom extensions are automatically detected and displayed when present.

These extra properties are grouped under the Other Fields section, allowing the editor to remain clean and organized while still supporting extended functionality.

The screenshots below illustrate the general layout and structure of the Bery Plant editor. They serve as a visual guide to help you quickly locate sections and understand how information is organized within the interface.

Detailed explanations of individual parameters are provided in the sections that follow. For deeper technical insight or engine-level behavior, refer to the official documentation:

Defining a Berry Plant on the wiki.

Wiki

On the top-right corner of the Berry Plant Editor, you'll find the Wiki button. This provides quick access to the official Essentials documentation for Berry Plant definitions.

Clicking this button will open the following page in your browser: Defining a Berry Plant page on the Essentials Wiki.

This resource contains detailed technical documentation for every parameter available in an Berry Plant PBS entry, including engine-level behavior and supported values. It's especially useful when you need deeper insight beyond what's shown in the editor.

Settings

Located next to the Wiki button in the top-right corner of the Berry Plant Editor, the Settings button provides quick access to the PBS Editor configuration.

There are no settings relevant to this page which means this button is disabled.

Import Berry Plants

To Import one or more Berry Plants into the Editor, your data must be provided in a TSV (Tab-Separated Values) file.

The easiest way to create this format is by using Google Sheets, which allows you to quickly organize your data and export it directly as a TSV file.

For reference, you can use the following example as a template for structuring your data correctly: TSV Berry Plants Example

Required Fields

Each Berry Plant entry must include the following required parameters:

• ID
• hoursPerStage
• dryingPerHour
• yield

If any of these fields are missing, the editor will skip the entry and report which required values are not present-helping you quickly identify and correct issues in your file.

File Selection

This dropdown allows you to choose between all available Berry Plant PBS files detected in your project.

The primary file is typically named berry_plants.txt, but the editor also supports additional files follwing the format berry_plants_xxx.txt.

The underscore (_) is required for these extra files to be recognized. Any text can follow it (e.g. berry_plants_custom.txt), but files without this naming pattern will not be detected as Berry Plant PBS files.

If only a single file is available, the dropdown will be automatically disabled, and that file will be selected by default.

Berry Plant Selection

This dropdown lists all available Berry Plant entries for the currently selected file, identified by their ID.

In the PBS file, these IDs are defined using the format [xxx]. For improved readability, the editor displays them without brackets in the interface.

Despite this visual simplification, the brackets are still required in the actual PBS structure. When saving, the editor will automatically restore the correct [xxx] format, even though it is not shown within the editor itself.

ID

The ID serves as the internal identifier used by the engine to reference a Berry Plant. Each Berry Plant must have a unique ID to function correctly.

In most cases, the ID mirrors the Berry Plant's name, formatted in ALL CAPS and without spaces or special characters (e.g. MAGOBERRY, RINDOBERRY). To help prevent errors, the editor will automatically filter out invalid characters as you type.

Within the PBS file, the ID defined the start of a new Berry Plant entry and must always appear first in each block. This structure is handled automatically by the editor when saving, so no manual formatting is required.

Hours per Stage

The HoursPerStage defines the growth rate, i.e. the amount of hours between growth stages.

Default value

The HoursPerStage field is optional, but no default value is assigned by the editor.

If left undefined, the Berry Plant's HoursPerStage will be 3

Drying per Hour

The DryingPerHour defines how much moisture the soil loses per hour (newer berry plant mechanics only). A Berry Plant begins with 100 moisture, and returns to 100 moisture when it is watered.

Default value

The DryingPerHour field is optional, but no default value is assigned by the editor.

If left undefined, the Berry Plant's DryingPerHour will be 15

Yield

The Yield defines a range of two numbers. The number of berries yielded by the Berry Plant falls within this range, and is higher the more it was watered.

Default value

The Yield is optional, but no default value is assigned by the editor.

If left undefined, the Berry Plant's Yield will be 2,5

Other Parameters

Any custom parameters present in your Berry Plant PBS files that are not recognized by the editor will automatically be grouped under the Other Fields section.

These values are preserved exactly as they appear in the original file, without modification or reformatting.

When saving, the editor will write these fields back unchanged ensuring that plugin-specific or engine-modified data is never lost or corrupted.

Berry Plant Overwrite

This toggle determines how the editor handles saving the current Berry Plant entry:

• On — The editor will overwrite the existing Berry Plant entry that matches the current ID across the selected PBS file. This is the default mode.
• Off — The editor will save the entry as a new Berry Plant entry, but only if the ID does not already exist in any loaded Berry Plant PBS file. If a matching ID is found anywhere, the entry cannot be saved.