Interesting. Changing base carrying capacity of ships seems reckless. I can see it causing problems for the early game, which is already slow. Besides, all it really does is postpone what is already happening. Eventually, the civvies will just build more ships or larger ships and it all comes back again.

The maintenance idea seems good. A nice soft cap on individual potential. If I understood it correctly, it would only affect each line separately and so not cause problems with a growing empire, as new lines can simply pop up over time and fulfill that demand until they too become "decadent" and slow down growth to potentially nothing.

I think it is logical and appropriate that larger empires do things more massively and faster than smaller ones. Especially if compact in territory. It gives a sense of progress and allows the player to more easily marshall additional resources toward other interesting parts of the game. It provides a more or less clear transition between the early-game exploration phase where everything is slow; through the mid-game expansion phase where everything is fast; to the late-game exploitation phase where you can do anything you wish due to having infinite resources.

In my current campaign, I am 32 years into a conventional start and I have four shipping lines for the player race. The largest has forty-eight huge colony ships and forty-nine huge freighters, plus numerous smaller ones,  and seems to be building a new huge ship every few weeks. The other three shipping lines are considerably smaller.

The number of huge colony ships means that the civs will build up a new colony very quickly and also eat into source populations fairly quickly too.

So I am considering changing how shipping lines work, so they don't become so overwhelming, while trying to retain the flavour. I have a few ideas, such as halving the money received by civilian shipping, changing civilian designs so they are slower, significantly reducing the money for in-system transport, or maybe paying by distance travelled in km rather than transits made or limiting how often new ships can be built.

Another option is replacing dividends with a percentage maintenance payment, which is modified by an admin overhead that increases as the number of ships increases - effectively limiting the rate at which a shipping line can increase in size.

A more dramatic change would be altering transport for all ships, not just civilians, so less can be transported. That means fewer cargo points and less colonist capacity per ton.

However, I would like to hear other opinions and ideas before deciding how to tackle it.

So, a weird behavior I'd like clarification on:

In my current campaign, I have one player race in Sol, and then I've created a habitable system in SM mode and placed a second player race in that system. The second race is therefore aliens from a human perspective with no connection to Earth.

This second race has just explored their first jump point and discovered the system of 70 Ophiuchi. By which I mean, that's the name this non-Terran race has assigned to this star system, despite being a completely alien race that has never heard of Sol as anything besides a random G2-V star that they probably have seen in their telescopes at some point in ancient history, and which has completely different constellations in any case.

So my question is: if the game is being played with Real Stars (which I prefer for system generation), do all player races use the 'real' names for the star systems even if they don't start on Earth? And if so, is there any way to force the system names to follow the naming theme? The setting in the Galactic Map window does not seem to matter here.

SQL Raiders

Instead of railguns and slave ships, they just use queries to place your population in their home system while you shake your fist impotently. Truly Steve's most diabolical creation yet.

I can check, but it was more than one year ago and the longest travel time is 4 months. And still, it would not explain the 'freeze' on current AM count when producing an extra 0.2

Attach your DB if you like. I'll send my SQL Raiders to find the missing 0.2 automines.