Talking about A, what could be done is to include features he said would included at next vbs version, but that were then included at C# (and not vbs) because he stopped working with vbs.

The idea is that those ideas WOULD BE vbs, not only that they got included at C# (only those included at C# would be included at quasar4x) and the fact they got included there shows he wouldn't change his mind during development of next vbs version and not include them at next vbs version.

Hey Kyle, could you include a Readme with your releases, including some basic information such as a project synopsis, where the saves are kept, and perhaps the licensing information? Have you decided on a license to distribute quasar under, actually? Recent patch notes in releases might be handy too, as well as a link back to the itch.io and forum directory.

I have a suggestion for a QoL improvement that doesn't even exist in C# aurora.

Mineral shipping civilian contracts. Bonus points if you could set the demand to use reserve levels.

As an aside it would also be nice to have the new "load minerals until full" order which is actually in C#.

I'd say this would be more useful that most of the stuff I've suggested so far.
Also the ability to move transfers ships in and out of civ control might be good.

Ok this is a bit of an extensive list, however a lot aren't radical gameplay changes. Just some SM mode tools useful for running the game.

The ability to manually set ruins level without continually rerolling.
The ability to spawn wrecks or defenders without spawning ruins.
The ability to remove ruins, Anomalies, and wrecks.
The ability to roll Anomalies.
A DB table with all of the anomalies and their properties so they can be modded.
An SM menu to add a Lagrange Point or body.
An SM option to add body with no properties in deep space.
The ability to delete bodies, JPs, and LPs.
When connecting a JP, it'd be nice if the list of options contained the JP's number and not just its position.
The ability to teleport fleets to waypoints.
The ability to move & construct ground troops using SM mode.
The ability to create empires on planets that cannot support life (can already do this by terraforming then un terraforming bodies).
A way to force communications between two races that have not encountered each other yet.
A dummy component with adjustable mass.
A way to un research tech.
When comparing techs a way to transfer all instead of manually transferring over dozens of techs.
A order to wait for N amount of time.
An option for system names to always be fixed.
An option for body names to always be fixed
The ability to force fleets to move faster than they actually can using SM mode.
A SM tool that terraforms to the indicated colony cost.
A SM mode screen for editing a planets parameters.
If the PD modes table had a adjustable percentage modifier to accuracy  and a count of the number of missiles launched at a target.
The ability to adjust precursor, star swarm, and ruin spawnrate.
[VERY IMPORTANT] Backup DB once  button.

The holy grail of features though would be to save / load ship & component designs from a file.
However I can see how that'd get a bit complicated.

Thanks for the suggestions   I may do some of these if more interest is shown or I run into the need myself.

I will add a Backup DB item to the Quasar4x menu now, for the next version.

"The holy grail of features though would be to save / load ship & component designs from a file."  I agree!  I've already started some work on this.  It wont be available in the next version(s), but I want to get it done eventually. 

Rather than reply to all of the suggestions I'll just list the ones that definitely wont be happening, mainly because they are nowhere near as simple to implement as the other suggestions:  A way to un-research tech,  The ability to force fleets to move faster than they actually can using SM mode, and an SM tool that terraforms to the indicated colony cost.

Ok this is a bit of an extensive list, however a lot aren't radical gameplay changes. Just some SM mode tools useful for running the game.

The ability to manually set ruins level without continually rerolling.
The ability to spawn wrecks or defenders without spawning ruins.
The ability to remove ruins, Anomalies, and wrecks.
The ability to roll Anomalies.
A DB table with all of the anomalies and their properties so they can be modded.
An SM menu to add a Lagrange Point or body.
An SM option to add body with no properties in deep space.
The ability to delete bodies, JPs, and LPs.
When connecting a JP, it'd be nice if the list of options contained the JP's number and not just its position.
The ability to teleport fleets to waypoints.
The ability to move & construct ground troops using SM mode.
The ability to create empires on planets that cannot support life (can already do this by terraforming then un terraforming bodies).
A way to force communications between two races that have not encountered each other yet.
A dummy component with adjustable mass.
A way to un research tech.
When comparing techs a way to transfer all instead of manually transferring over dozens of techs.
A order to wait for N amount of time.
An option for system names to always be fixed.
An option for body names to always be fixed
The ability to force fleets to move faster than they actually can using SM mode.
A SM tool that terraforms to the indicated colony cost.
A SM mode screen for editing a planets parameters.
If the PD modes table had a adjustable percentage modifier to accuracy  and a count of the number of missiles launched at a target.
[VERY IMPORTANT] Backup DB once  button.

The holy grail of features though would be to save / load ship & component designs from a file.
However I can see how that'd get a bit complicated.

Could somebody explain tracking speed to me?

I think you might be in the wrong board .

But tracking speed acts to modify beam weapon hit chance. A fire control has a tracking speed rating, and a beam weapon ALSO has a tracking speed.

If the beam weapon is not turreted, the weapon tracking speed is the larger of the ship's speed (whcih may decrease due to destroyed engines) and the racial tracking speed (which is just the highest level of beam fire control tracking speed tech you have researched).

If the weapon is turreted, the tracking speed is the turret tracking speed.

When you shoot at something, the smaller of the weapon tracking speed and the tracking speed of the fire control is used. This tracking speed is compared to the current speed of the target. If the target is slower than the tracking speed, you shoot with full accuracy. If the target is FASTER than the tracking speed, your accuracy is reduced by the ratio of target speed to tracking speed.

An example:

A 4000 km/s tracking speed beam fire control is mounted on a ship that goes 2500km/s. The ship has a hull-mounted laser, a turreted laser with a turret speed of 4000km/s, and a turreted laser with a turret speed of 8000km/s. The race has a 2000km/s racial tracking speed.

The hull-mounted laser will get a tracking speed of 2500km/s, because the ship moves that fast. Thus, the BFC has "excess" tracking speed. However, if the ship loses an engine and drops to 1250 km/s, the tracking speed will drop only to 2000km/s because the racial tracking speed acts as a floor. It would have full accuracy against anything going slower than 2500km/s. When the engine is lost, this drops to only 2000km/s. Its accuracy would be halved against a 5000km/s target (or a 4000km/s target once the engine goes).

The 4000km/s turret gets a tracking speed of 4000km/s, regardless of how fast the ship moves. Full accuracy against 4000km/s or less. Half accuracy against 8000km/s, 1/4 against 16000, etc.

The 8000 km/s turret ALSO gets a tracking speed of 4000km/s, because the fire control only goes so fast. Same accuracy pattern as the 4000km/s turret.

One last wrinkle: there is a tech for "missile tracking bonus." What this does is provide a bonus to the tracking speed of beam weapons (I'm not sure if this affects the fire control value, the weapon value, or the final tracking speed value that is normally the minimum of the fire control and weapon values). The bonus increases the longer the missile has been detected on active sensors. I've never used this and I'm not sure if it's actually implemented.

EDIT: literally unplayable typos

I wanted to do a comunity game in such format but realized real life makes it impossible. I also thod it could lead to functional multiplayer, the game would just pause when meaningfull decisions are available for a player.