Company of Heores 3 Data

Data and icons on all Company of Heroes 3 units / stuff in a developer friendly format.

Goal

Goal of this repository is to gather all the data from the game Company of Heroes 3. For example data for all units. As well as tools and scripts for gathering this data from the game. We beliave that open sourcing all the data and tools can only help the game and community. Once we have the data it's up to anyone to build any web-site or apps and work with this data. But let's put all our heads together

Convention

• All the data should be converted into .json files
• Please provide all the scripts / add manuals how you get the data
  • We can expect a lot of updates from developers. So we will need to run our scripts many times.
• We shall do git tags to mark patch changes
• The tags are in the format v1.0.7-1, where 1.0.7 should match the game patch version, -x (marks our revision). So v1.0.7-1 means game patch 1.0.7, data revision 1.

Downloading the data

If you want to utilize the data in the build / download them periodically. Please use this URL:
https://data.coh3stats.com/cohstats/coh3-data/${dataTag}/data/${dataFile}

• dataTag is the tag in this repo
• dataFile is the file from the data folder in this repo

So for example the url could look like this: https://data.coh3stats.com/cohstats/coh3-data/v1.2.5-1/data/battlegroup.json

Contribution

We are looking for more help! If you would like to contribute in any way. Please rech out ot us here in the issues / on the discord https://discord.gg/jRrnwqMfkr

Also if you utilize the data, please give us shoutout! Thank you

How to generate the data

1. Open Company of Heroes 3 Essence Editor (it's located in your COH3 instalaltion folder).

2. One file ReferenceAttributes.sga ...\Company of Heroes 3\anvil\archives\ReferenceAttributes.sga

3. Click on the attrib field, right click, extract
   

4. Delete content of folder xml in this repo,

5. Extract it into folder xml of this repository. Should look like this:
   

The locstrings must be exported as well, but requires the following steps:

1. Within the Essence Editor, click "Attributes" in the menu panel then click "Open Attributes". Wait for it to completely load.
2. Open any attribute file (ebps is opened by default) then click "View" -> Show LocString Report... in the menu panel.
3. With the opened locstring table, select the first column then scroll to the last one and press "Shift" to select all (alternatively Ctrl + A). Then right click, copy or Ctrl + C then paste the content inside the xml/loc_english/locale.txt file of this repository.

Convert the data

1. Go into folder cd scripts/xml-to-json.
2. Run Python script main.py. You need python3. Like this python main.py, you should see this result:
   
3. Check the folder, you should see exported files.

Hint: python main.py -no_bl disables blacklist filter and generates complete JSON files. However, when possible, the filtered JSON files should be used to reduce file size.

You can verify the changes by running command git diff

Changes after the patch

1. Generate the data into folder /data
2. Make an MR with the changes

The folder /data should always have the stable export of the data.

Folder chunked

Folder chunked has the big json files split to a smaller files for better manipulation.

How to add/fix missing data not delivered by the Essence Editor

Some times it is nessecary to add some modifications to the XML as not all informations are delivered by relic. E.g. Stormtroopers are spawned with an lmg but there is no lmg member referenced within the loadout of the sbps. For that we created a CoH3 tuning mod which can be adoptet to overwrite missing information.

1. Open the mod from the projects xml directory with the Essence Editor

2. Clone the attribute file that needs to be modified and assign a name. If the mod file has the same name as the original file, the extensions will overwrite extensions from the orginal otherwise, a new json object will be created for that element.

3. Modify the cloned file which will appear in the corresponding Mod directory. You can also delete some extensions which are not required at all to reduce traffic.

4. Save the mod. When the steps of How to generate data are performed, the modifications will be added or overwrite the original data during the json generation process (see step 6 above).

Hint: Overwriting can be skipped during script execution via -no_mod flag. Be aware after patches, the overwriting mod might need to be adopted to reflect Relics patch changes. Thus, choose the files to modify wisely.

References:

Big thanks to all open source tools focused on Relic games. https://github.com/RobinKa/RGDReader/tree/master/RRTexConverter