@Wuzzy2 Great idea. :)
@Xenega Thanks for working on this. :)

I think we need a better way to deal with the g.pl.recalc_cpu() issue during loading of the save game. I was trying to implement a similar change before you submitted this and I had issues getting the recalc_cpu() flow right as well.

What do you think of g.pl.recalc_cpu() checking whether we are loading a save game and then ignoring the call if we are. The flag would be start when loading starts and the finally block for loading will clear it and call g.pl.recalc_cpu() once when we know everything else is loaded correctly?

OK, I have finally gotten around to actually test this, and it works fine.

One thing I noticed it that you are now able to change the power state in bases in which the CPU is complete, but you build other items.
Previously, the power state was locked at “Active” while building a non-CPU object in a base with finished CPU. I don't know if this is intentional, I'm just mentioning it to you, just in case.

Hmmm, another change I noticed:

While you are building CPU, the detection% goes down like in Sleep. Previously, you were fully vulnerable to detection while building CPU.

This is a major gameplay change which might make the game easier (not sure). I hope you know what you're doing …

@Wuzzy2 Yes it's intentional. I want to simplify power state to use only cpu.
@nthykier Unfortunately, better solutions needs to add completely new complex abstraction, so I will do that.