Nainstalovat Steam
přihlásit se
|
jazyk
简体中文 (Zjednodušená čínština)
繁體中文 (Tradiční čínština)
日本語 (Japonština)
한국어 (Korejština)
ไทย (Thajština)
български (Bulharština)
Dansk (Dánština)
Deutsch (Němčina)
English (Angličtina)
Español-España (Evropská španělština)
Español-Latinoamérica (Latin. španělština)
Ελληνικά (Řečtina)
Français (Francouzština)
Italiano (Italština)
Bahasa Indonesia (Indonéština)
Magyar (Maďarština)
Nederlands (Nizozemština)
Norsk (Norština)
Polski (Polština)
Português (Evropská portugalština)
Português-Brasil (Brazilská portugalština)
Română (Rumunština)
Русский (Ruština)
Suomi (Finština)
Svenska (Švédština)
Türkçe (Turečtina)
Tiếng Việt (Vietnamština)
Українська (Ukrajinština)
Nahlásit problém s překladem
I avoid adding gameplay altering mods mid-campaign, as their changes are more extensive and so, IMO, more likely to mess up. So I'd install something which added a single enemy (Celatid), but not something which changed enemy mechanics, like the Hive. I'd add cosmetic armour mods, but not mods which affect how armours are built in Engineering or the Proving Grounds. I'd add voice packs for soldiers but not new soldier classes; new map plots and parcels but not new mission types. Etc. etc. etc.
I add mods mid-campaign, just not this one. Similarly I wouldn't add e.g. class mods.
Is it recommended for people not to add mods mid-campaign? If yes, how can one know whether certain mods will work or not? I mean, I don't want to wait till June (in game time) to find out that my mods don't work :( You can't test certain mods when you start a new game, because the stuff they modify won't open up until mid-game.