There is only one event with the param \g and another one with \G:
\s attempted to execute transfer orders with \g involving either fuel or colonists. The attempt failed.

\s had orders to transfer cargo to or from a \G. A futile pursuit.

If someone can simulate а game with these events and send me an m + xy files, then I can say exactly what is this.

Yes, there is a count and damage per design id in fleet inside fleet block.

export players (player id, logo id, singular and plural names)

export planets (planet id, original/current environment, minerals concentration and available amount, starbase design id and damage, rout to target)

export designs (including design name, hull, items on board)

So far I have all of these info extracted, just need to carefully drop it to CSV.

I thinking of the one command line for all of this, just with the different switches like: /export players, /export planets, /export designs, /export fleets, /export events.

just wondering, what kind of tool(s) are you going to do first once you have all of this info exported?

* "routes" checker/tweaker
* "packeting" checker/tweaker
* "fuel" checker/tweaker (better if all waypoints known, not just the next)
* "danger" analyzer
* external shipdesign organizer/tweaker/library
* prod Qs checker/tweaker
* pop & mins "optimizer"?