Install RaG BeeHive on a DayZ server

By VYKIX

Updated 7 October 2026

Install RaG BeeHive and RaG Core on the server and joining clients, then edit BeeHive’s generated settings. The original RaG_BeeHive package, item 2879040969, is published by RaG Tyson. Honey liquids are included through Core; a separate liquid framework is no longer required.

Install the packages

Stop the service and back up the mission, world save, profiles, packages, keys and startup settings. Keep a record of the DayZ build and mod versions. Use a separate instance to check the change before adding it to a world your community uses.

In VXPanel Mods, find the original BeeHive package and RaG Core (3556131153), verify their Steam links and use client-visible loading. For a manual installation, follow the package and signing-key procedure. Keep signature checks enabled and make sure joining players load matching releases.

Core’s dependency documentation explains that DayZ resolves addon order through declared dependencies. Reordering the launch argument cannot replace a missing package. Start the restricted instance, check for missing-addon or script errors, then stop it before inspecting profiles.

Find and edit the BeeHive JSON

After first startup, look beneath the directory selected by the service’s -profiles argument:

RaG_Core/Configs/
  RaG_Beehive/
    RaG_Beehive.json

The author’s published example is:

{
  "Version": 1,
  "GetFrameFillTime": 60.0,
  "GetSmokedStateTime": 5,
  "GetChanceForBeesToStay": 50,
  "GetChanceToFarmBeeTrap": 10
}

• GetFrameFillTime: minutes to fill each frame.
• GetSmokedStateTime: minutes the smoker suppresses hive damage.
• GetChanceForBeesToStay: percentage chance added bees remain.
• GetChanceToFarmBeeTrap: percentage chance a tree search yields a trap.

Keep percentages between 0 and 100. Restart after changing settings.

Save a copy of the generated file before editing. Compare it with the example instead of replacing it: a later package may generate a newer schema or additional fields. Preserve field names and the generated Version. Validate the JSON, change one setting and check the result before making another adjustment.

Check older configurations before an update

The 28 January 2025 change note says frame and smoker timers changed to minutes. It calls the frame field GetFillFrameTime; the newer description uses GetFrameFillTime. The 27 November 2025 note then records a script rework and the Core dependency.

Keep your old file as a recovery copy. Generate a fresh profile on the separate instance with the versions you intend to run, then compare names, units and values. Do not assume the old field name is an alias or copy an old duration without checking its unit. If the installed file differs from the current author instructions, resolve that difference before updating the live world.

Supply the items and check a working hive

Installing the package does not populate your economy. Add the desired items through your economy, trader or another spawning system, as the author instructs.

Obtain exact classnames and economy definitions for your installed release from the package or author. Display names are not reliable configuration identifiers. Keep a separate copy of your mission edits and follow custom loot registration when using the Central Economy. Get any missing definitions from the author before enabling natural spawns or trader stock.

Use the author’s beekeeping instructions for equipment and recipes. Frames require bees to progress; the author describes frame progress as surviving a restart. If an action is missing, check the bees, attachment slot and item in your hands.

On the separate instance, obtain a kit through the same route a player will use. Deploy it, complete a production cycle and record the settings and elapsed time. Stop and start the service while another frame is partly filled, then check the hive, attachments and remaining progress. Repeat the relevant check with an ordinary player account.

Diagnose errors and keep a recovery path

If the BeeHive file does not appear, confirm the active profiles directory and both loaded packages before creating folders yourself. Use server logs to trace the first error in that startup session.

Core’s own diagnostic settings live separately at RaG_Core/Configs/RaG_Core/RaG_Core.json. Its server configuration reference recommends retaining error logging and enabling detailed logs for a specific investigation. Its production example is not a universal default. Keep heavy extended logging off during normal use unless you need the extra output, then restore your previous diagnostic settings after investigating.

Undo a configuration-only change by stopping the service and restoring the saved BeeHive JSON. For a package rollback, restore a matching package, profile and world snapshot on the separate instance first; a JSON backup alone cannot restore placed objects. Confirm the recovered hive and contents before applying the recovery to the live service. Check mod removal before removing Core, since other installed mods may require it.

Source and verification scope

This AI-assisted procedure was checked against the author’s cached BeeHive description, ten displayed historical change notes and three complete Core wiki pages on 7 October 2026. The Core pages match the 29 September documentation revision. Current package contents, exact item definitions, generated settings, gameplay and recovery have not been tested here.

BeeHive and Core prohibit repacking, reuploading and monetizing the mods themselves. Their author permits use on an approved monetized server when the mods are excluded from monetization. Check the original BeeHive listing and Core permissions before changing how you distribute or sell access to their content.