Can't stop making rangers!

I've noticed an odd feature, that has now occurred in more than one game. On high production planets, in the late game, I'll be creating self-designed ships that are very powerful: perfect defenses, maximum weapons, great range, and lots of speed. I only need one or two fleets of these to hold my own in any battles, so the time usually comes when I want to delete them from the production queue.

But when I do so from the "Make Ship" dialog box, the planet won't reset to manufacturing "nothing". Instead, it'll switch to manufacturing rangers. This happens whether I go directly to the Make Ship dialog, or go through the planet management screen.

After a few games where I had way too many rangers for my own good, I finally figured out that I could use the governor screen to tell all planets producing rangers to produce nothing. That, at least, solved the problem.

But it's still odd behavior. Any explanation? Or is it just a bug? I would add that it only seems to happen on high production planets, and only later in the game, although I haven't done a scientific test of it.

Curious,

Alex
8,283 views 7 replies
Reply #2 Top
Click on the Civ Manager button on the bottom of the screen. There is a "Governor" tab in the window that opens.
Reply #3 Top
What version are you playing ? This was a bug in one of the 1.1 betas, never had it in 1.11.
Reply #5 Top
I have that bug too still. I even obsoleted the Ranger design and THAT didn't make it stop. I was still spending the money. God only knows what would have happened if I hadn't canceled it in the governor.
Reply #6 Top
This bug has been addressed in version 1.2.
Thank you for reporting it.
Reply #7 Top
I still have it in 1.11, and I think I was the first to discover it in the 1.1 beta's. The only way around it is in the Governor screen by selecting the Ranger on the left and Nothing on the right and updating. It happens, I am pretty sure, once you get the black hole mass driver and up to a particular armor defense.

I am glad to hear it is fixed in 1.2, just another reason to drool over that update.
Thanks CodeCritter, for mentioning that.