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
a:Yes.
1. Attack gates
2. Liberate Captives
3. Attack Enemies
4. Protect Allies
5. Look around for enemies
6. Loot food
So normally, after getting through the gates they'd immediately try to free your prisoners. In some ways this makes sense, since captives would be potential allies for the fight. Though I could see issues arising form prioritizing that over fighting, similar to your issues with food. Then they'd kill all hostiles, look for more, then steal the food after it was safe.
So yeah, no chance this is intended behavior.
I'd venture this could be solved by staggering the loot food process by displacing it from the source assault package, directing that to lead to the looting of the food, then finally the retreat AI once satisfied. If the events are separate and conditional on the assault succeeding and completing, they shouldn't even attempt it with it locked in a separate but potentially upcoming package.