One can get the status report from CLS1 by selecting homebase in "Add Factory".
And indeed, the initialization is occasionally odd. I used to start the CLS once right after setting homebase and before adding the ware.
There are 'beeps' and 'burps'. IIRC, succesful add of ware is single beep, removal of ware is double beep, and error is 'burb'. Or whatever that tone is.
CAG/CLS count accumulated flying time. Time spent on actual hauling runs. And one level requires two hours. So fastest learners are those that fly practically non-stop.
One trick is to set a CLS2 ship to run between waypoints without actualy hauling anything. And then transfer the experienced pilot into "production freighter".
Another thing you can do with CLS1 is to adjust the ... there are four configurable options, which you can set only with the CLS2 Config command. Furthermore, you have to stop CLS1 for the command to be available.
The {2}{4}{X} can be used to force-fly. The X is 5 by default, ie if the producer (usually homebase) has at least 5% in stock, the ship will fly. Drop that to 0, and the ship should fly whenever the producer has anything. But I use it usually in weapon Forges, set to 85%. 6/8 < 85% < 7/8, ie the ship will fly when the forge has 7 guns in stock. And the Forge does not have to stop, because it will never be full.
The {2}{5}{X} is about the consumer. The default is 95. Do not run, if the consumer is already over 95% full. When serving a Factory/Complex, I tend to drop that to 50%.
And then is the {0}{1}{X}. Name. I prefer option 3, both on CAG and CLS.
Finally, {2}{3}{X}. Fuel. No need for the Boost Extension.
To show some of them, lets tell about an
user error. I do know very well that 99% of problems are user errors, simply because it is true in my game.
I had a aPBE Forge (Complex actually). And I did set up a Hydra (a M6) to haul them to a TL (needs experienced pilot, which I had). So CLS2-Config {2}{3}{800} to use most of cargobay for fuel; aPBEs do not need much space. And everything worked fine. But I got more aPBE production around the universe, and the 800 ECells started to feel potentially small, and the space for aPBEs too. And worst of all, the homebase does not list M6/M7 as "Owned ship", so tracking the CLS1 ship was not easy.
Finally, I took a Caiman Hauler, and transferred the pilot from Hydra. Increased the fuel storage to 3000 units; still plenty of space for the payload. And everything seemed dandy. Until yesterday. A complex was full of aPBE. Another too. And the CLS1 remained on "Standby". The status report seemed all fine too. A restart made no difference. Finally, I did enabled the script editor, turned script debugging on the ship, and watched the debug output.
Trivial error: no Transporter Device on the Caiman.
You do need one, if you do deliver to TL, like I do. And this was not the first time that I have made similar "change ship", with exactly the same mistake.
