* prepare gamedir for running the game
* Stop telling installers to overwrite the vanilla game
The release no longer contains anything that lands on a vanilla file:
its base data lives in Base, so unpacking it over the game directory
and copying the game's Data into the release now amount to the same
installation.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
* Give the mod's base data its own VFS profile
Its files ship in Base now, so that a vanilla Data directory can be
copied in whole without a single collision. Mount Base right above the
vanilla dirs in every profile stack — the slot where the installer's
overwrites used to end up.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
* Mount Base in the language overlays' VFS configs too
Assembling a release copies a <Language>_Version directory over
gamedir, its own copies of the configs included, so without the same
Base profile every non-English release would mount nothing from Base.
Their libraries move along with the rest of the base data: each
language slf, and the Russian data.slf that shadows the vanilla
Data.slf by name.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
* Ignore a vanilla Data directory dropped into gamedir
Running the game here needs one copied in, and it is an untouched copy
of somebody's retail install — nothing this repository should track.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
* Ignore only the player profile directory, not every Profiles
The unanchored pattern also swallowed Base/TableData/Profiles, the
mod's soldier profile XMLs, which are tracked and belong in a release.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
* move gamedir/Data to gamedir/Base
* move gamedir-languages' Data to Base
---------
Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
