Which mods work in DCS Liberation and how do I install them?

DCS Liberation works only with community mods that its installed release explicitly defines and that the selected campaign or faction expects. Common examples include supported builds of the A-4E-C and UH-60L, but the list changes between releases. Install each mod in DCS World’s Saved Games folder, not inside Liberation.

What counts as a DCS Liberation-compatible mod?

A compatible mod must work at three separate levels: DCS World must load it, Liberation must recognise its unit identifiers, and the chosen campaign or faction must permit the unit.

This is why there is no permanent list covering every Liberation version. Examples commonly supported by particular releases include the A-4E-C and UH-60L, along with selected community aircraft and ground-asset packs. A similarly named mod, fork or newer build is not automatically interchangeable if its internal identifiers have changed.

Use only mods named by the campaign requirements or the documentation supplied with your Liberation release. Installing an unsupported aircraft under Mods\aircraft makes it available to DCS, but it does not teach Liberation how to place, purchase or assign it. That requires a Liberation unit definition and suitable campaign or faction data.

If the campaign generator itself is not configured yet, our Liberation setup and campaign workflow covers its DCS and Saved Games paths separately.

Which types of DCS mods can Liberation use?

Liberation can use unit-adding mods for which explicit support exists; cosmetic and utility mods follow different rules.

• Community aircraft and helicopters: Supported examples may include the A-4E-C or UH-60L. The correct build must be installed before flying or hosting a mission that references it.
• Ground, naval and SAM asset packs: These work only when Liberation defines their units and the campaign calls for that exact pack.
• Official DCS modules: These are not community mods. A player needs the appropriate licence to occupy a flyable slot, while terrain and paid asset requirements remain separate campaign dependencies.
• Liveries: These do not add a new unit type. They can normally be installed independently, although a Liberation-generated mission may fall back to a default skin if a named livery is missing.
• Graphics, cockpit and sound modifications: These generally have no bearing on Liberation’s unit database, but they may still be affected by DCS updates or multiplayer integrity checks.
• Mission scripts and plug-ins: Enable these only when the installed Liberation release provides the corresponding integration. Putting an arbitrary script in a mod folder does not add it to generated missions.

How do I install a mod for DCS Liberation?

Install the mod for DCS World first, verify it there, and only then generate a Liberation mission that uses it.

1. Confirm the exact dependency. Check the campaign description and the information supplied with your Liberation release. Match the mod name and required build rather than assuming any fork will work.
2. Find the active Saved Games profile. Most installations use %USERPROFILE%\Saved Games\DCS\. Older or retained profiles may use %USERPROFILE%\Saved Games\DCS.openbeta\. Use the profile containing the Config and Missions folders written by the DCS installation you launch.
3. Extract the mod to the correct category. Aircraft and helicopters normally belong under Saved Games\DCS\Mods\aircraft\; ground, naval and other asset packs normally use Saved Games\DCS\Mods\tech\.
4. Check the folder depth. The mod’s main folder should contain files such as entry.lua. A path resembling Mods\aircraft\mod-name\mod-name\entry.lua is double-nested and usually will not load.
5. Test it in DCS World. Start DCS and look for the unit in the Mission Editor. If it is absent, fix the DCS installation before troubleshooting Liberation; the generator cannot use a mod that DCS itself has not loaded.
6. Open Liberation and select the matching campaign or faction. Make sure Liberation points to the same Saved Games profile. Enable a mod-specific option or integration only if that option exists in your installed release.
7. Generate a fresh mission. A previously exported .miz retains its original unit types. Regenerate it after adding, removing or changing a required mod.

Do not install community mods inside the Liberation directory or overwrite DCS World’s core installation unless a mod’s verified instructions explicitly demand it. Saved Games installation is easier to remove and is less likely to be overwritten by a simulator update. Our full DCS Saved Games mod-installation guide covers the general folder rules, while the step-by-step A-4E-C folder example shows the aircraft layout in practice.

Why is a Liberation mod missing or causing mission errors?

Most failures come from the wrong folder, the wrong mod build or a campaign that does not include the installed unit.

• The unit is absent from DCS: Check for a double-nested archive, missing dependency or installation in the wrong Saved Games profile.
• The unit appears in DCS but not Liberation: The Liberation release may not support it, or the selected faction, campaign date and roster may exclude it.
• The Mission Editor hides the unit: Check whether historical filtering is active, because the mission date can hide otherwise installed units.
• An update broke the campaign: The DCS mod may have changed its unit identifier or file structure while Liberation still expects the previous implementation. Use our method for checking a DCS mod after an update before changing the campaign.
• Only an old generated mission fails: Export a new mission after correcting the dependency. Existing mission files are not rewritten automatically.
• DCS reports an unknown or missing unit: Compare the host’s mod folders and versions with the campaign requirements; do not substitute a similarly named package.

Do all multiplayer players need Liberation’s mods?

The server and every participating player should use the same versions of all community mods referenced by the generated mission.

This is essential for flyable community aircraft and the safest rule for AI asset packs as well. A missing package can remove a slot, produce an unknown-unit error, stop the mission loading correctly or leave clients with mismatched assets. Distribute the campaign’s dependency list before generating the multiplayer mission, and avoid changing mod builds midway through an active turn.