Game updated 2026-10-22 (Halloween 2026 event). The DLL mods that needed a rebuild (CDCompat and Anti-Lag) have new builds. A copy installed before the update switches itself off in the new game without telling you, so download it again and replace it in MintCat. Status of each mod →

MY MODS / Game updates

Mod status after game updates

Every time Deep Rock Galactic updates, the mods of mine that ship a native DLL notice the new game build and switch themselves off until I rebuild them; pure pak mods normally keep working. This page lists where each mod stands and is updated as patches ship.

Current game build

2026-10-22 updateHalloween 2026 event

Build 25433570 → 26107973

0mod(s) waiting for a patchStatus updated 2026-10-22

  • CDCompat0.2.0-alpha.4(drg1022)
    Patched 2026-10-22

    Rebuilt for the 2026-10-22 game update.

    Download the new ZIP (CDCompat-0.2.0-alpha.4-drg1022.zip), replace the old one in MintCat and press Install mods again. Only the DLL changed to recognise the new game build; everything else is the same as the 9/23 build. The old ZIP shows “CDCompat runtime is not active” on the new game.

  • Anti-Lag0.1.0-alpha.5-r13.1
    Patched 2026-10-22

    Rebuilt for the 2026-10-22 game update.

    Download the new ZIP (AntiLag-0.1.0-alpha.5-r13.1.zip), replace the old one in MintCat and press Install mods again. Movement works the same as before; from this version on, the game itself tells you to come here for a new build after the next game update.

  • Ally Outlines Plus0.4.0-alpha.5
    Not affected

    Pure pak mod; still works after the 2026-10-22 game update.

  • Shield Link Range0.1.0-alpha.1
    Not affected

    Pure pak mod; still works after the 2026-10-22 game update.

  • Not affected

    Pure pak mod; still works after the 2026-10-22 game update.

  • Not affected

    Pure pak mod; still works after the 2026-10-22 game update.

  • Not affected

    Pure pak mod; still works after the 2026-10-22 game update.

Why this happens

Mods with a native DLL (Anti-Lag, CDCompat, …) hook straight into the game executable, so each build only recognises one exact game executable. When the game updates, the executable changes; the DLL notices at start-up, switches itself off and does nothing (the log says unsupported EXE). No crash, no damage to saves. Once I have matched the addresses to the new build and rebuilt, the new version goes up on the mod page.

Pure pak mods (a single .pak, no DLL or UE4SS) normally keep working. They only need an update when the game changes the exact file they modify, and that will be flagged here when it happens.

You don’t need to remove a mod that is waiting; leave it in MintCat. When the new build is up, swap the file and press Install mods again.

Bug reports or questions: Discord arthur_lin_0906 (feel free to add me), or leave a comment on the My mods page.

This is the first game update recorded here; every later one stays on this page.