68
edits
Changes
Jump to navigation
Jump to search
m
→Using the manifest
*normal directories - where each directory represents separate mod.
We recommend using normal directories for development of the mod and using zip archives for mod release, to make mod size smaller and more handy for end-user (on file vs. directory full of files). Inside the package you can define manifest file containing meta data about the mod. Meta data are used by mod manager to display your mod to the user. You can specify description, icon image and much more.
Since ETS2 & ATS version 1.48 you can use mods that contain subdirectories or files which are mounted only if DLC with the same name is owned. If mod root contains directory "base", zip archive "base.zip", directories or zip archives prefixed with "dlc_", game mounts only parts of the mod that correspond to owned DLCs. "base" part is mounted always (if it’s present). Mod manifest and other metadata are still contained in the mod root.
=Using the manifest=
<li>Type: string</li>
<li>
Name of file inside the root of the mod package directory which contains the description text. Description file has to be a simple text file with .txt extension saved in UTF-8 encoding. Content of the description file is shown in mod details window and should include information about usage of your mod, additional credits of included mods etc. For possible text formatting see section [[#Description_of_your_mod|Description of your mod]]
{{Tip|Since ETS 2 1.23 you can specify localized description files for more check: [[#Localized_description|Localized description]].}}
<li>Type: array of strings</li>
<li>
List of compatible game versions. If the list is present and the game version does not match any version from that list, the user will be unable to use the mod and he they will have to wait for the author to update it. Shall be used only for mods that are likely to get broken, like a map modsmod.
<br><b>Note:</b> If you want your mod to be compatible with all versions simply skip this parameter. Note also that formatting of the Steam version with "s" suffix (for example: 1.18.1s) does not exist in this versioning so please do not use it.
<br>Each item from the list supports wildcards formatting shown below:
</tr>
</table>You can also specify support for only one revision of the game which is not recommended as we do not change game a lot between minor patches.<br>For example:
<pre>compatible_versions[]: "1.19.1"</pre>This usage is not a good idea as your mod will work only with the 1.19.1 version.<br>If we will release some hotfix, your mod will simply be incompatible with it.<br>You can also use more than one compatible version definitionsdefinition, like this:
<pre>compatible_versions[]: "1.19.*"
compatible_versions[]: "1.20.*"</pre>This way you support both 1.19 and 1.20 patches.<br><b>REMEMBER! If you specify a very restricted set of versions, users of your mod may wait for you, to release a hot fix for the mod evenversion number and , even if your mod is 100% compatible with the latest release.</b>
</li>
<li>
