mirror of https://github.com/1dot13/source.git synced 2026-08-05 14:00:23 +02:00

Files

T

* 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>

2026-08-01 11:05:15 -03:00

3.8 KiB

Raw Blame History

JA2 v1.13

Preamble

Jagged Alliance 2 v1.13 is a modification for the Jagged Alliance 2 game.

Original development was done through SVN, this however ended abruptly in 2022, to keep the development going the step to Github has been made.

Feel free to participate in the development!

For more information you can visit the following locations:

In case of any issues, look at Reports or Participation

Downloads

Note

All-in-one releases come for different languages and include JA2 v1.13, the Map Editor and JA2 Unfinished Business.

Visit the releases page to download the latest all-in-one.

Installation

Install the original Jagged Alliance 2
Download the latest all-in-one release and copy its content to JA2 game directory.
Modify ini settings if you like.
Play the game.

Some additional information on can be found in folder "docs" inside download.

If you face issues with higher resolutions, alt+tab not working, blackscreen, etc.,
run the "cnc-ddraw-config.exe" in game-folder and adjust settings to your liking.
(those issues can occur due to the combination of old game and modern OS/hardware, cnc-ddraw helps to avoid those)

Visual Studio setup

Run Visual Studio 2019 or newer.
Clone and open the location with the source code using one of these two options:
- Click Clone a repository
  - Enter git@github.com:1dot13/source.git or https://github.com/1dot13/source.git in the Repository location field, select the path you want to clone the repository to and click Clone.
  - Double-click on Folder View in the Solution Explorer
- Click Open a local folder
  - Use this option if you already cloned the repository yourself.
Visual Studio will automatically detect the CMake configuration files and will run the CMake generation. There will bet a CMake error in the logs saying No existing preset was found, copied a preset template to [some_path]. This is normal and only happens once.
Click on the dropdown that says x64-Debug and select Manage configurations.... This should trigger Visual Studio to load the CMakeUserPresets.json file it just copied. Now you can close the window for managing the configurations.
The x64-Debug option should have been replaced by 1dot13 Debug. Click it and select Manage configurations... again. Here is where you configure the language for the built executables as well as which ones to build, Most important, here is where you set CMAKE_RUNTIME_OUTPUT_DIRECTORY to the path to your JA2 1.13 installation. This will be used for debugging. Note that the path needs to have a working 1.13 installation, and that includes the 1.13 game data.
You can use Build -> Build All to build the executables you selected in the configuration.

Reports

For more information and reports, visit Bug reports at Bear's Pit Forum or join the Bear's Pit Discord

Participation

Feel free to participate on GitHub. If you want to know how, or simply wanna share your thoughts on a topic join the Bear's Pit Discord

3.8 KiB Raw Blame History