[BUG] Colonizers ability - minor bug if you select a project first

from GalCiv3 Forums

More of an annoyance bug than a game breaker, but -> With a race that has the Colonizers ability (first building on a new colony is free)...

If you select a project like Economic stimulus, the next turn you see that this project is displayed as Rushed in the manufacturing queue. If you select a new building, no production gets added to the new building, because each turn it thinks you have rush bought economic stimulus, thus no production gets actually added anywhere. (You can still select a different building after you cancel the rush of the project first, still getting your new free building so no big deal.)

Steps to recreate this:

Colonize a planet, select Economic Stimulus as your first building/project.

Go to next turn.

Look at colony screen... Economic Stimulus listed as rushed.

8,913 views 1 replies
Reply #1 from GalCiv3 Forums Top


More of an annoyance bug than a game breaker, but -> With a race that has the Colonizers ability (first building on a new colony is free)...

If you select a project like Economic stimulus, the next turn you see that this project is displayed as Rushed in the manufacturing queue. If you select a new building, no production gets added to the new building, because each turn it thinks you have rush bought economic stimulus, thus no production gets actually added anywhere. (You can still select a different building after you cancel the rush of the project first, still getting your new free building so no big deal.)

Steps to recreate this:

Colonize a planet, select Economic Stimulus as your first building/project.

Go to next turn.

Look at colony screen... Economic Stimulus listed as rushed.
End of quote


I don't know if that's a bug or a mechanic for something else. I've bought/rushed other buildings besides the Eco Stim on the turn I landed on the planet and still seen exactly what you describe and also did not choose the colonizer ability. I figured maybe there was a additional turn needed somewhere in the process I wasn't seeing or didn't know about or notice. Maybe the rush command didn't go through on the same turn as landing? Hmm, maybe that is a bug after all. Just not sure if it's exclusive to the buildings you mention, or maybe it is and you found a new variant? Either way I've noticed the same behavior on a few world's first turns and it was there in 1.01 and 1.02.