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
The exceptions are where Mod-A has a dependancy or a reference to Mod-B, in which case Mod-A loads after Mod-B.
The only reliable way to circumvent the mod loading order issue is to use a trigger in your SQL:
whoward69's Circumventing mod load order issues with database triggers tutorial [forums.civfanatics.com]
I suppose I could experiment with trying to use the OnCreateModUserData action rather than OnModActivated, but I don't know if that would behave the way I want.