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
That's it.
Edit BEsettings.lua to point at the settings file you want to use.
If you want to customize things beyond the three options (CBP, vanilla, whitewalkers) then pick BEsetPersonalized.lua and read the comments to understand what all the settings do.
The reason I can't give you ONE option is because the option applies to everyone who downloads the mod. One size does not fit all. So I set a default (Vanilla) that covers most cases, and created a few files to cover edge cases (CBP, White Walkers).
However, I'm trying to use MPMPM Multiplayer Mod Workaround to compile a pack so I can use mods without going into the mod section and perhaps even multiplayer. Therefore I'm using the BE SETTING notepad file with the include string.
I'm having issues with the fact that no matter what I include there is no change. I'll include BEsetWhiteWalkers and even delete the other setting lua files and when I load the mod there are no white walkers.
Once when I just used custom settings, the barb civ worked just fine and got really strong but the barbs could walk on water even though I did not give them the hover promotion. How could I fix this?
I'm wondering, could I try v3 out in case v4 removed the functionality of the notepad settings? Could you offer any help? I would love to enjoy this mod to its full potential. Thanks!
My suggestion would be to start FireTuner and look at the lua log. There should be heaps of debugging info printed there.