Building from Source (HEMTT) - Theseus-Aegis/TheseusServices GitHub Wiki

• Arma 3
• Arma 3 Tools (available on Steam)
• Run Arma 3 and Arma 3 Tools directly from Steam once to install registry entries (and again after every update)
• HEMTT (>=v1.5.1) in in project root (Windows users can double-click tools/setup.bat)
  • hemtt (Linux) or hemtt.exe (Windows)

Replace hemtt with hemtt.exe on Windows.

• Open terminal (Linux) or command line (Windows)
• Run $ hemtt build to create a test build (Windows users can double-click build.bat)
• Run $ hemtt release to create a release build
  • Only Windows release builds are currently supported due to binarization!
• Run $ hemtt dev to create a development build with file patching
  • mklink /J <Arma 3>\x\tac <TAC_Mods>/.hemttout/dev (/D instead of /J for network paths)
  • $ hemtt launch is not supported. Use ArmaQDL.

File Patching allows you to change the files in an addon while the game is running, requiring only a restart of the mission. This makes it great for debugging, as it cuts down the time required between tests. Note that this only works with development build.

To run Arma 3 with file patching add the -filePatching startup parameter.

Files must exist in the built PBOs for file patching to work. If you create a new file you must rebuild the PBO or Arma will not find it in your file paths.

Configs are not patched during run time, only at load time. You do not have have to rebuild a PBO to make config changes, just restart Arma. You can get around this though if you are on the dev branch of Arma 3 and running the diagnostic exe. That includes diag_mergeConfig which takes a full system path (as in p:\x\tacs\addons\my_module\config.cpp) and allows you to selectively reload config files.

Adapted from the ACE3 documentation.