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.

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

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

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.

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?

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>