Installation

Installation and safe updates

English | Русский

Updated 31 October 2026. Issued private alpha: 0.19.328. This is not a public beta or a Thunderstore package. Version and limits.

The internal 0.19.329 candidate has passed eight bounded native data checks. Four direct producer-profile checks (.blueprint/.vbuild) have passed independent review. Acceptance of 2.17 covers codec/profile data only in the internal 0.19.329 candidate. Strict player-state endpoints differ; the cause is not established. Inventory, source files and catalogue content hashes were preserved; the ordinary-save comparison covered metadata only. This run does not establish UI, world construction, new visual frames, networking or a cold-process test. The next requirement is 2.18; the 2.16 HOLD is unchanged. The .280 examples and 23 October captures describe their historical version; they do not validate 0.19.328 or the 0.19.329 candidate.

Install the issued328 package

Follow the package-matched instructions: close the game, back up outside plugins, replace BuildWorks.dll/BuildWorks.Geometry.dll/YamlDotNet.dll/THIRD_PARTY_NOTICES.md together, and keep one active copy. Do not copy a QA profile/token/bridge; retain worlds/characters. Older public versions below are historical references.

Home · First blueprint

Purpose and starting point

You need Valheim, a compatible BepInExPack Valheim 5.4.x, and an explicitly released BuildWorks package. Follow the requirements of that particular package. The old 0.19.37 alpha ZIP does not automatically include the development features described here. This guide does not assert which public release is newest.

Install or update

1. Close the game and server. Back up your world, character, and BuildWorks data from the profile you use.
2. Before updating, keep the previous DLL pair separately and read the package's data compatibility notes. Do not mix builds.
3. Install both BuildWorks.dll and BuildWorks.Geometry.dll into BepInEx/plugins/Ostrix-BuildWorks/.
4. Check other plugin subfolders for duplicate BuildWorks installations.
5. During your normal launch, find BuildWorks <version> loaded. in BepInEx/LogOutput.log. Match the number to the package, then check that the catalogue opens.

Expected result: one matching version loads. A loader message alone does not verify importing, construction, or multiplayer.

Your data

The normal library is BepInEx/config/BuildWorks/blueprints.json. Separate imported copies are stored in imports; portable copies use share/<id>.buildworks.json inside the BuildWorks data directory. Use Share to obtain the actual path: isolated QA uses a different root. The share folder is not automatically imported or published to the server.

With the game closed, back up the whole BuildWorks data directory alongside the world and character. A single shared blueprint is not a backup of construction projects or refund records. Do not delete operation journals to clear an error. Downgrading after a format change is not guaranteed; use a compatible backup.

Compatibility and removal

Jotunn, EarthWorks, and TerrainRamp are not required runtime dependencies. A blueprint containing another mod's pieces still needs that mod; importing does not install it. Compatibility with every mod and a complete multiplayer cycle is not claimed.

To remove BuildWorks, save your data, close the game, and remove only the plugin folder. This does not cancel already constructed native objects. Mods supplying custom pieces have their own persistence requirements.

Common problem — no UI: inspect the log, duplicate DLLs, game version, and mod list. Do not replace DLLs while Valheim is running. The owner's development QA uses a separately guarded test profile; the source workspace is not a player installation directory.