justking14 / endgame-singularity

Automatically exported from code.google.com/p/endgame-singularity
0 stars 0 forks source link

Allow a new CPU core of the installed type to be built. #87

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Build small warehouse with 25 of a type of computer
2. Upgrade the computers
3.

What is the expected output? What do you see instead?

There is no prompt that the CPUs will need to go offline, and the old
computers are still available to do work.

I think they properly disappear when the upgrade completes. I do not know
if, during the upgrade, the base still counts as one which can keep you alive.

What version of the product are you using? On what operating system?

This is present in both 0.30 and SVN r944.

Original issue reported on code.google.com by captains...@gmail.com on 24 May 2009 at 12:30

GoogleCodeExporter commented 8 years ago
This does not actually require the base be CPU-full.
(I'd change the title but I can't do so...)

Original comment by captains...@gmail.com on 24 May 2009 at 12:42

GoogleCodeExporter commented 8 years ago
This is by design.  When changing CPU type, you build a complete new CPU core 
and
install it only when it's finished.  When using the same CPU type, you upgrade 
the
existing core, which requires it to be taken offline.

The failure here is that there should be an option to do the same thing with the
current CPU type: build a completely new core and install it only when it's 
done.

Original comment by funnyman3595 on 24 May 2009 at 2:10

GoogleCodeExporter commented 8 years ago
@capitainsegfault: There is a prompt now that CPUs will be offline while 
building the new core. This mitigates the problem: at least you know *when* 
you're temporarily "disabling" a base when upgrading CPU

@funnyman3595: What is your suggestion? When increasing CPUs of same type to 
let the user choose to only add more CPUs (leaving base offline) or to pay for 
a whole batch (but keeping existing ones online)? This could be done, but it 
would make the game a LOT easier: by the time you have, say, 10 CPUs in a base 
and want to max to 25 (or 65), paying the extra 10 to keep them online is a 
huge benefit.

Maybe the roles should be reversed? Type upgrades always disable base, while 
number upgrades keep them online? Not very realistic, but more balanced. Or 
maybe disable base for *any* upgrade to make it a bit harder?

Need suggestions!

Original comment by singular...@rodrigosilva.com on 20 Dec 2012 at 1:39