In Aurora, there are a lot of things to manage.
To avoid spending more playtime than necessary managing relatively minor concerns, I use a simple system with three components:
1) Naming conventions for fleets and colonies.
2) Annual management task checklist.
3) Timer fleet.
An explanation of each component:
1) Naming conventions for fleets and coloniesI use a consistent naming convention for fleets and colonies.
Names of fleets indicate the fleet composition, as well as the location and/or task and/or capacity and/or needs of the fleet.
Example: FT ANT-A3 infra 245/yr Hlr x12 B
Interpretation:
- FT: Freighters. (Just the default hull abbreviation.)
- ANT-A3 infra 245/yr: Cycling orders to haul infrastructure to colony ANT-A3, with average throughput of 245 per year (varies somewhat by orbital positions of source and target colony).
- Hlr x12: Contains 12 ships of the Hauler class.
- B: Appending a unique letter per each fleet with the same hull abbreviation makes it easier to quickly find this fleet when a list contains several fleets with similar (or even otherwise identical) names.
Names of colonies include the base name (usually the name of the system body), plus the intended role and/or current task and/or current needs of the colony.
Example: _~ANT-A3 MINE DurBor -mines 25 ~500k
- _~: Special symbol prefixes help me quickly identify colonies with pending tasks. The underscore indicates a freight task. The tilde indicates a colonist task.
- ANT-A3: This colony is located at the planet ANT-A3.
- MINE DurBor: A mining colony with significant deposits of Duranium and Borium.
- -mines 25: Pending task to ship 25 mines to the colony. As I assign freighters for this, I update the name to indicate the remaining amount.
- ~500k: Pending task to ship 500k colonists to the colony. As above, I update the name as fleets are assigned.
2) Annual management task checklistMake a checklist of housekeeping tasks to be performed no more than once a year (or any frequency of your choosing).
Some of these tasks will involve assessing the status of fleets and colonies, and updating their names appropriately.
For example, suppose colony "ANT-A3 MINE DurBor" is my highest priority development colony.
If the colony's current infrastructure capacity exceeds current population, I will change the name to indicate a pending task to move colonists to fill it to capacity.
If the colony has available workers, I will change the name to indicate a pending task to haul in enough mines to occupy the available workers.
Examples of other tasks:
- Admin commands. Best commanders in place?
- Fleets. Check for hidden problems (bad cycle loops, forgotten fleets sitting idle, potential fuel shortages, active sensors or shields not turned on, etc.).
- Fuel and MSP supplies. Determine if additional production is needed.
- Scientists. Check for newly arrived (or recently improved) scientists with superior bonuses to those currently assigned.
- Shipyards. Did I leave idle any yards intended for constant shipbuilding? Am I adding slipways and/or adding capacity to all desired yards?
- Wealth. Am I spending the desired percentage on research?
- Minerals. Do I face near-term outages at any production centers?
- Orbital production fleets. Do I need to move any mining fleets due to depleting resources? Are my terraforming fleets performing as expected (or did I forget to check/uncheck a checkbox)?
3) Timer fleetCreate a fleet containing only a single trivial ship. (An empty no-armor hull costs 0.4BP.)
Give it a delayed Move order and a Send Message order, both of which target the fleet's permanent location, and cycle the orders.
This provides an event log interrupt at the frequency of your choosing.
Each time the event occurs, process your checklist.
With this process in place, I spend far less time overall managing the things in my annual checklist.
For example, commander announcements (new hires, promotions, retirements/deaths, etc).
Instead of stopping for each announcement and considering what adjustments to make, I just make an optimization check once per year.
This saves a lot of time, and the price is reasonable: command assignments becoming slightly suboptimal over the course of a year.
The exception to this is the death/retirement of an admin commander. An empty admin command breaks the chain of bonuses, so I always stop and make adjustments for those.