Installer Steam
log på
|
sprog
简体中文 (forenklet kinesisk)
繁體中文 (traditionelt kinesisk)
日本語 (japansk)
한국어 (koreansk)
ไทย (thai)
Български (bulgarsk)
Čeština (tjekkisk)
Deutsch (tysk)
English (engelsk)
Español – España (spansk – Spanien)
Español – Latinoamérica (spansk – Latinamerika)
Ελληνικά (græsk)
Français (fransk)
Italiano (italiensk)
Bahasa indonesia (indonesisk)
Magyar (ungarsk)
Nederlands (hollandsk)
Norsk
Polski (polsk)
Português (portugisisk – Portugal)
Português – Brasil (portugisisk – Brasilien)
Română (rumænsk)
Русский (russisk)
Suomi (finsk)
Svenska (svensk)
Türkçe (tyrkisk)
Tiếng Việt (Vietnamesisk)
Українська (ukrainsk)
Rapporter et oversættelsesproblem
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.