ORIGINAL: pjcoia
Firstly, I want to acknowledge the amazing achievement which Command is, as well as the tremendous continued support given to it by the development team. I get tremendous joy playing what-ifs scenarios as well as the amazing scenarios both within the game and contributed from the community.
My suggestion, and apologies if it has been mentioned but search didn't show that it had, is around the interface for reference points. On a large scenario, the number of reference points can quickly become chaotic and confusing. It seems to me that the two main uses for reference points are 1) to define an area and 2) to define a route. Regular use has taught me that reusing reference points across two or more paths or areas is bad practice so I always have distinct sets of ref points.
So the idea is this: the user should manage Areas or Routes primarily (adding, editing or deleting). They could be attached to missions where appropriate and modified within that context (Support mission -> add/edit route). In other words, instead of adding reference points individually, selecting them (and hoping not to have selected a stray one), and then creating a mission, you create the mission and then define an area/route which may or may not only exist within the context of the mission.
Some of problems it would solve are: 1) accidentally deleting a reference point that you didn't know you had selected, 2) having stray reference points lying around from defunct missions, 3) moving reference points accidentally as the majority of points would now be related to defined areas/routes and no longer need to be editable outside of the missions they're related to.
Progression of the game has many of the elements needed for this: missions highlight the relevant areas/routes on the map, and no-nav and exclusion zones appear in the same way. I see this suggestion as the logical conclusion of this which is the removal of the need for raw reference point editing.
Paul
Added.