Modding


 * See also: Guide, Modding/Useful links.
 * See also - mods: Mod:Age of Calamitous, Mod:Emberlight, Mod:WARRIOR Mutator for Conan Exiles.

' features full modding''' support on PC. This was made available at the start of Early Access. Mod developers are able to download a custom Unreal Engine editor, letting them create a whole host of modifications to the game. Everything from changing aspects of gameplay to adding new monsters and items to the game can be done with the modding tools. A mod management tool which connects to the Steam Workshop allows players to easily load in the mods they want to play with.

Mods for Conan Exiles
The mod DevKit is a work in progress and there are many rough edges still. (This also goes for the documentation!) Some things to be aware of: We will be focusing on fixing these issues and generally improving the modding experience over the coming weeks. Thanks for your patience!
 * You have to restart it when you want to work on a new mod. (This might not get fixed any time soon, since flushing / reloading assets seems problematic.)
 * Renaming mods is not trivial, so choose good unique names.
 * The feedback for users when joining a server that has mods is very bare bones right now. It currently requires people to look for the mods manually, but this will be improved.

Mods - Short Version
A mod in  is a single .pak (archive) file containing modified versions of game assets and optionally new assets.

To create mods, get the DevKit from the Epic Games Launcher, do your changes and build the mod to generate a mod file. You can either distribute the mod through the Steam Workshop by uploading it from the DevKit, or simply share the file with your friends directly.

Installing Mods
The easiest way to install mods is to subscribe to them on the Steam Workshop. Once they are downloaded you can find them in the "Mods" menu from the Main Menu in-game. You can also use mods that you get outside of the Steam Workshop - put the mod .pak file in " " and it will be available in the in-game mods menu.

Note: You have to restart the game before changes to the selected mod list has any effect. The ingame gui doesn't make this very clear right now.

Downloading Mods
Downloading mods may be done either automatically or manually.

Automatic Downloading of Mods
"This is a quality of life fix that we have wanted to add for a while. Much requested by modders, this allows people a smoother gateway into the experiences created by our amazing community."

- Dev Blog

The simple version: Automatic downloading of mods allows you to join a server without having to find and subscribe to every mod first.

The full explanation: When you join a modded server without having subscribed to their mods first, the game will give you a list of which mods you are not subscribed to with an option at the bottom to download and enable all missing mods. Bear in mind doing so will require the game to restart and the game takes a long time to start up if you're using a lot of mods.

Non-Steam mods are shown in the list, but you will have to get their correct version manually.

There are also two checkboxes, one to automatically subscribe to / update mods when needed and one to automatically connect when ready. These may be changed from Settings > Gameplay:

Manual Downloading of Mods
Clientside: To join a server with mods, you must first have the same mods the server is running, with the same load order. When joining a server, you will get a message box telling you which mods you are missing. You cannot connect to the server unless you have those mods installed and activated.

Serverside: To start a server with mods, you put the mod files in " " and add a text file with the file names of those .pak files, one per line, like this:

Instead of creating  manually you can also select the mods you want in your game client, then copy the file from " " to " ". When clients try to connect to the server, the game will first check to make sure the clients have the same mods as the server selected. If they don't they won't be able to connect.

Mod compatibility
Mod compatibility depends on the nature of code changes done in patches. Players and server admins who use mods may experience compatibility issues when trying to play the game immediately after a new patch. These can be anything from not being able to access a chosen server to placeables disappearing and the game crashing on start-up. It could even result in world corruption! To be safe, don't launch your server until you've updated every mod possible and/or tried them in singleplayer, where it's not so much of an issue if the world gets corrupted.

To fix these compatibility issues the developers have to release a new DevKit so the mod creators can update their mods. They try to have a new DevKit ready as quickly as they can after rolling out a patch and they are usually able to release it no later than 24 hours after the patch came out. Having a DevKit ready when a patch is fresh causes less downtime for modded servers and players.

Since the developers cannot always guarantee that existing mods will be compatible with a new version of the game, they are recommending that you disable mods if you encounter an issue right after a patch has gone out. That way you can confirm that an issue is caused by an incompatible mod or if it is a bug that they have to patch.

DevKit
You can get the DevKit (~270 GB) itself from either the
 * Epic Games Store (has to be reverted to the UE version  is on.)
 * Epic Games Launcher (~8 GB), by either
 * Downloading it directly from their site.
 * "Purchasing" it (it's free) with an Epic Games account and installing it from the store.

Once purchased from the website links above, it will be in the game library, which is hidden by default. Go to settings and uncheck hide game library to find it.


 * WARNING: install the DevKit with the shortest possible path to prevent future build failures. In other words, prefer  over.

Finally, run the DevKit under the "Modding" tab. The DevKit is a modified version of the Unreal Engine editor and will let you do (almost) everything the developers can do except C++ code changes.

Support

 * Guide
 * Modding/Useful links

Usage
The first time you launch the DevKit it will open with a default mod selected. You can use this to play around and see how things work, but before you start working on something you want to use or distribute to other people, you'll need to create a new mod with a unique name. See Create new mod below for more details.

Note: The folders in "/Games/ConanSandbox/Mods/" are used by the DevKit to edit the mod, so deleting a folder here means you can no longer edit that mod. These are the folders you want to have backups of!

Editing existing game assets: Modify assets normally. Note that you can't rename, move, or delete default game assets.

To create new assets: New assets can only be added in "Content/Mods/ ."

Use "Play in current viewport" to test with the mod content loaded without having to wait for the game itself to load.

Build errors
When building a mod, Unreal will "cook" each asset. This process will fail if the assets contains certain errors (like a Blueprint compiler error). If the build fails, check the output log for the lines saying something like this (should be near the bottom):

In this example there are 7 errors that caused the build to fail. The log will say what the errors were in more detail further up. Fix these and try to build again!

Sharing mods
When you have a mod you want to share with others, you must first build the mod. Then you can either upload the mod to the Steam Workshop or share the generated .pak file directly with your friends.

Conan DevKit menu

 * Select active mod: Switch which mod you are currently editing. This will restart the editor!
 * Create new mod: Use this to .. create a new mod.


 * The name you enter here will be used to create a folder: /Games/ConanSandbox/Content/Mods/.
 * Any assets you add will end up here, so make sure you choose a unique name to avoid conflicts with other mods. (Especially until we figure out a safe way to rename mods >.<) (Suggestion by Carnaxus: "Save As" funciton?)
 * You can change the display name of the mod to something more user friendly before building/uploading to Steam, aka if you named your work in progress "bossweaken," you can rename it to show up as "Weaker Bosses" on the Workshop.

DevKit window

 * Name: Name of mod as it appears in the in-game mod menu and in the Steam Workshop.
 * The name can't be empty and must be less than 128 characters long.


 * Author: Name shown as author in the in-game mod menu.
 * Author URL: Shown in the in-game mod menu.
 * Version major, minor, build: Show in the in-game mod menu. Please don't go crazy, we don't need to know that your mod is currently in version 0.2.5.rv2.beta.test3.
 * Description: Shown in the in-game mod menu and on the Steam Workshop. Max length is 8000 characters.


 * Change notes: Shown in Change Notes on the Steam Workshop page.
 * Preview image: A .png image that must be less than 1MB. Used on the Steam Workshop page. Not necessarily required, but your mod will probably be ignored without at least one image.
 * Build mod: This will cook the mod and package it so it can be used/uploaded to Steam. Building can take a while depending on how complex your mod is (possibly even an hour or longer, welcome to the world of programming)


 * The generated .pak file is the only file needed to load the mod. You can share this with and/or without Steam.
 * Open in File Explorer (or whatever your equivalent is):
 * Active mod folder: Opens the local folder of the active mod that the DevKit uses when editing the mod.
 * Built mod folder: Opens the folder where the .pak file generated from a build is located.


 * Cook by the book: By default, the DevKit will find and cook each asset modified in the currently active mod individually. If "Cook by the book" is checked, it will do a full dependency based cook (but force include all new assets added by the mod) and then pack up cooked versions of the mod's assets. The normal cook will almost always be much faster.


 * Steam file ID: The Steam Workshop item ID used to identify the mod in the Workshop.


 * This is automatically managed when uploading to Steam.
 * Open workshop page: Opens a browser window with the Workshop page of the current mod. It might take a few seconds before the page is updated after uploading. It also might open in Steam instead.


 * Steam visibility: Visibility of the mod in the Steam Workshop.


 * Public: Visible to everyone.
 * Friends-only: Visible to you, your friends and Steam admins.
 * Hidden: Visible to you, Steam admins and users marked as creator.
 * Unlisted: Visible to you but does not show up in search results. Requires you to send a direct link to anyone you want to be able to use the mod.


 * Upload to Steam button: Uploads the current mod to Steam. You must first have a build of the mod.
 * Update mod info to Steam button: This will only update the info on the Steam page for your mod with the current state of all the textboxes and preview image. Allows you to update the preview image on Steam and Steam visibility without uploading the whole mod.

Steam
You can upload a mod to Steam through the DevKit so others can subscribe to the mod. Note that changes made to the mod on the Steam Workshop website will NOT be reflected in the DevKit. This means that changes to name, description, visibility or preview image will be overridden the next time you upload your mod from the DevKit, so make sure you update these field only through the DevKit, or make sure you mirror such changes manually. Changes to the other fields will not be affected.



Creating an example mod

 * 1) Open the DevKit and go to the DevKit drop down menu. Select "Create a new mod..." and you will be asked to enter a name for the mod: HowToCreateNewMod.png
 * 2) Enter a name and click "Create." Once the editor has restarted you can begin creating the mod.
 * 3) For this tutorial, we'll open "BP_Axe" In the content folder Items/Weapons/Axe: HowToCreateNewMod3.png
 * 4) Select the "StaticWeaponMesh" in the Components window: HowToCreateNewMod4.png
 * 5) Change the values of the Scale property of the Transform in the Details window: HowToCreateNewMod5.png
 * 6) Hit "Compile" and "Save" for that Blueprint. Repeat for whatever other items you feel like changing (like "Items/Weapons/Torch," "Items/Weapons/RepairHammer," "tems/Weapons/Pickaxe," etc.).
 * 7) To test your mod you can use "Play" from the main window:HowToCreateNewMod6.png
 * 8) Once you are done with your mod, go to the DevKit panel. See the "DevKit window" section for details on the different fields and buttons: HowToCreateNewMod7.png
 * 9) Enter the details and select a preview image: HowToCreateNewMod8.png
 * 10) Click the "Build mod" button to build the mod. This process can take a while depending on how many assets are changed in the mod.
 * 11) Once the build is done, you can either click "Upload mod to Steam" or go to the "Built mod folder" and share the " .pak" file directly.

Under the hood
The DevKit is built from Funcom's modified version of Unreal Engine 4.15.3. The main changes specific to the DevKit are:
 * The Conan devkit redirects reads/writes of assets/maps to the mod's folder on disk:


 * Reads/writes in " /Mods/ /*" are remapped to " /Mods/ /Local/*"
 * Reads/writes anywhere else in " /Mods/*" are blocked.
 * Reads/writes anywhere else under /Content are redirected to " /Mods/ /Content," with reads falling back to the original path if nothing is found in the mod.


 * It tries to prevent adding/moving/deleting/renaming anything outside "/Content/Mods/ /"
 * It prevents opening or exporting assets Funcom bought from the marketplace (for licensing reasons).
 * It adds the DevKit toolbar button and menu.

Media

 * Stream: UnrealEngine, Andy Benditt - November 23, 2016]
 * Announcement: "Conan Exiles Mod Editor - Feb 16th - Live From Epic HQ!" Alexander Paschall, Unreal Engine Forums - February 15, 2017