Panzer Corps Toolkit — Summary of additions, fixes, and improvements since v1.9.8.5
Since v1.9.8.5, the Panzer Corps Toolkit has grown substantially, especially in the areas of Unit Paint Studio, campaign-army management, doctrine generation, equipment editing, localization, and installer safety.
Unit Paint Studio
The Unit Paint Studio received major improvements to file handling and insignia replacement.
Unit skinning now works correctly with icons stored in:
the installed program folder;
the user’s Documents folder;
OneDrive-backed folders;
any custom location selected by the user.
The selected icon’s exact full path is now treated as authoritative, preventing the program from silently substituting a similarly named file from the installation folder.
Mask lookup was improved so the program checks:
for a matching mask beside the selected icon;
the user mask library in Documents;
the installed fallback mask library.
The Studio Folders browser was also improved:
a visible Select Unit for Painting command was added;
mask files ending in _Mask.png cannot be selected as unit icons;
double-clicking a valid icon opens it directly;
custom, Documents, OneDrive, and installed folders are supported.
Insignia replacement was substantially refined. The program now correctly handles both compact replacement regions and older fragmented masks by grouping nearby blue mask areas separately for each sprite view. Insignias are proportionally scaled, centred, and rendered with transparency and opacity controls.
Custom insignia assets were added for:
United Kingdom;
Belgium;
France;
Greece;
Italy;
Slovakia;
Soviet Union.
These are installed into:
Documents\Panzer Corps Toolkit\Unit Paint Studio\Insignia
Existing user-edited insignia files are preserved.
Campaign Army Reinforcements
The Reinforcements Editor gained a dedicated Add Bonus Unit feature.
It now allows bonus equipment to be added explicitly to an imported campaign army while keeping normal reinforcement generation rules unchanged.
The bonus-unit picker:
shows only equipment containing the bonus trait;
limits available nations to those already present in the imported army;
supports multi-nation campaign armies;
provides Nation, Class, and unit-name filters;
preserves equipment ID, nation, class, and custom-name information;
does not consume reinforcement budget or ordinary purchase limits;
supports Undo and Redo;
warns before accidental duplicates.
Bonus entries now display readable nation, class, unit name, and equipment ID information.
Upgrade Generator
The Upgrade Generator was updated to handle imported bonus units correctly.
Bonus units can now upgrade only to:
another unit containing the bonus trait;
equipment belonging to the same nation;
equipment satisfying the normal date, class, series, and cost rules.
The generator no longer allows:
bonus units to upgrade into normal equipment;
normal units to upgrade into bonus equipment;
foreign-nation bonus replacements.
Custom names, experience, strength, heroes, and other campaign-state information remain preserved during upgrades.
When no valid bonus replacement exists, the unit remains unchanged and the generator explains why.
Army Doctrine Generator
The Doctrine Generator was extensively expanded.
Italy was added alongside the existing doctrine nations:
Germany;
Poland;
France;
United Kingdom;
Soviet Union;
United States;
Italy.
Detailed year profiles were added for the period 1938–1946.
Doctrine posture selection was introduced:
Offensive;
Defensive;
Breakthrough;
Reserve.
Posture now modifies the national and yearly doctrine by influencing:
class proportions;
mobility;
artillery support;
anti-tank and anti-aircraft support;
reconnaissance;
equipment age and quality;
transport behaviour;
rarity weighting;
air support.
Doctrine definitions were moved into an editable DoctrineProfiles.json file.
The program now provides commands to:
open the doctrine file;
reload it;
validate it;
restore the default version.
Invalid JSON or invalid doctrine values produce readable validation errors instead of crashing the generator.
A Doctrine Explanation section was added. It reports:
the nation and year profile used;
the selected posture;
class and support priorities;
equipment-age and mobility bias;
rarity handling;
transport behaviour;
why units were selected or omitted.
Generated doctrine armies now enforce strict uniqueness by equipment ID. The same equipment entry can never appear twice.
When there are not enough eligible unique units, the generator creates the largest valid army possible and reports the shortfall instead of inserting duplicates.
Class allocation was also improved. Simple rounding was replaced with a largest-remainder method, preventing low-percentage classes such as fighters and tactical bombers from being consistently rounded down to zero.
Doctrine profiles can now define minimum class quantities, for example one fighter or one tactical bomber, provided eligible equipment exists.
The Equipment File Editor (new feature)
The Add Unit window now includes:
every major equipment field;
a scrolling vertical layout;
a full Traits section;
custom traits;
Remove Traits;
Series;
a Usable Transports section;
automatic .png handling for icon filenames;
several insertion-position options;
proper nation and class binding;
date validation;
confirmation before insertion;
automatic preparation for the next unit.
Supported insertion positions include:
top of the equipment list;
bottom of the list;
bottom of the selected nation;
bottom of the selected class within a nation;
above a selected equipment ID;
below a selected equipment ID.
The editor now preserves the original equipment file structure as closely as possible.
Saving was improved to avoid file-lock errors. Files are now written through a temporary file, validated, backed up, and then replaced safely.
The editor’s Validate command was expanded to check equipment dates using the exact required format:
DD.MM.YYYY
Validation now reports:
invalid dates;
the affected equipment ID;
the affected field;
the invalid value;
the required format;
mixed date formats;
end dates earlier than start dates.
Validation never silently changes the file.
Negative Air Attack values are also handled correctly:
negative values represent passive anti-air capability;
zero means no counterattack;
positive values represent active air attack.
Default equipment file handling
The bundled default equipment.pzeqp was replaced with the newer user-provided version.
The program now maintains two copies:
the release default in the program installation folder;
the active working copy in
Documents\Panzer Corps Toolkit\Equipment\equipment.pzeqp.
The installation-folder copy is always replaced by the version shipped with the current release.
During installation or upgrade, if a Documents working copy already exists:
a timestamped backup is created;
the installer asks whether the user wants to replace the active working copy;
Yes activates the new equipment file;
No preserves the current working file.
The prompt defaults to No for safety.
An installer runtime error caused by incorrect timestamp formatting in the backup routine was fixed.
Localization
A broad localization audit was performed across all eight supported languages:
English;
German;
French;
Russian;
Polish;
Dutch;
Spanish;
Italian.
The audit covered:
menus;
dialogs;
viewers;
editors;
generators;
column headings;
filters;
context menus;
validation messages;
status text;
tooltips;
print output;
saved text;
Help;
installer messages.
New Doctrine, bonus-unit, equipment-validation, and installer strings were localized.
v2.0.0.2:
https://www.mediafire.com/file/dtxtzbwj ... 2.rar/file