To be placed inside the OpenFodder/Run directory.
This repository packages the complete runtime resources: Data/, Campaigns/,
Scripts/ (a pinned submodule), and about.png. No separate scripts release is
needed. Retail game files and user saves are not included.
Before tagging a release, commit the intended Scripts submodule revision and
the root compat.json. Its data and script versions describe engine compatibility,
not the release tag; both are currently 1.
Build locally with Python 3:
git submodule update --init --recursive
python Tools/BuildRelease.py --version 1.9.0Upload both dist/OpenFodder-data-1.9.0.zip and dist/compat.json to the same
GitHub release. Tag pushes run this packaging automatically, including the
submodule contents that GitHub's automatic source ZIP omits. For a manual run,
choose the branch/ref to package and enter the release tag as version. Enable
Publish release assets to attach the package to that tag, replacing existing
assets. Leave it disabled to build workflow artifacts only. Manual runs package
the selected checkout, so choose the intended release contents. The release tag
must already exist when publishing.
The workflow skips forks entirely. Packaging has read-only repository permissions;
only the separate publishing job can write releases. It runs for version-tag pushes
or explicitly opted-in manual runs in OpenFodder/data. Branch pushes and pull
requests do not trigger it.
The ZIP extracts directly into the runtime root, alongside openfodder.exe for
portable installs. It has no outer repository directory. The packager generates
matching root and subtree installation records. Only Git-tracked runtime files
are included; local scratch files, executables, and saves are excluded.
Automatic installation of this complete bundle requires an engine with the unified data downloader. Earlier split downloaders cannot install this layout.