Searchable reference for DayZ Tools, PBO builds, keys, models, textures, Workshop publishing and typical modder errors.
entries85categories23
85 matchesSearch by tool, file, error, command or workflow.
First steps / Getting started
Official DayZ Tools start
Getting started
Official DayZ Tools start is a DayZ Tools reference entry for Getting started. Use it in the First steps area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
Official DayZ Tools start belongs to the First steps area and helps place the correct DayZ Tools workflow step.
Practical checks
Install DayZ Tools through Steam, then check the DayZ game path.
Set up Project Drive or WorkDrive before working with your own mod files.
DayZ Tools Launcher is a DayZ Tools reference entry for Environment. Use it in the Launchers and environment tools area to check paths, files, build output, signatures or Workshop steps before publishing.
Bin\Launcher\DayZToolsLauncher.exe
Details
Purpose
DayZ Tools Launcher belongs to the Launchers and environment tools area and helps place the correct DayZ Tools workflow step.
Related tool or path: Bin\Launcher\DayZToolsLauncher.exe.
Practical checks
Check the launcher, game path and Project Drive before starting an individual tool.
If a tool does not start, verify the DayZ Tools installation and local paths first.
Launchers and environment tools / Environment
WorkDrive / Project Drive mount
Environment
WorkDrive / Project Drive mount is a DayZ Tools reference entry for Environment. Use it in the Launchers and environment tools area to check paths, files, build output, signatures or Workshop steps before publishing.
Bin\WorkDrive\WorkDrive.exe
Details
Purpose
WorkDrive / Project Drive mount belongs to the Launchers and environment tools area and helps place the correct DayZ Tools workflow step.
Related tool or path: Bin\WorkDrive\WorkDrive.exe.
Practical checks
Check the launcher, game path and Project Drive before starting an individual tool.
If a tool does not start, verify the DayZ Tools installation and local paths first.
Launchers and environment tools / Environment
Workbench
Environment
Workbench is a DayZ Tools reference entry for Environment. Use it in the Launchers and environment tools area to check paths, files, build output, signatures or Workshop steps before publishing.
Bin\Workbench\workbenchApp.exe
Details
Purpose
Workbench belongs to the Launchers and environment tools area and helps place the correct DayZ Tools workflow step.
Related tool or path: Bin\Workbench\workbenchApp.exe.
Practical checks
Check the launcher, game path and Project Drive before starting an individual tool.
If a tool does not start, verify the DayZ Tools installation and local paths first.
PBO creation and packaging / PBO build
Addon Builder
PBO build
Addon Builder is a DayZ Tools reference entry for PBO build. Use it in the PBO creation and packaging area to check paths, files, build output, signatures or Workshop steps before publishing.
Bin\AddonBuilder\AddonBuilder.exe
Details
Purpose
Addon Builder belongs to the PBO creation and packaging area and helps place the correct DayZ Tools workflow step.
Related tool or path: Bin\AddonBuilder\AddonBuilder.exe.
Practical checks
Check the source folder, config.cpp, Addon Builder output and build log.
Keep work files, built PBOs and signed release files clearly separated.
PBO creation and packaging / PBO build
Binarize
PBO build
Binarize is a DayZ Tools reference entry for PBO build. Use it in the PBO creation and packaging area to check paths, files, build output, signatures or Workshop steps before publishing.
Bin\Binarize\binarize.exe
Details
Purpose
Binarize belongs to the PBO creation and packaging area and helps place the correct DayZ Tools workflow step.
Related tool or path: Bin\Binarize\binarize.exe.
Practical checks
Check the source folder, config.cpp, Addon Builder output and build log.
Keep work files, built PBOs and signed release files clearly separated.
PBO creation and packaging / PBO build
FileBank
PBO build
FileBank is a DayZ Tools reference entry for PBO build. Use it in the PBO creation and packaging area to check paths, files, build output, signatures or Workshop steps before publishing.
Bin\PboUtils\FileBank.exe
Details
Purpose
FileBank belongs to the PBO creation and packaging area and helps place the correct DayZ Tools workflow step.
Related tool or path: Bin\PboUtils\FileBank.exe.
Practical checks
Check the source folder, config.cpp, Addon Builder output and build log.
Keep work files, built PBOs and signed release files clearly separated.
PBO creation and packaging / PBO build
BankRev
PBO build
BankRev is a DayZ Tools reference entry for PBO build. Use it in the PBO creation and packaging area to check paths, files, build output, signatures or Workshop steps before publishing.
Bin\PboUtils\BankRev.exe vagy BankRevGUI.exe
Details
Purpose
BankRev belongs to the PBO creation and packaging area and helps place the correct DayZ Tools workflow step.
Related tool or path: Bin\PboUtils\BankRev.exe vagy BankRevGUI.exe.
Practical checks
Check the source folder, config.cpp, Addon Builder output and build log.
Keep work files, built PBOs and signed release files clearly separated.
PBO creation and packaging / PBO build
PboViewer
PBO build
PboViewer is a DayZ Tools reference entry for PBO build. Use it in the PBO creation and packaging area to check paths, files, build output, signatures or Workshop steps before publishing.
The v1.4.2b release note mentions a fix for export paths ending with a trailing slash.
CLI examples
./PboViewer packFolder --path="C:\test"
./PboViewer unpackFolder --path="C:\test.pbo"
./PboViewer listFiles --path="C:\test.pbo"
DayZ release note
Use it for inspection, listing, unpacking or simple tests, but keep Addon Builder/Binarize and DSUtils signature checks in the release flow.
When unpacking third-party PBOs, respect the mod license and usage rights.
Keys, signing and server signature checks / Key and signature
DSCreateKey
Key and signature
DSCreateKey is a DayZ Tools reference entry for Key and signature. Use it in the Keys, signing and server signature checks area to check paths, files, build output, signatures or Workshop steps before publishing.
Bin\DsUtils\DSCreateKey.exe
Details
Purpose
DSCreateKey belongs to the Keys, signing and server signature checks area and helps place the correct DayZ Tools workflow step.
Related tool or path: Bin\DsUtils\DSCreateKey.exe.
Practical checks
Keep the private key safe and publish only the matching .bikey file.
Sign every release PBO again and place the public key in the server keys folder.
Keys, signing and server signature checks / Key and signature
DSSignFile
Key and signature
DSSignFile is a DayZ Tools reference entry for Key and signature. Use it in the Keys, signing and server signature checks area to check paths, files, build output, signatures or Workshop steps before publishing.
Bin\DsUtils\DSSignFile.exe
Details
Purpose
DSSignFile belongs to the Keys, signing and server signature checks area and helps place the correct DayZ Tools workflow step.
Related tool or path: Bin\DsUtils\DSSignFile.exe.
Practical checks
Keep the private key safe and publish only the matching .bikey file.
Sign every release PBO again and place the public key in the server keys folder.
Keys, signing and server signature checks / Key and signature
DSCheckSignatures
Key and signature
DSCheckSignatures is a DayZ Tools reference entry for Key and signature. Use it in the Keys, signing and server signature checks area to check paths, files, build output, signatures or Workshop steps before publishing.
Bin\DsUtils\DSCheckSignatures.exe
Details
Purpose
DSCheckSignatures belongs to the Keys, signing and server signature checks area and helps place the correct DayZ Tools workflow step.
Related tool or path: Bin\DsUtils\DSCheckSignatures.exe.
Practical checks
Keep the private key safe and publish only the matching .bikey file.
Sign every release PBO again and place the public key in the server keys folder.
Keys, signing and server signature checks / Key and signature
DSUtils GUI
Key and signature
DSUtils GUI is a DayZ Tools reference entry for Key and signature. Use it in the Keys, signing and server signature checks area to check paths, files, build output, signatures or Workshop steps before publishing.
Bin\DsUtils\DSUtils.exe
Details
Purpose
DSUtils GUI belongs to the Keys, signing and server signature checks area and helps place the correct DayZ Tools workflow step.
Related tool or path: Bin\DsUtils\DSUtils.exe.
Practical checks
Keep the private key safe and publish only the matching .bikey file.
Sign every release PBO again and place the public key in the server keys folder.
Config, binary config and conversion / Config and script
CfgConvert
Config and script
CfgConvert is a DayZ Tools reference entry for Config and script. Use it in the Config, binary config and conversion area to check paths, files, build output, signatures or Workshop steps before publishing.
Bin\CfgConvert\CfgConvert.exe
Details
Purpose
CfgConvert belongs to the Config, binary config and conversion area and helps place the correct DayZ Tools workflow step.
Related tool or path: Bin\CfgConvert\CfgConvert.exe.
Practical checks
Check config.cpp, CfgPatches, CfgMods and requiredAddons before the build.
Read script compile errors together with the affected path and file name.
Config, binary config and conversion / Config and script
BinMake
Config and script
BinMake is a DayZ Tools reference entry for Config and script. Use it in the Config, binary config and conversion area to check paths, files, build output, signatures or Workshop steps before publishing.
Bin\BinMake\binMake.exe
Details
Purpose
BinMake belongs to the Config, binary config and conversion area and helps place the correct DayZ Tools workflow step.
Related tool or path: Bin\BinMake\binMake.exe.
Practical checks
Check config.cpp, CfgPatches, CfgMods and requiredAddons before the build.
Read script compile errors together with the affected path and file name.
Textures, images and materials / Texture and material
ImageToPAA
Texture and material
ImageToPAA is a DayZ Tools reference entry for Texture and material. Use it in the Textures, images and materials area to check paths, files, build output, signatures or Workshop steps before publishing.
Bin\ImageToPAA\ImageToPAA.exe vagy imageToPaaGUI.exe
Details
Purpose
ImageToPAA belongs to the Textures, images and materials area and helps place the correct DayZ Tools workflow step.
Related tool or path: Bin\ImageToPAA\ImageToPAA.exe vagy imageToPaaGUI.exe.
Practical checks
Check PAA format, texture size, alpha channel and RVMAT paths.
Keep source images and exported game textures separated.
Textures, images and materials / Texture and material
TexView
Texture and material
TexView is a DayZ Tools reference entry for Texture and material. Use it in the Textures, images and materials area to check paths, files, build output, signatures or Workshop steps before publishing.
Bin\ImageToPAA\TexView.exe
Details
Purpose
TexView belongs to the Textures, images and materials area and helps place the correct DayZ Tools workflow step.
Related tool or path: Bin\ImageToPAA\TexView.exe.
Practical checks
Check PAA format, texture size, alpha channel and RVMAT paths.
Keep source images and exported game textures separated.
Textures, images and materials / PBO build
MatEditor
PBO build
MatEditor is a DayZ Tools reference entry for PBO build. Use it in the Textures, images and materials area to check paths, files, build output, signatures or Workshop steps before publishing.
Bin\ObjectBuilder\MatEditor.exe
Details
Purpose
MatEditor belongs to the Textures, images and materials area and helps place the correct DayZ Tools workflow step.
Related tool or path: Bin\ObjectBuilder\MatEditor.exe.
Practical checks
Check the source folder, config.cpp, Addon Builder output and build log.
Keep work files, built PBOs and signed release files clearly separated.
Models and objects / PBO build
Object Builder
PBO build
Object Builder is a DayZ Tools reference entry for PBO build. Use it in the Models and objects area to check paths, files, build output, signatures or Workshop steps before publishing.
Bin\ObjectBuilder\ObjectBuilder.exe
Details
Purpose
Object Builder belongs to the Models and objects area and helps place the correct DayZ Tools workflow step.
Related tool or path: Bin\ObjectBuilder\ObjectBuilder.exe.
Practical checks
Check the source folder, config.cpp, Addon Builder output and build log.
Keep work files, built PBOs and signed release files clearly separated.
Models and objects / PBO build
O2Script
PBO build
O2Script is a DayZ Tools reference entry for PBO build. Use it in the Models and objects area to check paths, files, build output, signatures or Workshop steps before publishing.
Bin\ObjectBuilder\O2Script.exe
Details
Purpose
O2Script belongs to the Models and objects area and helps place the correct DayZ Tools workflow step.
Related tool or path: Bin\ObjectBuilder\O2Script.exe.
Practical checks
Check the source folder, config.cpp, Addon Builder output and build log.
Keep work files, built PBOs and signed release files clearly separated.
Models and objects / PBO build
p3d2bmp
PBO build
p3d2bmp is a DayZ Tools reference entry for PBO build. Use it in the Models and objects area to check paths, files, build output, signatures or Workshop steps before publishing.
Bin\TerrainBuilder\p3d2bmp.exe
Details
Purpose
p3d2bmp belongs to the Models and objects area and helps place the correct DayZ Tools workflow step.
Related tool or path: Bin\TerrainBuilder\p3d2bmp.exe.
Practical checks
Check the source folder, config.cpp, Addon Builder output and build log.
Keep work files, built PBOs and signed release files clearly separated.
Terrain, maps and world building / PBO build
Terrain Builder
PBO build
Terrain Builder is a DayZ Tools reference entry for PBO build. Use it in the Terrain, maps and world building area to check paths, files, build output, signatures or Workshop steps before publishing.
Bin\TerrainBuilder\terrainBuilder.exe
Details
Purpose
Terrain Builder belongs to the Terrain, maps and world building area and helps place the correct DayZ Tools workflow step.
Related tool or path: Bin\TerrainBuilder\terrainBuilder.exe.
Practical checks
Check the source folder, config.cpp, Addon Builder output and build log.
Keep work files, built PBOs and signed release files clearly separated.
Terrain, maps and world building / Terrain and world
Terrain Processor
Terrain and world
Terrain Processor is a DayZ Tools reference entry for Terrain and world. Use it in the Terrain, maps and world building area to check paths, files, build output, signatures or Workshop steps before publishing.
Bin\TerrainProcessor\TerrainProcessor.exe
Details
Purpose
Terrain Processor belongs to the Terrain, maps and world building area and helps place the correct DayZ Tools workflow step.
Related tool or path: Bin\TerrainProcessor\TerrainProcessor.exe.
Practical checks
Check terrain source data, CE structure, navmesh steps and exported files.
Use small test runs before publishing large world changes.
Terrain, maps and world building / Terrain and world
NavMeshGenerator
Terrain and world
NavMeshGenerator is a DayZ Tools reference entry for Terrain and world. Use it in the Terrain, maps and world building area to check paths, files, build output, signatures or Workshop steps before publishing.
Bin\NavMeshGenerator\NavMeshGenerator_x64.exe
Details
Purpose
NavMeshGenerator belongs to the Terrain, maps and world building area and helps place the correct DayZ Tools workflow step.
Related tool or path: Bin\NavMeshGenerator\NavMeshGenerator_x64.exe.
Practical checks
Check terrain source data, CE structure, navmesh steps and exported files.
Use small test runs before publishing large world changes.
Terrain, maps and world building / Terrain and world
CE Editor
Terrain and world
CE Editor is a DayZ Tools reference entry for Terrain and world. Use it in the Terrain, maps and world building area to check paths, files, build output, signatures or Workshop steps before publishing.
Bin\CeEditor\CeEditor.exe
Details
Purpose
CE Editor belongs to the Terrain, maps and world building area and helps place the correct DayZ Tools workflow step.
Related tool or path: Bin\CeEditor\CeEditor.exe.
Practical checks
Check terrain source data, CE structure, navmesh steps and exported files.
Use small test runs before publishing large world changes.
Publishing and Steam Workshop / Publishing
Publisher
Publishing
Publisher is a DayZ Tools reference entry for Publishing. Use it in the Publishing and Steam Workshop area to check paths, files, build output, signatures or Workshop steps before publishing.
Bin\Publisher\Publisher.exe
Details
Purpose
Publisher belongs to the Publishing and Steam Workshop area and helps place the correct DayZ Tools workflow step.
Related tool or path: Bin\Publisher\Publisher.exe.
Practical checks
Check mod.cpp, preview image, Workshop metadata and the final file list.
Test the release locally before updating the Workshop item.
Mod structure and base files / Config and script
config.cpp
Config and script
config.cpp is a DayZ Tools reference entry for Config and script. Use it in the Mod structure and base files area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
config.cpp belongs to the Mod structure and base files area and helps place the correct DayZ Tools workflow step.
Practical checks
Check config.cpp, CfgPatches, CfgMods and requiredAddons before the build.
Read script compile errors together with the affected path and file name.
Mod structure and base files / Config and script
CfgPatches
Config and script
CfgPatches is a DayZ Tools reference entry for Config and script. Use it in the Mod structure and base files area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
CfgPatches belongs to the Mod structure and base files area and helps place the correct DayZ Tools workflow step.
Practical checks
Check config.cpp, CfgPatches, CfgMods and requiredAddons before the build.
Read script compile errors together with the affected path and file name.
Mod structure and base files / Config and script
CfgMods
Config and script
CfgMods is a DayZ Tools reference entry for Config and script. Use it in the Mod structure and base files area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
CfgMods belongs to the Mod structure and base files area and helps place the correct DayZ Tools workflow step.
Practical checks
Check config.cpp, CfgPatches, CfgMods and requiredAddons before the build.
Read script compile errors together with the affected path and file name.
Mod structure and base files / Publishing
mod.cpp
Publishing
mod.cpp is a DayZ Tools reference entry for Publishing. Use it in the Mod structure and base files area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
mod.cpp belongs to the Mod structure and base files area and helps place the correct DayZ Tools workflow step.
Practical checks
Check mod.cpp, preview image, Workshop metadata and the final file list.
Test the release locally before updating the Workshop item.
Mod structure and base files / Publishing
meta.cpp
Publishing
meta.cpp is a DayZ Tools reference entry for Publishing. Use it in the Mod structure and base files area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
meta.cpp belongs to the Mod structure and base files area and helps place the correct DayZ Tools workflow step.
Practical checks
Check mod.cpp, preview image, Workshop metadata and the final file list.
Test the release locally before updating the Workshop item.
Typical modding workflow / Modding reference
New mod development
Modding reference
New mod development is a DayZ Tools reference entry for Modding reference. Use it in the Typical modding workflow area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
New mod development belongs to the Typical modding workflow area and helps place the correct DayZ Tools workflow step.
Practical checks
Check the relevant paths, source files and tool outputs.
After a failed run, read the newest logs first.
Typical modding workflow / Modding reference
Server-side mod test
Modding reference
Server-side mod test is a DayZ Tools reference entry for Modding reference. Use it in the Typical modding workflow area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
Server-side mod test belongs to the Typical modding workflow area and helps place the correct DayZ Tools workflow step.
Practical checks
Check the relevant paths, source files and tool outputs.
After a failed run, read the newest logs first.
Typical modding workflow / Modding reference
Client-side mod test
Modding reference
Client-side mod test is a DayZ Tools reference entry for Modding reference. Use it in the Typical modding workflow area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
Client-side mod test belongs to the Typical modding workflow area and helps place the correct DayZ Tools workflow step.
Practical checks
Check the relevant paths, source files and tool outputs.
After a failed run, read the newest logs first.
Typical modding workflow / Troubleshooting
Dependency check
Troubleshooting
Dependency check is a DayZ Tools reference entry for Troubleshooting. Use it in the Typical modding workflow area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
Dependency check belongs to the Typical modding workflow area and helps place the correct DayZ Tools workflow step.
Practical checks
Compare fresh client, server and build logs with the time of the error.
Check requiredAddons, paths, PBO content, signatures and bikey files.
Common errors and quick causes / PBO build
Missing addon / requiredAddons error
PBO build
Missing addon / requiredAddons error is a DayZ Tools reference entry for PBO build. Use it in the Common errors and quick causes area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
Missing addon / requiredAddons error belongs to the Common errors and quick causes area and helps place the correct DayZ Tools workflow step.
Practical checks
Check the source folder, config.cpp, Addon Builder output and build log.
Keep work files, built PBOs and signed release files clearly separated.
Common errors and quick causes / Key and signature
Missing bisign
Key and signature
Missing bisign is a DayZ Tools reference entry for Key and signature. Use it in the Common errors and quick causes area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
Missing bisign belongs to the Common errors and quick causes area and helps place the correct DayZ Tools workflow step.
Practical checks
Keep the private key safe and publish only the matching .bikey file.
Sign every release PBO again and place the public key in the server keys folder.
Common errors and quick causes / PBO build
PBO mismatch
PBO build
PBO mismatch is a DayZ Tools reference entry for PBO build. Use it in the Common errors and quick causes area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
PBO mismatch belongs to the Common errors and quick causes area and helps place the correct DayZ Tools workflow step.
Practical checks
Check the source folder, config.cpp, Addon Builder output and build log.
Keep work files, built PBOs and signed release files clearly separated.
Common errors and quick causes / Config and script
Script compile error
Config and script
Script compile error is a DayZ Tools reference entry for Config and script. Use it in the Common errors and quick causes area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
Script compile error belongs to the Common errors and quick causes area and helps place the correct DayZ Tools workflow step.
Practical checks
Check config.cpp, CfgPatches, CfgMods and requiredAddons before the build.
Read script compile errors together with the affected path and file name.
Common errors and quick causes / Texture and material
Texture/material error
Texture and material
Texture/material error is a DayZ Tools reference entry for Texture and material. Use it in the Common errors and quick causes area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
Texture/material error belongs to the Common errors and quick causes area and helps place the correct DayZ Tools workflow step.
Practical checks
Check PAA format, texture size, alpha channel and RVMAT paths.
Keep source images and exported game textures separated.
Security and release rules / Key and signature
Private key protection
Key and signature
Private key protection is a DayZ Tools reference entry for Key and signature. Use it in the Security and release rules area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
Private key protection belongs to the Security and release rules area and helps place the correct DayZ Tools workflow step.
Practical checks
Keep the private key safe and publish only the matching .bikey file.
Sign every release PBO again and place the public key in the server keys folder.
Security and release rules / PBO build
Release PBO check
PBO build
Release PBO check is a DayZ Tools reference entry for PBO build. Use it in the Security and release rules area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
Release PBO check belongs to the Security and release rules area and helps place the correct DayZ Tools workflow step.
Practical checks
Check the source folder, config.cpp, Addon Builder output and build log.
Keep work files, built PBOs and signed release files clearly separated.
Security and release rules / Modding reference
Version control
Modding reference
Version control is a DayZ Tools reference entry for Modding reference. Use it in the Security and release rules area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
Version control belongs to the Security and release rules area and helps place the correct DayZ Tools workflow step.
Practical checks
Check the relevant paths, source files and tool outputs.
After a failed run, read the newest logs first.
Security and release rules / Key and signature
Key rotation
Key and signature
Key rotation is a DayZ Tools reference entry for Key and signature. Use it in the Security and release rules area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
Key rotation belongs to the Security and release rules area and helps place the correct DayZ Tools workflow step.
Practical checks
Keep the private key safe and publish only the matching .bikey file.
Sign every release PBO again and place the public key in the server keys folder.
DayZ Tools Launcher in detail / Environment
Launching tools from one place
Environment
Launching tools from one place is a DayZ Tools reference entry for Environment. Use it in the DayZ Tools Launcher in detail area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
Launching tools from one place belongs to the DayZ Tools Launcher in detail area and helps place the correct DayZ Tools workflow step.
Practical checks
Check the launcher, game path and Project Drive before starting an individual tool.
If a tool does not start, verify the DayZ Tools installation and local paths first.
DayZ Tools Launcher in detail / Environment
Game path setup
Environment
Game path setup is a DayZ Tools reference entry for Environment. Use it in the DayZ Tools Launcher in detail area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
Game path setup belongs to the DayZ Tools Launcher in detail area and helps place the correct DayZ Tools workflow step.
Practical checks
Check the launcher, game path and Project Drive before starting an individual tool.
If a tool does not start, verify the DayZ Tools installation and local paths first.
DayZ Tools Launcher in detail / Environment
Project Drive path setup
Environment
Project Drive path setup is a DayZ Tools reference entry for Environment. Use it in the DayZ Tools Launcher in detail area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
Project Drive path setup belongs to the DayZ Tools Launcher in detail area and helps place the correct DayZ Tools workflow step.
Practical checks
Check the launcher, game path and Project Drive before starting an individual tool.
If a tool does not start, verify the DayZ Tools installation and local paths first.
DayZ Tools Launcher in detail / Environment
Mount / unmount Project Drive
Environment
Mount / unmount Project Drive is a DayZ Tools reference entry for Environment. Use it in the DayZ Tools Launcher in detail area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
Mount / unmount Project Drive belongs to the DayZ Tools Launcher in detail area and helps place the correct DayZ Tools workflow step.
Practical checks
Check the launcher, game path and Project Drive before starting an individual tool.
If a tool does not start, verify the DayZ Tools installation and local paths first.
Addon Builder fields and usage / PBO build
Addon source directory
PBO build
Addon source directory is a DayZ Tools reference entry for PBO build. Use it in the Addon Builder fields and usage area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
Addon source directory belongs to the Addon Builder fields and usage area and helps place the correct DayZ Tools workflow step.
Practical checks
Check the source folder, config.cpp, Addon Builder output and build log.
Keep work files, built PBOs and signed release files clearly separated.
Addon Builder fields and usage / PBO build
Destination directory
PBO build
Destination directory is a DayZ Tools reference entry for PBO build. Use it in the Addon Builder fields and usage area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
Destination directory belongs to the Addon Builder fields and usage area and helps place the correct DayZ Tools workflow step.
Practical checks
Check the source folder, config.cpp, Addon Builder output and build log.
Keep work files, built PBOs and signed release files clearly separated.
Addon Builder fields and usage / PBO build
Binarize switch
PBO build
Binarize switch is a DayZ Tools reference entry for PBO build. Use it in the Addon Builder fields and usage area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
Binarize switch belongs to the Addon Builder fields and usage area and helps place the correct DayZ Tools workflow step.
Practical checks
Check the source folder, config.cpp, Addon Builder output and build log.
Keep work files, built PBOs and signed release files clearly separated.
Addon Builder fields and usage / PBO build
Clear temp folder
PBO build
Clear temp folder is a DayZ Tools reference entry for PBO build. Use it in the Addon Builder fields and usage area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
Clear temp folder belongs to the Addon Builder fields and usage area and helps place the correct DayZ Tools workflow step.
Practical checks
Check the source folder, config.cpp, Addon Builder output and build log.
Keep work files, built PBOs and signed release files clearly separated.
Addon Builder fields and usage / PBO build
Include / exclude file rules
PBO build
Include / exclude file rules is a DayZ Tools reference entry for PBO build. Use it in the Addon Builder fields and usage area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
Include / exclude file rules belongs to the Addon Builder fields and usage area and helps place the correct DayZ Tools workflow step.
Practical checks
Check the source folder, config.cpp, Addon Builder output and build log.
Keep work files, built PBOs and signed release files clearly separated.
Addon Builder fields and usage / PBO build
Reading build logs
PBO build
Reading build logs is a DayZ Tools reference entry for PBO build. Use it in the Addon Builder fields and usage area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
Reading build logs belongs to the Addon Builder fields and usage area and helps place the correct DayZ Tools workflow step.
Practical checks
Check the source folder, config.cpp, Addon Builder output and build log.
Keep work files, built PBOs and signed release files clearly separated.
DSUtils and key management / Key and signature
Create a new key with DSUtils GUI
Key and signature
Create a new key with DSUtils GUI is a DayZ Tools reference entry for Key and signature. Use it in the DSUtils and key management area to check paths, files, build output, signatures or Workshop steps before publishing.
Bin\DsUtils\DSUtils.exe
Details
Purpose
Create a new key with DSUtils GUI belongs to the DSUtils and key management area and helps place the correct DayZ Tools workflow step.
Related tool or path: Bin\DsUtils\DSUtils.exe.
Practical checks
Keep the private key safe and publish only the matching .bikey file.
Sign every release PBO again and place the public key in the server keys folder.
DSUtils and key management / Key and signature
Create a new key from the command line
Key and signature
Create a new key from the command line is a DayZ Tools reference entry for Key and signature. Use it in the DSUtils and key management area to check paths, files, build output, signatures or Workshop steps before publishing.
Bin\DsUtils\DSCreateKey.exe
Details
Purpose
Create a new key from the command line belongs to the DSUtils and key management area and helps place the correct DayZ Tools workflow step.
Related tool or path: Bin\DsUtils\DSCreateKey.exe.
Practical checks
Keep the private key safe and publish only the matching .bikey file.
Sign every release PBO again and place the public key in the server keys folder.
DSUtils and key management / Key and signature
Signing a PBO with DSUtils GUI
Key and signature
Signing a PBO with DSUtils GUI is a DayZ Tools reference entry for Key and signature. Use it in the DSUtils and key management area to check paths, files, build output, signatures or Workshop steps before publishing.
Bin\DsUtils\DSUtils.exe vagy Bin\DsUtils\DSSignFile.exe
Details
Purpose
Signing a PBO with DSUtils GUI belongs to the DSUtils and key management area and helps place the correct DayZ Tools workflow step.
Related tool or path: Bin\DsUtils\DSUtils.exe vagy Bin\DsUtils\DSSignFile.exe.
Practical checks
Keep the private key safe and publish only the matching .bikey file.
Sign every release PBO again and place the public key in the server keys folder.
DSUtils and key management / Key and signature
Public key for the server
Key and signature
Public key for the server is a DayZ Tools reference entry for Key and signature. Use it in the DSUtils and key management area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
Public key for the server belongs to the DSUtils and key management area and helps place the correct DayZ Tools workflow step.
Practical checks
Keep the private key safe and publish only the matching .bikey file.
Sign every release PBO again and place the public key in the server keys folder.
DSUtils and key management / Key and signature
Key names and versioning
Key and signature
Key names and versioning is a DayZ Tools reference entry for Key and signature. Use it in the DSUtils and key management area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
Key names and versioning belongs to the DSUtils and key management area and helps place the correct DayZ Tools workflow step.
Practical checks
Keep the private key safe and publish only the matching .bikey file.
Sign every release PBO again and place the public key in the server keys folder.
Publisher and Workshop in detail / Publishing
Creating a Workshop item
Publishing
Creating a Workshop item is a DayZ Tools reference entry for Publishing. Use it in the Publisher and Workshop in detail area to check paths, files, build output, signatures or Workshop steps before publishing.
Bin\Publisher\Publisher.exe
Details
Purpose
Creating a Workshop item belongs to the Publisher and Workshop in detail area and helps place the correct DayZ Tools workflow step.
Related tool or path: Bin\Publisher\Publisher.exe.
Practical checks
Check mod.cpp, preview image, Workshop metadata and the final file list.
Test the release locally before updating the Workshop item.
Publisher and Workshop in detail / Publishing
Updating a Workshop item
Publishing
Updating a Workshop item is a DayZ Tools reference entry for Publishing. Use it in the Publisher and Workshop in detail area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
Updating a Workshop item belongs to the Publisher and Workshop in detail area and helps place the correct DayZ Tools workflow step.
Practical checks
Check mod.cpp, preview image, Workshop metadata and the final file list.
Test the release locally before updating the Workshop item.
Publisher and Workshop in detail / Publishing
mod.cpp check before Publisher
Publishing
mod.cpp check before Publisher is a DayZ Tools reference entry for Publishing. Use it in the Publisher and Workshop in detail area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
mod.cpp check before Publisher belongs to the Publisher and Workshop in detail area and helps place the correct DayZ Tools workflow step.
Practical checks
Check mod.cpp, preview image, Workshop metadata and the final file list.
Test the release locally before updating the Workshop item.
Publisher and Workshop in detail / Publishing
Workshop preview image
Publishing
Workshop preview image is a DayZ Tools reference entry for Publishing. Use it in the Publisher and Workshop in detail area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
Workshop preview image belongs to the Publisher and Workshop in detail area and helps place the correct DayZ Tools workflow step.
Practical checks
Check mod.cpp, preview image, Workshop metadata and the final file list.
Test the release locally before updating the Workshop item.
Publisher and Workshop in detail / Publishing
Common Publisher errors
Publishing
Common Publisher errors is a DayZ Tools reference entry for Publishing. Use it in the Publisher and Workshop in detail area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
Common Publisher errors belongs to the Publisher and Workshop in detail area and helps place the correct DayZ Tools workflow step.
Practical checks
Check mod.cpp, preview image, Workshop metadata and the final file list.
Test the release locally before updating the Workshop item.
Workbench in the DayZ Tools context / Environment
Script and resource orientation
Environment
Script and resource orientation is a DayZ Tools reference entry for Environment. Use it in the Workbench in the DayZ Tools context area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
Script and resource orientation belongs to the Workbench in the DayZ Tools context area and helps place the correct DayZ Tools workflow step.
Practical checks
Check the launcher, game path and Project Drive before starting an individual tool.
If a tool does not start, verify the DayZ Tools installation and local paths first.
Workbench in the DayZ Tools context / Environment
Understanding script compile errors
Environment
Understanding script compile errors is a DayZ Tools reference entry for Environment. Use it in the Workbench in the DayZ Tools context area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
Understanding script compile errors belongs to the Workbench in the DayZ Tools context area and helps place the correct DayZ Tools workflow step.
Practical checks
Check the launcher, game path and Project Drive before starting an individual tool.
If a tool does not start, verify the DayZ Tools installation and local paths first.
Workbench in the DayZ Tools context / Environment
Workbench and Project Drive relationship
Environment
Workbench and Project Drive relationship is a DayZ Tools reference entry for Environment. Use it in the Workbench in the DayZ Tools context area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
Workbench and Project Drive relationship belongs to the Workbench in the DayZ Tools context area and helps place the correct DayZ Tools workflow step.
Practical checks
Check the launcher, game path and Project Drive before starting an individual tool.
If a tool does not start, verify the DayZ Tools installation and local paths first.
Object Builder practical checks / PBO build
LOD check
PBO build
LOD check is a DayZ Tools reference entry for PBO build. Use it in the Object Builder practical checks area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
LOD check belongs to the Object Builder practical checks area and helps place the correct DayZ Tools workflow step.
Practical checks
Check the source folder, config.cpp, Addon Builder output and build log.
Keep work files, built PBOs and signed release files clearly separated.
Object Builder practical checks / PBO build
Named selections
PBO build
Named selections is a DayZ Tools reference entry for PBO build. Use it in the Object Builder practical checks area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
Named selections belongs to the Object Builder practical checks area and helps place the correct DayZ Tools workflow step.
Practical checks
Check the source folder, config.cpp, Addon Builder output and build log.
Keep work files, built PBOs and signed release files clearly separated.
Object Builder practical checks / PBO build
Memory points
PBO build
Memory points is a DayZ Tools reference entry for PBO build. Use it in the Object Builder practical checks area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
Memory points belongs to the Object Builder practical checks area and helps place the correct DayZ Tools workflow step.
Practical checks
Check the source folder, config.cpp, Addon Builder output and build log.
Keep work files, built PBOs and signed release files clearly separated.
Object Builder practical checks / PBO build
model.cfg relationship
PBO build
model.cfg relationship is a DayZ Tools reference entry for PBO build. Use it in the Object Builder practical checks area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
model.cfg relationship belongs to the Object Builder practical checks area and helps place the correct DayZ Tools workflow step.
Practical checks
Check the source folder, config.cpp, Addon Builder output and build log.
Keep work files, built PBOs and signed release files clearly separated.
Texture and material workflow with DayZ Tools / Texture and material
PNG/TGA -> PAA workflow
Texture and material
PNG/TGA -> PAA workflow is a DayZ Tools reference entry for Texture and material. Use it in the Texture and material workflow with DayZ Tools area to check paths, files, build output, signatures or Workshop steps before publishing.
ImageToPAA vagy imageToPaaGUI
Details
Purpose
PNG/TGA -> PAA workflow belongs to the Texture and material workflow with DayZ Tools area and helps place the correct DayZ Tools workflow step.
Related tool or path: ImageToPAA vagy imageToPaaGUI.
Practical checks
Check PAA format, texture size, alpha channel and RVMAT paths.
Keep source images and exported game textures separated.
Texture and material workflow with DayZ Tools / Texture and material
PAA check in TexView
Texture and material
PAA check in TexView is a DayZ Tools reference entry for Texture and material. Use it in the Texture and material workflow with DayZ Tools area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
PAA check in TexView belongs to the Texture and material workflow with DayZ Tools area and helps place the correct DayZ Tools workflow step.
Practical checks
Check PAA format, texture size, alpha channel and RVMAT paths.
Keep source images and exported game textures separated.
Texture and material workflow with DayZ Tools / Texture and material
RVMAT path check
Texture and material
RVMAT path check is a DayZ Tools reference entry for Texture and material. Use it in the Texture and material workflow with DayZ Tools area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
RVMAT path check belongs to the Texture and material workflow with DayZ Tools area and helps place the correct DayZ Tools workflow step.
Practical checks
Check PAA format, texture size, alpha channel and RVMAT paths.
Keep source images and exported game textures separated.
Terrain and CE tools in DayZ Tools / PBO build
Basic Terrain Builder workflow
PBO build
Basic Terrain Builder workflow is a DayZ Tools reference entry for PBO build. Use it in the Terrain and CE tools in DayZ Tools area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
Basic Terrain Builder workflow belongs to the Terrain and CE tools in DayZ Tools area and helps place the correct DayZ Tools workflow step.
Practical checks
Check the source folder, config.cpp, Addon Builder output and build log.
Keep work files, built PBOs and signed release files clearly separated.
Terrain and CE tools in DayZ Tools / Terrain and world
Terrain Processor purpose
Terrain and world
Terrain Processor purpose is a DayZ Tools reference entry for Terrain and world. Use it in the Terrain and CE tools in DayZ Tools area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
Terrain Processor purpose belongs to the Terrain and CE tools in DayZ Tools area and helps place the correct DayZ Tools workflow step.
Practical checks
Check terrain source data, CE structure, navmesh steps and exported files.
Use small test runs before publishing large world changes.
Terrain and CE tools in DayZ Tools / Terrain and world
NavMeshGenerator purpose
Terrain and world
NavMeshGenerator purpose is a DayZ Tools reference entry for Terrain and world. Use it in the Terrain and CE tools in DayZ Tools area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
NavMeshGenerator purpose belongs to the Terrain and CE tools in DayZ Tools area and helps place the correct DayZ Tools workflow step.
Practical checks
Check terrain source data, CE structure, navmesh steps and exported files.
Use small test runs before publishing large world changes.
Terrain and CE tools in DayZ Tools / Terrain and world
CE Editor purpose
Terrain and world
CE Editor purpose is a DayZ Tools reference entry for Terrain and world. Use it in the Terrain and CE tools in DayZ Tools area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
CE Editor purpose belongs to the Terrain and CE tools in DayZ Tools area and helps place the correct DayZ Tools workflow step.
Practical checks
Check terrain source data, CE structure, navmesh steps and exported files.
Use small test runs before publishing large world changes.
Which DayZ Tools utility to use and when / PBO build
Wrong or missing PBO content
PBO build
Wrong or missing PBO content is a DayZ Tools reference entry for PBO build. Use it in the Which DayZ Tools utility to use and when area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
Wrong or missing PBO content belongs to the Which DayZ Tools utility to use and when area and helps place the correct DayZ Tools workflow step.
Practical checks
Check the source folder, config.cpp, Addon Builder output and build log.
Keep work files, built PBOs and signed release files clearly separated.
Which DayZ Tools utility to use and when / PBO build
Build fails
PBO build
Build fails is a DayZ Tools reference entry for PBO build. Use it in the Which DayZ Tools utility to use and when area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
Build fails belongs to the Which DayZ Tools utility to use and when area and helps place the correct DayZ Tools workflow step.
Practical checks
Check the source folder, config.cpp, Addon Builder output and build log.
Keep work files, built PBOs and signed release files clearly separated.
Which DayZ Tools utility to use and when / Key and signature
Client is kicked with a signature error
Key and signature
Client is kicked with a signature error is a DayZ Tools reference entry for Key and signature. Use it in the Which DayZ Tools utility to use and when area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
Client is kicked with a signature error belongs to the Which DayZ Tools utility to use and when area and helps place the correct DayZ Tools workflow step.
Practical checks
Keep the private key safe and publish only the matching .bikey file.
Sign every release PBO again and place the public key in the server keys folder.
Which DayZ Tools utility to use and when / Texture and material
Texture does not appear
Texture and material
Texture does not appear is a DayZ Tools reference entry for Texture and material. Use it in the Which DayZ Tools utility to use and when area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
Texture does not appear belongs to the Which DayZ Tools utility to use and when area and helps place the correct DayZ Tools workflow step.
Practical checks
Check PAA format, texture size, alpha channel and RVMAT paths.
Keep source images and exported game textures separated.
Which DayZ Tools utility to use and when / Modeling
Model error
Modeling
Model error is a DayZ Tools reference entry for Modeling. Use it in the Which DayZ Tools utility to use and when area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
Model error belongs to the Which DayZ Tools utility to use and when area and helps place the correct DayZ Tools workflow step.
Practical checks
Check LODs, named selections, memory points and the model.cfg link.
Test the model after changes in a small isolated build.
Which DayZ Tools utility to use and when / Publishing
Workshop upload problem
Publishing
Workshop upload problem is a DayZ Tools reference entry for Publishing. Use it in the Which DayZ Tools utility to use and when area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
Workshop upload problem belongs to the Which DayZ Tools utility to use and when area and helps place the correct DayZ Tools workflow step.
Practical checks
Check mod.cpp, preview image, Workshop metadata and the final file list.
Test the release locally before updating the Workshop item.
Minimal pre-publish checklist / Modding reference
Minimal pre-publish checklist
Modding reference
Minimal pre-publish checklist is a DayZ Tools reference entry for Modding reference. Use it in the Minimal pre-publish checklist area to check paths, files, build output, signatures or Workshop steps before publishing.
Details
Purpose
Minimal pre-publish checklist belongs to the Minimal pre-publish checklist area and helps place the correct DayZ Tools workflow step.
Practical checks
Check the relevant paths, source files and tool outputs.
After a failed run, read the newest logs first.
FAQ
Frequently asked questions about DayZ Tools and PBOs
DayZ modding
When is PboViewer enough, and when do I need Addon Builder?
PboViewer is useful for quick inspection, listing, unpacking and simple tests. For a public DayZ mod release, keep Addon Builder/Binarize, signing, .bisign and .bikey checks in the workflow.
Does PboViewer replace BankRev?
Not necessarily. BankRev belongs to the DayZ Tools environment, while PboViewer is an external cross-platform alternative. Both are mainly useful for checking and analyzing PBO files.
Can I unpack another mod author's PBO?
Technically this is often possible, but use it only for troubleshooting, dependency checks or learning. Do not reuse or republish someone else's mod content without permission.
Why does a PBO need to be signed?
With verifySignatures enabled, the server checks whether the PBO, .bisign and server-side .bikey match. Missing or wrong signatures can cause signature, modified-data or PBO-mismatch kicks.
What should I check before a Workshop or server release?
Check config.cpp, requiredAddons, folder structure, PBO content, .bisign, the .bikey in the server keys folder, old deploy files and fresh client/server logs.
What do packFolder, unpackFolder and listFiles mean?
packFolder creates a PBO from a folder, unpackFolder extracts a PBO, and listFiles lists the PBO content without forcing you to browse everything manually.
What if the PBO builds, but the mod does not work?
Common causes are wrong paths, missing requiredAddons, old PBO/bisign files, missing .bikey, wrong server launch parameters or fresh script/config errors in the logs.
Should I use PboViewer for the final build?
For testing and inspection, yes. For a final DayZ mod release, the conservative workflow is Addon Builder/Binarize, DSUtils signing, then release PBO and signature verification.