hemtt dev

Build the project for development

Usage: dev [OPTIONS]

Options:
  -o, --optional <OPTIONAL>  Include an optional addon folder
  -O, --all-optionals        Include all optional addon folders
      --no-rap               Do not rapify (cpp, rvmat, ext, sqm, bikb, bisurf)
  -b, --binarize             Use BI's binarize on supported files
      --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 development

hemtt dev is designed to help your development workflows. It will build your mod into .hemttout/dev, with links back to the original addon folders. This allows you to use file-patching with optional mods for easy development.

Configuration

.hemtt/project.toml

[hemtt.dev]
exclude = ["addons/unused"]

exclude

A list of addons to exclude from the development build. Includes from excluded addons can be used, but they will not be built or linked.

Arguments

-o, --optional <OPTIONAL>

Include an optional addon folder

This can be used multiple times to include multiple optional addons. Optional addons are stored in the optionals/ directory and can be used to separate compatibility patches or features that not all users need.

hemtt dev -o caramel -o chocolate

-O, --all-optionals

Include all optional addon folders

Builds all addons from the optionals/ directory in addition to main addons.

--no-rap

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

They will be copied directly into the PBO, not .bin version is created.

-b, --binarize

Use BI's binarize on supported files

By default, hemtt dev will not binarize any files, but rather pack them as-is. Binarization is often not needed for development.