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
Instead it uses the very functions of about.xml you discussed to place mods into groups by what part of rimworld they are modifying, which helps prevent overwriting.
Within each group, there is absolutely no control over order, and the number of mods automatically sorted by LOMS are actually quite small (though they are some of the more popular).
Yes, the LOMS series is designed to work as a set.
Due to the way that the vanilla <load after> tags work, the auto-sorting for every LOMS MOD is actually on the mod AFTER the mod named for any particular group.
Ideally, you should download them all, activate them and place them at the top of you mod order, do an Auto-Sort, (which will spread them out to the correct locations among your mods, and change your mods order to fit them), and then do manual sorting from there for the Mods that did not get auto-sorted.