Assassin's Creed Unity modding: ReShade, config tweaks, and a closed engine
ActionAdventureStealth0 Modsopenmods.json · supportedGameId: "assassins-creed-unity" or 134
Why Unity's scene is about polish, not new content
Read more
Articles & guides
Official channels
Where else to find Assassin's Creed Unity
About
More about Assassin's Creed Unity
Assassin's Creed Unity is Ubisoft's 2014 recreation of revolutionary Paris, built on the AnvilNext 2.0 engine, and its modding scene looks nothing like an Unreal or Bethesda game. There is no mod loader, no pak system, and no official toolkit. AnvilNext is a closed, proprietary engine, so the community never got the hooks needed for deep content mods. What grew instead is a focused scene around making an already striking game look modern.
How the scene is shaped
Unity's strength was always its visuals: dense crowds, hand-detailed architecture, and a Paris that still impresses years later. That is exactly what the community doubled down on. Browse the game's Nexus Mods page and the overwhelming majority of entries are ReShade presets, post-processing layers that adjust colour, sharpness, contrast, and atmosphere on top of the running game. Alongside them sit configuration tweaks that push graphics settings beyond the in-game menu.
Deep gameplay mods are rare to nonexistent, and that is not for lack of interest. The engine simply does not expose the systems a content mod would need, so new missions, characters, or mechanics are off the table. Knowing that up front saves a lot of fruitless searching.
There is a historical reason the scene tilted this way. Unity launched in 2014 to heavy criticism over bugs and performance, and even after Ubisoft's patches restored its reputation, the modding instinct that survived was about polish: squeezing the best possible image out of a game that was always visually ambitious. A handful of mods do go further, swapping individual textures or adjusting the HUD, but Unity packs its assets into compressed .forge archives that are awkward to open and repack, which is why post-processing presets remain the path of least resistance.
The toolchain primer
The core tool is ReShade, a general-purpose post-processing injector that is not specific to Unity. You install ReShade into the folder that holds ACU.exe, then drop a preset's .ini file alongside it. In game, the preset's effects layer over the original image. Because ReShade sits on top of the game rather than replacing assets, presets are easy to swap, stack, and remove.
The second lever is the ACU.ini configuration file, where values for draw distance and texture quality can be raised past what the settings menu allows, on hardware that can take it. Both approaches are non-destructive and reversible, which suits a game whose modding is about polish rather than overhaul.
What you'll find on OpenMods
OpenMods indexes mods from public repositories, and Unity's scene is small and concentrated on Nexus Mods, so coverage here is limited by design. This is an honest reflection of the game: there is not a large body of open-source Unity tooling the way there is for Unreal titles. For ReShade presets and config guides, Nexus Mods and the community wiki are the primary destinations.
Practical notes
- ReShade is reversible. Delete the injected files from the ACU.exe folder to return to vanilla.
- Performance varies by preset. Heavier presets can cost a large chunk of frame rate, so match the preset to your GPU.
- ACU.ini edits are not officially supported. Keep a backup of the original file before changing values.
- Expect graphics, not gameplay. Unity's scene is about how the game looks, not new missions or systems.
For a hands-on setup, see the Assassin's Creed Unity ReShade guide.