Installer Steam
log på
|
sprog
简体中文 (forenklet kinesisk)
繁體中文 (traditionelt kinesisk)
日本語 (japansk)
한국어 (koreansk)
ไทย (thai)
Български (bulgarsk)
Čeština (tjekkisk)
Deutsch (tysk)
English (engelsk)
Español – España (spansk – Spanien)
Español – Latinoamérica (spansk – Latinamerika)
Ελληνικά (græsk)
Français (fransk)
Italiano (italiensk)
Bahasa indonesia (indonesisk)
Magyar (ungarsk)
Nederlands (hollandsk)
Norsk
Polski (polsk)
Português (portugisisk – Portugal)
Português – Brasil (portugisisk – Brasilien)
Română (rumænsk)
Русский (russisk)
Suomi (finsk)
Svenska (svensk)
Türkçe (tyrkisk)
Tiếng Việt (Vietnamesisk)
Українська (ukrainsk)
Rapporter et oversættelsesproblem








Mod sorting rules are necessary to optimize the loading and operation of mods to avoid conflicts and ensure correct interaction between them. A clear sorting structure helps users easily manage mods and ensure that they are loaded in the correct order.
An example of the contents of the sorting_rules.txt file:
Just add the desired fields loadAfter, loadBefore, loadFirst, loadLast or incompatibleMods and describe the corresponding lists of mods.
However, there are a few nuances:
These limitations are due to the fact that the game developers added support for versioning mods by game version number, but the getModFileReader method I use to read the mod.info file only reads the mod.info file from the common folder.
An example of the contents of the mod.info file: