You are unable to build constructors at this time

Unclear as to what your trying to do and what you have done.  BUT it is a very bad idea to touch the schema files, guaranteed to break thins if you do. Only change xml files.  To modify the constructor summoned by starbases, edit the default in shipblueprints.xml.

You might want to verify your files with Steam. It sounds like you might have deleted the base game design for the constructor as that is what starbases call for when requesting constructors unless you've done what a0152570 is suggesting.

Thank you both for your recommendations. Conducted the files verification of Steam - It has restored 7 files, restarted game but no change in behavior.

What I have done is probably deleted the basic constructor schema within Designer. I haven't changed anything outside of the game GUI so no changes in the file system. I was cleaning up the tidal wave of Constructor schemas - this is also necessary as the bases only order the most expensive one per default.

So I was searching for the shipblueprints.xml but no luck finding it in Steam app Common DIR nor in Games DIR of the user profile. If I could set the basic schema to be used in such a file that would of course be wonderful but can't imagine it would be that simple as the DEVs would have done it already.

It's under Steam\SteamApps\common\Galactic Civilizations III\data\Game.

he, sorry gave you the name a bit wrong

/data/Game/ShipBlueprintDefs.xml.

If yot want a low cost const. with max modules and engines, Replace the constructor blue print with:

 <!-- my New Constructor Begin Blueprint -->
 
  <ShipBlueprint>
    <InternalName>ConstructorBlueprint</InternalName>
    <ShipHullType>Cargo</ShipHullType>
    <Role>Support</Role>
    <RequiredComponentType>ConstructionModule</RequiredComponentType>
    <ComponentType>ConstructionModule</ComponentType>
    <ComponentType>InterstellarDrive</ComponentType>
    <FillerComponentType>ConstructionModule</FillerComponentType>
    <FillerComponentType>ConstructionModule</FillerComponentType>
    <FillerComponentType>InterstellarDrive</FillerComponentType>
    <FillerComponentType>ConstructionModule</FillerComponentType>
  </ShipBlueprint>

Suggest you do it as a mod and not in the game directory but it works either way

Ok, I do seem to have a ConstructorBlueprint in that file:

  <ShipBlueprint>
    <InternalName>ConstructorBlueprint</InternalName>
    <ShipHullType>Cargo</ShipHullType>
    <Role>Support</Role>
    <RequiredComponentType>ConstructionModule</RequiredComponentType>
    <ComponentType>LifeSupport</ComponentType>
    <ComponentType>LifeSupport</ComponentType>
    <ComponentType>InterstellarDrive</ComponentType>
    <ComponentType>LifeSupport</ComponentType>
    <ComponentType>LifeSupport</ComponentType>
    <ComponentType>Sensor</ComponentType>
    <ComponentType>InterstellarDrive</ComponentType>
    <FillerComponentType>ConstructionModule</FillerComponentType>
    <FillerComponentType>LifeSupport</FillerComponentType>
    <FillerComponentType>LifeSupport</FillerComponentType>
  </ShipBlueprint>

Do I need to add back a basic constructor here in order to be able to order these from the star bases?

If yes can some please tell me the InternalName the bases use as reference? - The game might have deleted this when it is deleted in the Designer

No, Replace it with my blueprint.  It will be the constructor used by the starbae Request Con.  It becomes the default constructor,  note it has minimal eng and no life supp, but starts with 2 modules and 1 eng (mass permitting) & continues adding modules and engines as your capacity grows. So if you want a fast or long range one you need to design it (or change my blueprint). 

Thanks a0152570 I tried that and it works fine. I can now also see what you were getting at. This is a good solution to replace the default Constructor and thus resolves the problem with ordering more constructors via the bases.

What I was looking for though is more on the other two ends of the problem:

1. How can we configure the bases to always use a minimalist design from the get-go without affecting the default constructor line as that also affects AI and our starting constructors leading to the necessity to always design a new one for longer range for each race (it also messes with the tactic of getting the 3 free contributors with ideology to snatch resources far away). So ideally we should have:
• The basic Constructor line present today and not used by bases per default
• A minimalistic design used by the bases per default
2. What do you do once you have Obsoleted the default constructor? Luckily It does not affect new games but the existing one is toast once someone does that as the error will render the ordering option useless. Considering the redundancy and long list of ship schemes I can image that obsoleting the default ship is a common event and thus the error as well

 As long as we could edit the bases config to reference another blueprint both of the above could be solved. We could tell it to take a specific custom template and define that template to only contain the components you have listed.

hay LoV

1) Sorry no way to do this.  When request con was first introduced it had a Basic Con but it never upgraded so it was always slow with only 1 module. Why they did it this way, no idea.

So yes, with my 'fix' , if you need a long range con, you need to design one but i don't mind this.

2) Not true in 1.4. If you obsolete the default and request a con, it reverts back to a Basic Constructor.

I agree, wish they would have done this.

A complete redesign of starbase building is coming so all this is going to change

Hm... it doesn't work like that in my 1.4 version ... maybe that is the one I have deleted

So this suggests there was another schema in that file called Constructor Basic or something similar and if I place it back in again, the bases should find it again.

Can you please forward the parameters of that schema if you can see it in your file?

I poped into my 1.4.1 game and Base con works, dont recall but i though it did the same in 1.4.

Yes, in the same file there is a print for BasicConstructor (do a search).  Note it has <CanBeBuilt>false</CanBeBuilt> so it will not show up in shipyard or designer.  It is only used if the default has been deleted

Tried below but the bases do not seem to consume the schema, is the name correct?:

  <ShipBlueprint>
    <InternalName>BasicConstructor</InternalName>
    <CanBeBuilt>false</CanBeBuilt>
    <ShipHullType>Cargo</ShipHullType>
    <Role>Support</Role>
    <RequiredComponentType>ConstructionModule</RequiredComponentType>
    <ComponentType>InterstellarDrive</ComponentType>
    <FillerComponentType>ConstructionModule</FillerComponentType>
  </ShipBlueprint>

BasicC will only be used IF you obsolete the default.  I don't know if or how you can  have both.