In-game settings for my mods. Each mod ships a schema; this builds it into a page of toggles, sliders, colour pickers and drag-to-position handles.
The mods that use it treat it as a hard dependency — without it they disable
themselves and say so in python.log.
The panel is a battle element, so it appears in battle. It starts at the top-left and drags anywhere. Mods with their own gear button open straight to their page.
It is listed in-game under its old name, TTaro Mod Config.
Settings are saved to (wows)/ModPrefs/, outside res_mods — a game update does not
touch them, and settings from older versions migrate on first launch.
Important
Needs ModForge. It reads ForgeBlueprints/TTaroModUtils.xml
and mounts the panel into the battle UI — without it the mod loads and the panel never appears.
One copy of ModForge serves every mod that uses it.
- Download a zip.
- Unzip the archive. You get the
gui,PnFMods,ModSchemasandForgeBlueprintsfolders andPnFModsLoader.py. - Move them to
(wows)/bin/(latest_number)/res_mods/. The path then looks likeres_mods/PnFModsLoader.py. - Done. Every other mod adds its own page when you install it.
Warning
These files are generated by my own config tool. Do not edit them, and do not copy one
into another mod: the id inside names the player's settings file, so a reused id makes
the framework refuse both mods' settings. Trouble from an edited or copied schema is
not a bug in my mods.