Dwekat’s Mod Manager
One framework for managing Age of History 3 mods without making every code mod fight over the same game.jar.
Dwekat’s Mod Manager adds a dedicated Mods screen, loads compatible code mods from local and Steam Workshop folders, detects class conflicts, supports legacy jar mods, and gives modders a cleaner format for distributing code changes.
- Central mod screen – View local and subscribed mods from the main menu.
- Code mod loading – Load compatible code mods as separate packages instead of installing a different root game.jar for each one.
- Conflict detection – Detect when two active code mods replace the same game class.
- Settings integration – Compatible mods can expose a settings icon directly inside the Mods screen.
- Enable and disable controls – Manage installed mods using the game’s existing mod state and restart workflow.
- Legacy support – Best-effort support for older mods distributed as a complete game.jar.
- Data mod awareness – Display ordinary data-only mods alongside code mods.
The download includes MODDERS_GUIDE.md, covering:
- The dwekat/mod.json manifest format.
- Class patches and optional runtime jars.
- Dependencies and conflict declarations.
- Settings-screen registration.
- Workshop packaging rules.
- Legacy jar compatibility behavior.
Manager-compatible mods can ship only their own changed classes and helper code. The manager remains the only package responsible for installing the root framework jar.
Steam Workshop downloads files but Age of History 3 does not automatically execute Java code from Workshop folders. The manager therefore requires one bootstrap installation before its in-game Mods screen can exist.
- Subscribe to Dwekat’s Mod Manager and any dependent mods you want.
- Close Age of History 3 after Steam finishes downloading.
- Open steamapps/workshop/content/2772750.
- Find the manager folder, or search inside 2772750 for Install_Dwekat_Mod_Manager.bat.
- Run Install_Dwekat_Mod_Manager.bat once.
- Start the game normally. The main menu should now contain Mods.
If a game update or Steam file verification removes the Mods button, run the manager installer again.
Code mods can still conflict when they modify the same class. The manager detects and reports these overlaps instead of silently allowing one mod to overwrite another.
Legacy jar support is best-effort because older jars were not designed for composition.
Do not use old -javaagent launch options from development builds.
Use Steam -> Age of History 3 -> Properties -> Installed Files -> Verify integrity of game files.