What's the point of queing up constructors

I just qued up a but load of constructors only to find my ships idle. Why am I queing up constructors if they don't go to their targets.

6,151 views 4 replies
Reply #1 Top

was by chance the first ship out of your shipyard not assigned and it created a fleet?

I ask because I think if a ship is where your shipyard exists, they create a fleet, which I believe follows the command of the first ship. Thus they wouldn't move to your bases. 

Reply #2 Top

Are you manually queuing up ships in your shipyard build list, or are you queuing up constructor requests in your starbases?  If you are manually queuing up constructors, they won't know where to go. If you are queuing up constructor requests, they should show up in your shipyard build lists as "Starbase Factory (for Starbase Draginol 1)", or something like that.  They don't keep those labels when they get launched (darn), but if you are tracking to see if it is working, it can be helpful to see where the next constructor thinks it should be going.

One thing I do to help keep things straight is name my default starbase upgrade constructor designs, "up1", "up2", etc, according to how  many constructor modules they have. That keeps them different from the constructors I manually build in order to have them go out and create starbases.

Otherwise, I can't account for what you are seeing. Any more details available?

Reply #3 Top


I just qued up a but load of constructors only to find my ships idle. Why am I queing up constructors if they don't go to their targets.
End of quote

I'm not aware of any problems with idle constructors.  Can you give some more details?

Reply #4 Top

Sorry pshaw I was a little impatient they go to the shipyards just fine it makes no sense to have it in the ship list. The ship list is how I play my turns, so when I clicked on them they hadn't moved when I let them move then they moved to the shipyards sorry my bad.