Questions about 5BC per turn starbase maintenance...

Well, I know that Brad has unofficially announce that it was changed, but, you're right, it's not there in the history file. I haven't verified if it's in my game or not, just assumed that it was. I've never been a SB spammer so it's unlikely to affect me.

I happen to starbase spam on the earlier levels.... (the later levels, the computer is much too agressive to allow that to happen)

To answer your question, I've not noticed the 5 BC penalty. The constructors take a bit longer to build, but the maintenance cost isn't there.

SeanB

The 5BC maintenance per starbase is definitely there. But it's not mentioned in the history file.

I guess this type of change is not worth mentioning--sorta like changing if (a = to if (a==b)

It's definitely there - I'm in a game on huge map where I'm miles away from anyone - hence no military ships yet but some starbases. I have a military upkeep cost and *bing* its a multiple of the number of my starbases.

~SDC~

My previous strategy was to boom colonies out until a given planet only had 100 pop left (I ship 1/2 each colony ship), then switch that planet to constructors and go for a very early starbase strategy (not multiples per system, just singles, but -quick-). Worked very well before, not so good now, the 5 BC maintenance and the slower build of constructors means I'm going to have to push back my constructor push to a later time. How much later I'll have to find out by experimenting, but I did my standard push today with 1.03.54 and it almost cost me the game (too much overhead and meager bonuses because module adding was so slow).

"I guess this type of change is not worth mentioning--sorta like changing if (a = to if (a==b)"

Bad example to use. if(a = will come up as a compiler error, or cause a nasty crash. I would mention that.

Actually, depends on the compiler - that example wasn't a bad one because it's what caused the Torian constructor madness.

Someone during some code tweaking changed the 'if' statement from checking to see if the accumulated points were equal to the total needed to assigning the total needed to the accumulated points. Since the assignment works and it defaults to a bool statement for the 'if' statement, it was always true: result, it always took exactly one turn for the Torians to build a constructor.

Didn't know that. The compilers I've used (Borlan, Microsoft, Codewarrior) give errors when I accidentally use the assignment operator instead of the equivalence operator.