hemtt release

Build the project for release

Usage: hemtt [OPTIONS]

Options:
      --no-bin             Do not binarize the project
      --no-rap             Do not rapify (cpp, rvmat)
      --no-sign            Do not sign the PBOs or create a `bikey`.
      --no-archive         Do not create a zip archive of the release
  -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 release

hemtt release will build your mod into .hemttout/release. It will create bisign files for all addons, and a bikey for validation.

It is intended to be used for releasing your mod.

It will create two zip archives in the releases folder: - {name}-latest.zip - {name}-{version}.zip

Configuration

hemtt release is built the same way as hemtt build, and will use its configuration.

[hemtt.release]
sign = false # Default: true
archive = false # Default: true

sign

If sign is set to false, a bikey will not be created, and the PBOs will not be signed.

Danger

All public releases of your mods should be signed. This will be a requirement of many communities, and is an important security feature. Do not use this unless you know what you are doing.

Arguments

--no-bin

Do not binarize the project

They will be copied directly into the PBO. config.cpp, *.rvmat, *.ext will still be rapified. This can be configured per addon in addon.toml.

--no-rap

Do not rapify (cpp, rvmat)

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

--no-sign

Do not sign the PBOs or create a bikey.

Danger

All public releases of your mods should be signed. This will be a requirement of many communities, and is an important security feature. Do not use this unless you know what you are doing.

--no-archive

Do not create a zip archive of the release.

The output will be in .hemttout/release.

The HEMTT Book