Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
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: