Per-mod output, packaging script, fix requiredAddons CfgPatches names
- Split single config.cpp into per-mod output/<mod>/config.cpp files
- Use original CfgPatches class names (not sanitized folders) in requiredAddons
- Skip 'unknown' source_mod from requiredAddons
- Add scripts/package_mod.py with armake2 PBO packing
- Add package_mod.ini for configurable mod packaging
- Use {} array syntax instead of [] for Arma config compatibility
This commit is contained in:
@@ -51,11 +51,11 @@ Creates `data/[mod_name]/` folders with per-mod CSVs. Baseline mods (`_rhs`, `_v
|
||||
python scripts/generate_patches.py
|
||||
```
|
||||
Produces:
|
||||
- `output/config.cpp` — CfgPatches config with overrides
|
||||
- `output/<mod>/config.cpp` — Per-mod CfgPatches config with overrides
|
||||
- `output/unmatched.csv` — Items with no RHS equivalent (review manually)
|
||||
|
||||
### Step 5: Load in Arma
|
||||
Drop `output/config.cpp` into an `@mod/addons/config.cpp` structure and load it.
|
||||
Drop the `output/` folder contents into `@mod/addons/<mod>/config.cpp` structure and load it. Each subfolder is an independent addon with its own CfgPatches dependency.
|
||||
|
||||
## How the scripts work
|
||||
|
||||
|
||||
Reference in New Issue
Block a user