One of my old time favorite games is Jagged Alliance 2.
It is a wargame where you command a small team of mercenaries that fights a war against an evil enemy.
It is not a shooter that centers on speed and aiming, but a tactical game that focuses on tactical manoeuvering and some strategic teambuilding.
Combined with plenty of humor and an excellent user interface, this makes for a pleasurable experience with high replayability.
The game title, original by Sir-Tech, has been sold and resold several times to different publishers, but none have taken up further development to the point where they actually produce new versions. But a small team of independent enthusiasts has produced a mod that is so good that it actually plays like a solid upgrade of the original. This is the v 1.13 mod. For me, it revived interest in a game that I already played too many times.
Jagged Alliance 2 v1.13 comes with a several long list of hirelings, weapons and equipment that can be used in the game. To help myself sort things out, I made some tables that lists all those three. They include the most essential stats, layed out in a handy table format. Since the v1.13 builders made their mod available for free, I thought I should do the same with my tables. So here there are:
- Richard's Jagged Alliance 2 v1.13 build 7609 weapon table
- Richard's Jagged Alliance 2 v1.13 build 7609 load bearing equipment table
- Richard's Jagged Alliance 2 v1.13 build 7609 hirelings table
If you play the v1.13 mod or intend to, use them to your own advantage.
If you want a different sorting than the original, copy and past from the HTML into a spreadsheet program and use its sorting capabilities.
The weapons table includes stats for almost all weapons. All stats have been compiled from the game's original xml files, except the AP costs, which I have gathered during gameplay, as I cannot figure out the exact formulas that the developers used. A handful weapons I could not get my hands on during play, notably the XM-8 guns and some weapons from Unfinished Business. For these, AP costs and final score are missing. I hope to add them at a later stage.
The table also includes a score that indicates the overall quality of each weapon. This is calculated using a medium difficult formula, that tries combine multiple stats into one. Experienced Jagged Alliance players will point out that all different pros and cons of weapon simply cannot be crammed into a single score. They are of course right. There are too many variables in the game that influence the overall effectiveness of a weapon; this is part of the fun of playing it. But the overall score can serve as a general indication, which is what I am using it for. If you want to find out how the score is calculated, you will have to dig into the formula itself.
The tables were built using XSLT 1.0, transforming the original XML files to HTML by using the Microsoft .NET XSLT-processor from a Powershell script. If you are familiar with these technologies, or a not afraid to learn a little of them, and you want to rebuild the weapon table to your own preferences, then gather the following files.
For the weapons table:
- AmmoStrings.xml from the v1.13 data files
- Attachments.xml from the v1.13 data files
- Items.xml from the v1.13 data files
- Weapons.xml from the v1.13 data files
- weapons_rl.xml from this website. This lists types and AP costs that I could not find in the original xml files.
- WeaponType.xml from the v1.13 data files
- weapons.xsl from this website.
For the LBE table:
- Items.xml from the v1.13 data files
- lbe_rl.xml from this website. This lists LBE descriptions and some other stats that were buried too deep in the original xml files.
- LBE.xsl from this website.
For the hirelings table:
- MercProfiles.30-05-2015.xml from the v1.13 data files
- Hirelings.xsl from this website.
Put all files in the same directory. Transform Weapons.xml with weapons.xsl to an html file; lbe_rl.xml with LBE.xsl; MercProfiles.30-05-2015.xml with hirelings.xsl. The primary xml files will automatically include all other xml files needed for the transformations, provided they can be found in the same directory. Use the .NET XSLT processor, from Powershell, program code or some other source, to execute the transformations. If you want you can use another XSLT processor, but then you need to 'node-set' function inside the xslt with something equivalent. Many XSLT processors offer an equivalent node-set function. If you are not afraid of a little XSLT, you can change the layout, the ordering and/or the score formula.