Alef/modmixer – User

WIP (nearly RIP)

Idea

A program that take as input downloaded mods (.zip, .7z, .rar, .pbo) and produce more .pbo given a command file.

The "command file" is the "recipe" for the mix. A recipe would be created by someone, the resulting PBO files signed, and both put online (the recipie + the .bisignS).

Players can download them and produce their own mix, based on the recipe. The key will validate the PBO files, because we suppose the input file are the very same and the output too.

All of this should skip the need to obtain permissions from mod authors for incorporate their works. People will download their mods as usual, the websites will have their ads shown, their download counts.

Workflow

The "cook" will mix some mods through the application, producing a recipe. The recipe is a text file with zip/pbo/config references, in order. With the resulting PBO files, and the author private key, a .bisign key is created. The recipe and the key are then put online.

A player wants to try that "mix". He downloads the recipe and the key. Then, download the "ingredients" mods, as required by the recipe. With modmixer, he produces the same PBO files the cook created at his time. These, together with the downloaded recipe key, goes in some @modfolder/AddOns.

In MP, if the server has the cook's public key, the PBO files above will be trusted.

Assumptions

• PBOs do not contain time-dependant information, that is, no timestamps or info like that. This is needed to produce the very same pbo as the cook, byte by byte.

Analysis

• Recipe
  • a text file. Doesn't need to be human readable. Can be quite long. Optionally zipped (libz in boost_ios?).
  • content:
    • human readable list of mods for input, with optional URLs. No unattended downloads.
    • for each target pbo
      • list of sources pbo
      • list of dup config values to copy in
      • bspath to apply on resources
      • ...
• I/O
  • don't uncompress stuff in temp directories, try to do everything in memory/buffer
    • use 7z.dll
  • pbo
    • • read needed pbo from zipped files
      • write the final PBOs
        • PBOs need to be ordereed as the recipe says. Respect their $PREFIX$.
    • config.bin
      • unrap config.bin files from pbo from zipped files
    • boost::wave
      • preprocess config.cpp
      • need special filesystem for buffered archives/pbo entries
      • may need access to real ArmA\ directory (found by BI regkey) ?
• config.cpp
  • preprocessor
  • parser
  • write new configs based on the recipe