Precursor is a full scale test suite for evaluating the functionality and capabilities of TagTool-NET

Throughout the course of updating and extending the functionality in TagTool, I needed a way of testing functions across all supported uses cases. This included all supported cache generations and all supported engine versions. Precursor essentially acts as a wrapper for TagTool's code, and allows me to extend it and implement small or large scale unit tests, without having to modify or rework TagTool's underlying codebase.

By default, Precursor is setup to pull the paths for each supported engine version from the specified input file.

The paths for each build should only contain the cache files themselves, and any other dependencies located inside the maps folder of most Blam! engine titles (fonts, map info, images, texture or sound resource files, etc).

The Blam! titles supported by Precursor line up roughly with engine versions currently supported by TagTool-NET.

Default build paths refer to the default paths defined in the Docs\build_paths.cmds script. These are purely to be used as a reference for how to structure the builds, though realistically any file path will function correctly.

If multiple builds reference the same default path, it means that anyone of those builds can be placed in the input path, and Precursor will still recognise it as a valid build for the specified TagTool Cache Version.

MCC cache files are handled differently from all other builds. Since MCC uses a static folder structure for all its supported engine versions, the only input required is the path to the base MCC installation directory.