Keyboard shortcuts

Press or to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

hemtt build

Build the project for final testing

Usage: build [OPTIONS]

Options:
      --no-bin             Do not binarize the project
      --no-rap             Do not rapify (cpp, rvmat, ext, sqm, bikb, bisurf)
      --just <JUST>        Only build the given addon
  -t, --threads <THREADS>  Number of threads, defaults to # of CPUs
  -v...                    Verbosity level
  -h, --help               Print help (see more with '--help')

Description

Build the project for final testing

hemtt build will build your mod into .hemttout/build. It will binarize all applicable files, and will not create folder links like hemtt dev.

It is intended to be used for testing your mod locally before release.

Binarization

By default, supported file types are converted to their binary formats for optimal game performance. This process is slower but produces smaller, faster-loading files similar to BI's official addons.

Configuration

.hemtt/project.toml

[hemtt.build]
optional_mod_folders = false # Default: true

optional_mod_folders

By default, hemtt build will create separate mods for each optional mod folder.

Arguments

--no-bin

Do not binarize the project

Files will be copied directly into the PBO without binarization. config.cpp, *.rvmat, *.ext, *.sqm, *.bikb, *.bisurf will still be rapified. This can be configured per addon in addon.toml.

Useful for faster builds during testing when you don't need optimized file formats.

--no-rap

Do not rapify (cpp, rvmat, ext, sqm, bikb, bisurf)

They will be copied directly into the PBO. This can be configured per addon in addon.toml.