Does computer stack units?

[Bob_]

Dont have one. Saw no need to save.

 

[Ranos]

The ejected unit should be dead on next turn....

Depnding on where the unit gets ejected two and where your units are, it could survive until the next turn.

Why don't you post a save game?

A save game is unnecessary. This is easily reproduceable. Use worldbuilder or play a game as the Chinese. Put a Cho Ko Nu in a city, then while the city is under seige, build another Cho Ko Nu in the city. Attack with both Cho Ko Nus and end turn.

 

[muhtesem insan]

After shooting, one of the units is automtically "ejected" from the city after clicking "next turn", that's normal.

that explains it. thanks. But i still believe this should be treated as a bug or at least a design flaw.

 

[FlowKey]

that explains it. thanks. But i still believe this should be treated as a bug or at least a design flaw.

Why? You could do the same thing to them if you wanted to ...
And 'design flaw' sounds a bit too harsh - it's an inevitable consequence of the no-stacking game concept ... which some may call a design flaw, but that's a different discussion altogether ...

 

[CTH]

The AI has (and perhaps still are) cheating with that they can purchase a unit and move it the same turn (or possible that they can one-turn build modern armors in all cities, could be either way).

 

[puyo]

The AI has (and perhaps still are) cheating with that they can purchase a unit and move it the same turn (or possible that they can one-turn build modern armors in all cities, could be either way).

You can't purchase a unit in a city that has already a unit in it, I think that's the same for AI no?

 

[KaiserKevin]

What i see happen is on a city if there is a ranged unit inside and one built, the comp gets to fire both from the city, and then the offending 'stacked' unit gets shoved out of the city after it gets to fire a ranged shot at end of turn :/