Gimme a Governor/Type for automation of the entire tech-tree so i can concentrate on better things, please.
I'm almost sure, somebody might have proposed this before. Let me add to the importance of it, then.

I found myself in pretty steady patterns when it comes to "intuitively" select the sequence of research projects. Here's the suggested list of features which would need to be considered before even attempting to devise the code necessary... along with some pro & cons.

1) Optional and pre-defined in saved files listing the paths. (Even, some players could share their solutions via library uploads, then people could foreplay the things right through their games.)
2) Focus targets by choice. (Once we reach a certain branch or even a specific category, it could be useful to be told cost/weeks/totals and some of the key results that leads to.)
3) Slap a task to the governor, and simply forget it -- BUT, with a rapid pull-out option to "insert" an emergency switching to another tech.

PROS:
- Huge step towards easing MicMan.
- Encouraging steady paces progress via choices made in advance.
- About 450 extra-mouse-clicks less in any typical smallest games. Grows as time goes by.
- 75% increase in development pace. Indirectly.
- Fleets continually self-monitored by the governor since key-techs raise a toggle to upgrade. Y/N. Keep going.

CONS:
- New.
- Lack of trust or the impression to lose some pace when the on-going project (either within a focus target or in a global framework determined at & since boot-time) seem to be too slow for the advantages to be received later.
- Nothing much else! I think.

If the above sounds like i'm asking to hand-over the AI's processing "techno-paths", so be it. I really don't care, since in the long run and through observation(s) somebody is trying to figure out this stuff, right now. Might as well give it to the masses.

- Zyxpsilon.