QueryAddons Version 1.xx by Mikero

see readMeGeneral

see fixes

QueryAddons works on individual files, folder(s), or pbo's

QueryAddons works on mission.sqms and/or config.cpp/bin's

file types can be raPified or normal text.

The default use of QueryAddons is to provide a list of addon dependencies for that mission.sqm or config.cpp/bin

it inspects addons[]= and AddonsAuto[]= in mission.sqm. and RequiredAddons[]= in configs

Folder usage is similar. It's intent is to reflect an exploded, or, yet-to-be-made, pbo. Particularly useful for campaign inspection

The files are hunted recursively thru all sub folders (if any)

Pbo usage should be self explanatory, in that QueryAddons is looking inside, as if it were a folder tree.

useage

QueryAddons [-options] File/Folder/OrPbo

Name can be

config.cpp or

config.bin or

mission.sqm or

NameOf[.pbo] or

NameOfFolder

Options (Optional)

-n csv Output);

-a List Addons (default)

for configs only

-u Units

-w Weapons

-v RequiredVersion

-c ClassName(s) of the addon

config options are aggregated, you can, specify

QueryAddons -aucwv .....

Special considerations:

Pbos are NOT checked or looked for in folder tree mode. It would be illogical to list addons from more than one.

In the unlikely event that both a mission.sqm, AND, a config.cpp is encountered in a pbo or folder. BOTH will make up the list.

Comma Separated Output

csv output (if any) is intended to feed a database, either directly, or, via pipe > .csv

if csv is specified, the type of query (units,weapons eg) is not listed

Config options

are only relevant when config.cpp/bins are encountered. The results of specifying them for mission.sqm's is in-determinate.