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
Secondly, and I know this may be a hard one, but here goes. To the Dev. Would there be any possibility to further improve the persistence of the mission without affecting performance too much? My main suggestion, if it wouldn't have a major impact on performance, would be to include unit AI persistence, so that useful recon missions can be done, and once the player comes back to the location, the same units (particularly tanks and other vehicles, as well as fortifications) remain as they were.
Thirdly. Including additional stuff on the map, especially if you plan on expanding the mission to other bigger maps. This may include persistent/random checkpoints, roadblocks, bunkers and so on.
1. The cache exclusion system is useful for putting out a specific unit (Especially recruited units) from the custom caching system...
2. This is a good question, I will keep this in mind... The current caching system is based on counters (number of cars, number of enemies, civ, friendlies...) per compounds which is quitely performant. I don't know how much it would cost to add a persistence of already triggered compounds. I'd tried to give the feeling enemies reorganize their defenses when you're away...
3. Adding persistent resistance/enemy checkpoints is a nice idea of feature. I will keep it in mind.