Game misinforms about turns left for chopping

[dalamb]

I posted this earlier as a question, and confirmed it's a bug other people see in both pre-Warlords and Warlords versions of Civ:

In my current game, I've seen two instances where, at the end of one turn, hovering over a chopping worker says there are 2 turns before completion, when in fact the chop completes the next turn. I'm quite inexperienced, and so each game am trying to learn one or two new techniques. For this game, one such was chopping while building a non-settler, so the city will keep growing, then switching to settler when there is one turn of chopping left, so this bug (if that's what it is) messed me up twice.

I've attached a saved game at the point where it says 2 turns left. This is for GOTM-13, so nobody should look at the save if they haven't got 'way ahead of 2050 BC. I've been making saves at several points to retry the game after finishing the no-reload version, and made one just before starting this production-switching chop, which is how I was able to recreate the problem.

This is emperor level, epic, HOF-1.61.009 with most options turned on.

The save file is an attachment to the earlier post.

 

[crunch]

I don't have civ4 at this comp, but I suspect that this is the intended behavior and it works like this with all worker actions. Unless I misunderstood something.

If an improvement/chop is due in 2 turns, it will actually be ready at the end of the next turn. Also, if you activate the worker at the beginning of the next turn, and tell him to do the same thing, it is done immediately (and worker moves are consumed). Thus, the worker will be ready for further tasks in 2 turns.

 

[HardCoder]

In my current game, I've seen two instances where, at the end of one turn, hovering over a chopping worker says there are 2 turns before completion, when in fact the chop completes the next turn.

AFAIK it always does that with chopping. I don't pay attention to what it does with other improvements because it's just pre-chopping where it really matters. I don't think it's a correct or good behavior. The countdown goes 4..3..2..0.

 

[ggganz]

Yup, always happens. How again did you get it "confirmed as a bug"?