Crimson Desert - Mod Organizer 2 Plugin

Adds full basic game support for Crimson Desert in Mod Organizer 2, including archive building for loose file mods, JSON patches, archive bundle inputs, DDS texture mod support, and .asi loader support.

What This Plugin Adds

This plugin adds custom MO2 support for Crimson Desert and improves both mod installation and archive generation for the game’s PAZ / PAMT format.

• []Adds basic game support for Crimson Desert in MO2.[/]

  []Automatically detects the Steam install of the game.[/]

  []Adds support for standard Crimson Desert mod layouts such as loose game files, JSON patches, prebuilt archives, and .asi mods.[/]

  []Supports Ultimate ASI Loader's version.dll.[/]

  []Cleans up unnecessary install files such as manifest.json, mod.json, modinfo.json, preview images, readmes, and other junk files when possible.[/]

  []Lets you build generated PAZ/PAMT archive bundles directly from installed mods.[/]

  []Can generate multiple archives if one output would become too large.[/]

  []Defaults generated XML files to encrypted output and lets you manage plain-output XML exceptions directly from the Crimson Builder tree.[/]

  How It Works

  • []Install your Crimson Desert mods normally through MO2.[/]

    []Mods that contain loose files, JSON patches, or archives are normalized into crimson_builder.[/]

    []Open the Crimson Builder tab in MO2.[/]

    []Use Refresh to scan mods.[/]

    []Enable or disable the JSON patch entries you want.[/]

    []Click Build Archives.[/]

    []The plugin generates new numbered archive in overwrite and rebuilds meta/0.papgt.[/]

    Installation

    Drop the plugins folder into your Mod Organizer 2 root directory, where ModOrganizer.exe is located.

    If you are updating from an older version, replace the previous plugin files with the new ones.

    Important Setup

    • []Add crimson_builder to MO2's skipped directories if you want Builder source files excluded from the VFS when the game starts.

      These files are only source files for Crimson Builder and does not need to be loaded.

      Example: a file like crimson_builder/files/ui/splashscreen/splashscreen_0.png is just a Builder input, not a live game file.[/]

      Notes

      • []Generated archives are written to MO2’s overwrite folder.[/]

        []XML exceptions are user-managed from the Crimson Builder tree and saved to plugins\basic_games\games\crimsondesert\xml_plain_whitelist.txt.[/]

        []When a mod adds a brand-new DDS path that does not exist in the base archives, the Builder can infer matching texture metadata from a similar existing DDS entry.[/]

        []The Builder UI separates JSON Patches, Loose Files, Extracted Archive Files, and Archive Bundles, and also supports filtering, saved column layout, and preserved JSON toggle state across refreshes and MO2 restarts.[/]

        []The plugin automatically deploy active .asi mods, matching .ini files, and Ultimate ASI Loader’s version.dll into the real bin64 folder before launch and restore them after exit.[/]

        Credits

        []Mod Organizer 2 team[/]

        []IzeDev for Crimson Browser[/]

        []MrIkso for the CrimsonDesertTools[/]

        []Lazorr for the Crimson Desert Unpacker[/]

        []PhorgeForge for the JSON Mod Manager[/]

        [*]kindiboy for the python version of CSS/HTML patch tools &