How to install BaseBuildingPlus on a DayZ server

By Niko Catarino

Updated 3 October 2026

To install BaseBuildingPlus (BBP) on a DayZ Steam PC server, load the original package with CF, deploy its signing key and add the author’s item definitions to the active mission. Before inviting players to build, test the construction and damage rules and confirm that a saved structure survives a supported restart.

Use BaseBuildingPlus, Workshop item 1710977250, published by Chopper and the BBP team. A legacy package, repack or retexture with a similar name can contain different classes. This procedure is for Steam PC servers; console servers cannot load this package.

Check the release before touching a live world

Read the author’s current description, Required items and change notes. The author lists CF as required and describes its update for DayZ 1.27. That description does not prove compatibility with every later DayZ build. Record the package version and game branch you intend to use, then rehearse on a separate instance.

Start from a server that accepts a client join. Keep a stopped backup of its mission, world, profiles, mod list and existing building configuration. A server with BBP structures needs the corresponding classes to load when restoring that save.

Locate the active mission from the server’s template, rather than selecting the first Chernarus folder in File Manager. Confirm that your test instance uses separate persistence before starting it.

If the world does not already use CF: CF’s author requires a server wipe before installation. Use a fresh test world for the first installation. Plan that change and retain a recoverable copy before adding CF to an existing community; a BBP install job does not migrate the old world for you.

Install BBP and CF

In VXPanel:

1. Stop the test service and open Mods.
2. Install CF, Workshop item 1559212036, followed by the original BBP item. Compare the panel’s dependency list with the author’s current list.
3. Wait for both jobs to finish. Keep both packages in the client-required scope, with CF before BBP.
4. Check the accepted public keys in the server’s central keys/ directory. The author’s BBP instructions name BBP.bikey; use the key supplied by the release you installed.
5. Start the test service, read the new startup logs and join with a client that loads the same packages.

For a self-managed host, follow the manual mod transfer and key steps. Copy the complete folders, retain the existing launch parameters and append the packages to the normal mod list. If those folders are named @CF and @BaseBuildingPlus, the relevant argument is:

"-mod=@CF;@BaseBuildingPlus"

Keep any other required mods in the same argument in their documented order. Use the installed folder names, including case and spaces. Keep signature verification enabled. BBP supplies content that players must load, so this is not a -serverMod= installation.

The panel manages its own mod bindings. A second hand-written launch list can disagree with the installed list; use the panel’s controls when running a managed service.

Register the BBP economy definitions

The author supplies types.xml in the package’s info folder and calls out those definitions for preventing despawning. Find the file in your installed release and inspect its entries before copying them. An old mission pack can omit newer BBP classes or introduce duplicate definitions.

Use an additional economy file to keep your BBP entries separate from the stock db/types.xml:

1. Stop the service and copy the selected author file into the active mission under bbp_ce/bbp_types.xml. Create bbp_ce if needed. Preserve the original package file.
2. Check that the copied document has one <types> root around its <type> entries. If your source contains only individual entries, wrap those entries in a <types> document before registering it.
3. Open the mission’s existing cfgeconomycore.xml and add the following block inside its existing <economycore> element:

<ce folder="bbp_ce">
    <file name="bbp_types.xml" type="types" />
</ce>

4. Preserve the other registrations and the closing root. Check the path against the uploaded file, including case on Linux.
5. Search the mission’s registered type files for earlier BBP imports. Register each intended definition once. If BBP entries were pasted into db/types.xml, reconcile those copies before loading another set.
6. Validate both XML documents, start the test service and inspect the new logs for missing files, invalid XML and unknown classes.

The loot guide explains additional file registration and item-population controls. Keep the author’s building-related lifetimes and flags unless you have a reason to change them and a test for the result. Increasing the population of a kit does not correct a missing definition for its built structure.

Use Files and SFTP for these mission changes in VXPanel. A successful Workshop download does not register the economy file.

Choose building and damage behavior

Begin with BBP itself. The author lists BBPItemPack as a separate content package, plus separate add-ons for vanilla damage on all BBP parts or doors. Decide which behavior you want before adding those packages; they are not all requirements for a basic BBP installation.

For your test record, write down:

• Which BBP release and optional packages are loaded.
• Whether your community permits damage to doors, walls or other parts.
• Whether a raiding mod changes that damage path.
• Whether placement restrictions come from vanilla gameplay settings or another building mod.

Check vanilla build-anywhere settings before adding another placement mod. Those settings and a mod’s construction rules can affect different checks. For PvE, follow the damage-enforcement procedure and test BBP objects as well as players.

Code Lock, Expansion locks and other integrations have their own package and configuration requirements. Add one integration after the baseline construction test passes. Install the original Code Lock package if that is your chosen lock system, then test it on the BBP part you intend players to use. A lock that works on a vanilla gate does not establish compatibility with a particular BBP door.

Build and save a small test structure

Use the recipes linked from the author’s Workshop description and the classnames in the installed release. Give a normal test player the required kit, tools and materials through your existing admin tool. An item spawned with elevated permissions is only a setup aid; perform placement and construction as the normal player.

Check the test server’s territory, group and placement rules before diagnosing a failed build. The 21 June 2026 WarZ tutorial demonstrates a workbench, foundation, snapping and a door on that community’s mod set. Its group requirement, flagpole workflow and trader purchases do not establish requirements for every BBP server.

Check	Required observation
Client admission	A client with CF and BBP joins without a signature, script or missing-PBO error.
Construction	The normal player places the chosen kit and completes its build steps with the documented materials.
Access	The selected door, stairs and lock behave as intended for an owner and another player.
Damage	Allowed damage works on the intended parts, and disallowed damage remains blocked in the tested combination.
Persistence	The completed structure and its lock state remain after a normal stop and start using the same test save.
Economy	The required kits or materials appear through the configured loot or trader path, where applicable.

Scroll to see all columns →

Record the tested parts, coordinates, packages and observations. Inspect both construction and restart logs. If you use a trader, configure its BBP inventory as a separate step: economy XML does not add trader listings. For Expansion Market, use the inventory and category procedure.

Diagnose a failed check

Symptom	Check before changing saved data
Player cannot join	CF and BBP versions, required packages, keys and the client-required mod list. Use missing-PBO troubleshooting.
Classes cannot be spawned	The loaded package and the exact current classname. A name from a legacy recipe may be absent from another release.
Placement works but construction fails	Current recipe, material quantities, part selection, player permissions and conflicting construction mods.
Parts disappear after restart	The active mission, registered definitions for the affected classes, lifetimes, duplicate overrides and persistence errors.
Parts take unexpected damage	Loaded damage add-ons, raiding integrations and server damage settings.
A kit never appears as loot	Its nominal, min, restrictions and registration. A kit target does not control a placed structure’s save compatibility.

Scroll to see all columns →

The Workshop page contains recent reports of construction and persistence problems. Those reports are reasons to run the checks above; they do not identify a universal fix. Preserve the failed logs and package versions before changing the configuration.

Update or roll back

For an update, stop the service, take a compatible recovery set and read the BBP change notes. Replace the package and accepted key as required, compare the new supplied economy entries and coordinate the clients’ version. Repeat construction, damage and persistence checks on the test instance before applying the update to the live world.

For a failed installation, restore the previous mod list, mission and compatible saved state together. Follow mod removal before unloading BBP from a world containing its structures. Retaining a save while removing its building classes can leave missing objects or load errors.

Related documentation: Bohemia’s mission-file registration reference.

Return to the DayZ server guides after construction, access and saved-state checks pass.