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
I myself am not a fan of the "Save As" function because of the aforementioned score loophole but I do admit there are a couple of examples where I understand why it would be used:
1. To avoid redoing the battle preparation phase. The battle prep phase is incredibly important but somewhat tedious, especially in the much larger scenarios on the Eastern Front. Making a mistake that costs you the scenario/gold medal late on and having to redo obnoxious battle prep phases repeatedly, to the point you can end up memorising exactly what reinforcements you want to buy or exact placements of supply hubs, can be very annoying.
2. Trying different history tracks without starting a new campaign. Especially prevalent in the 'Stalingrad' campaign whose first four missions are both difficult and lengthy and the 'Victory in the West' campaign for its sheer length.
Unity of Command II is very different from other strategy games to the point where I would consider it more of a "tactics" game than strategy. Thus in my opinion, unless you're a perfectionist (which the devs recommend not being), the ideal way to play is to simply have at it and damn the saves, restarting scenarios only if you've taken losses or completely failed.