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
For example, using // in XPath can be slow since it checks all descendants instead of just direct children. Similarly, something like "contains(defName, "Turret")" might become time-consuming if you overuse them. (I think you would need A LOT of them to make the loading that slow, though.)
idk, I was going to ask if you’d tried Loading Progress, but then I saw your comment on that mod’s page. Using a lot of heavy XPath (like wildcards) could cause that, but I have no idea what’s going on in your modlist.
Yeah one of the new patches had wrong mod condition. It was fixed 10 minutes after the update, but I guess your Steam updated the mod before that. Sorry for the inconvenience!