Quote from: Steve Walmsley on Today at 04:53:48 PM

There is generally only one population per system body, so it would just add an extra layer that would be almost always redundant.

when you use genetic modification you end up with more then one on a system body and if you already have a bunch of colonies in a system before using genetic modification the new 'Race's' Colonies end up being so far down the line that it makes dragging a ground unit to the new race's colony impossible. maybe having them sort by name instead of creation order would be better?

We already have a system in the Economics window (image below, cropped and edited for size reasons) for displaying this information without an extra layer:



I would suggest:

• Modify this scheme for the ground forces window to list each population preceded by the system body name (unless both are the same, of course)
• Follow David's suggestion to sort by system body (perhaps optionally, as this could be toggled as it is in the Economics window).

Under these conditions, the ground forces display might look like:

[-] Sol
 |  [-] Earth
 |   |  [+] I. Corps
 |   |  [+] III. Corps
 |   |  [+] VI. Corps
 |  etc.
 |  [-] Luna - Genetic Research Base
 |   |  [+] 192nd Special Guard Brigade
 |  [-] Luna - Tranquility Base
 |   |  [+] Lunar Brigade
 |  [-] Mars - Cydonia
 |   |  [+] II. Corps
 |   |  [+] Martian Brigade
 |  [-] Mercury - Erebor
 |   |  [+] Inner System Brigade
etc.

It looks a little odd at first but would solve the issue without extra layers of information pretty neatly, and it could optionally be toggled if there's any space left in the ground forces UI to add yet another check box.

Wow Steve! Looooove the standing order changes and fleet waypoints! As if 2.6 wasn't already awesome, you just kicked it up a notch! Can't wait!

On the ground units Order of battle tab, can the hierarchy be: System>SystemBody>Population, Instead of what it is now: System>Population? It would make dragging units from one population to another a lot easier when you have a lot of colones in the same system thanks

There is generally only one population per system body, so it would just add an extra layer that would be almost always redundant.

Fleet Waypoints

A Fleet Waypoint is a new waypoint type that is associated with a specific fleet. A fleet can only have one Fleet Waypoint and if a new one is created, the one old disappears. The Fleet Waypoint will also disappear at the point of arrival, if the associated fleet uses a movement order with that waypoint as the destination.

A Fleet Waypoint can be created in several ways.

• There is a new Create Fleet Waypoint movement order, that will create the waypoint at the selected destination.
• On the military tab of the Tactical window, selecting a fleet and clicking 'Create Fleet WP' will create a Fleet Waypoint for that fleet at the fleet's current location.
• On the same military tab of the Tactical Window, 'Set Fleet WP' functions in the same way as Normal WP on the waypoints tab. The cursor changes to a cross and clicking on the map will create a Fleet Waypoint at the clicked location.
• There is also a 'Create Fleet WP' on the Movement Orders tab of the Fleet Window, although this doesn't immediately update the tactical map.
• There is a checkbox called 'Set FWP' next to the Add Condition button (see screenshot below). If this is checked when a Condition is created, that condition will be flagged to create a Fleet Waypoint at the fleet's current location when triggered.

"MV: Fleet Waypoint" is a new standing or conditional order that will cause the fleet to move to its associated 'Fleet Waypoint'.

This new functionality provides a number of different options for fleet orders. For example, the fleet in the screenshot below has "MV: Fleet Waypoint" as its first standing order. Most of the time this will not trigger as no Fleet Waypoint will exist. If however, the fleet triggers the Refuel conditional order, that order will generate a Fleet Waypoint. Once the refuel order is completed, the first standing order will be checked and the Fleet will return to the location at which the conditional order was triggered. On arrival, the fleet waypoint will be removed.

Alternatively, a fleet with survey standing orders could add "MV: Fleet Waypoint" standing order after the survey orders, then use a movement order to drop a fleet waypoint at its entry location. Once there are no remaining survey targets, it will move to the fleet waypoint.

The "MV: Fleet Waypoint" standing orders works for multi-system journeys. If a Fleet Waypoint is created on a system body, or by a fleet in orbit of a system body, it will move with that body.

How will the new standing order templates propagate through to both detaching subfleets and squadrons? I don't actually recall what the current functionality around propagation is though tbh.