Save addons required to view the replay back in game

[AdamTadeusz]

Using the steam workshop mod Ocap2Arma, one can view a replay of a mission saved using OCAP2 within Arma 3. While it is relatively easy to figure out what map needs to be loaded from the "worldName" field, the mods required to display everything correctly have to be worked out by delving into the replay and looking at the names of vehicles, weapons etc.

A solution to this could be to save a list of all the mods that were required by the server during recording in a separate field in the json file recorded by OCAP2, which could look something like this:

Since mods can change, vehicles added, renamed and removed etc, it would be useful to save the version of the mod used, though steam workshop support for addon versioning is not great and it is impossible to use steam to download an older version of an addon, so this would have to be done via other means to play the replay back faithfully.

[indig0fox]

Recommendation:

1. Pull allAddonsInfo and getLoadedModsInfo
2. for loop to iterate allAddonsInfo
3. Save version
4. Use modIndex to select index from getLoadedModsInfo, from which to grab modName and itemID (workshop ID)

Other ideas/notes:

• consider whether large modlists and extended information in recording.json may reduce available space for recording data. information can likely be truncated to an array of itemIDs and plugged into a preset generator instead
• the 'addon revision version'/version tag from allAddonsInfo may refer to a Steam version hash or something compiled in the addon itself, but to @AdamTadeusz 's point, has limited usefulness in differentiating file versions. storing the hash may allow power users to cross check and identify if their files match the originals, but not sure if the space usage would be worth it outside of internal mods
• there's also an option to store more metadata for a recording during the upload - i.e. in SQLite, rather than the recording file. this may cause some issues with data migrations/restores etc, but may be an alternative if information more than just itemIDs is desired. this would require modifications for the addon to send to extension, extension to receive/store, then send in a payload to the webserver, and webserver to receive and store as new JSON string column of the db (and ensure the schema is updated to include the new column at launch)
• if a specific use case is present, i.e. checking specific versions of specific mods known at mission runtime through variables or configs and beyond the base workshop publication info, the custom events framework can be used to make sure this or any other info is added to the recording