salty said:
What would be nice is if I could set a default garrison (e.g. 2 longbows, 1 pikeman or 3 mech infantry, 1 SAM) and have the computer spam out the appropriate units and send them off to the correct city.
Now
this is an idea that I could take and run with!
Today automation means you are delegating an important task, such as worker actions, build queue management or population assignment, and leaving a broad range of decisions in the hands of the AI.
Lets have an option for an automation interface that allows the human to quickly delegate a lower level set of objectives that leaves fewer decisions to the AI, basically letting the AI take care of the grunt work. Not quite as much micro management as queueing the actual commands but not quite as hands off as we have today.
The example above is a great one, in each city I want a default garrison of X, Y and Z. Another example would be to automate a worker based on a plan for city improvement...I want cottages here, farms here and mines here, plus these tiles need roads...go do it, oh and my priority is food supply first.
Even something as simple as setting a population target for a city, or a production target. "Grow Berlin until it has 16 population with a focus on generating hammers" might cause the AI to produce a city that has 13 tiles worked and 3 engineering specialists.
I guess what I am saying is rather than a broad 'focus on production' order I want to be able to set specific targets. (Mr. Governor, I need this to be a city that can produce a modern armor every 3 turns

)