sbach2o
Posts: 378
Joined: 3/26/2010 Status: offline
|
quote:
ORIGINAL: elliotg quote:
ORIGINAL: sbach2o The problem was discussed at some length in this topic. See in particular Elliot's explanation in the second post. I still think that the issue shouldn't rest with that. The behavior of ships you are trying to command is apparently in some very unhealthy way connected to a global setting affecting many, many ships in your empire. This shouldn't be the last word. But don't expect a quick fix. Note that the "Default Engagement Stances" in the Empire Settings screen (from Game Options screen) are not really global settings in the way that you are describing them. These "Default Engagement Stances" are simply the stances that are set for military ships when you assign specific mission types. Effectively these are shortcuts that set the engagement stance to something logical for the mission type, without you having to manually do this each time. If you do not like the current default stances you can change them to anything else. If you do not want your engagement stance overridden at all then in the "Default Engagement Stances" panel (Empire Settings screen) simply use the setting "No default stance". Then your military ships will always stay on their current Engagement Stance (whatever you have manually selected with the Comma key). I'd have to try that out, maybe I was making assumptions. These assumptions were: In the Empire Settings there are four categories 'Patrol', 'Escort', 'Attack' (?), 'Other'. The first two of these look like they directly correspoind to orders military ships can perform, so I was assuming they really apply there. About the one which I have forgotten , I don't know (Attack? then the default setting is sensible), the last looks like a fallback as in 'use this for ships which have no specific orders in the former categories'. In each category you can select between four stances. The settings for 'Patrol' and 'Escort' are fine. It is the 'Other' that causes most of the pains when its setting is 'Engage system targets'. Usually, having it at 'Engage nearby targets' works, unless the ship is directly attacked. Then it won't get the message when you tell it to run or do something more important, until other automation settings kick in. The idea to use 'no default stance' didn't occur to me, because, well, it#s meaning is completely nebulous. The problem is, that the 'other' applies to lots of military ships under automation. Those can have orders 'Move to' or no orders at all. Then, the stance shown for them seems to match the setting under 'Other', so I was assuming they all are affected. What about the setting no default stance? When it means that they retain the stance form their last mission (is that correct?), that'd be fine and make it the superior setting to engage nearby targets which I typically used because it seems to work with most direct intervention, but has the global effect I mentioned. I.e., if you set it to 'engage nearby' which lets ships respond satisfactorily to direct order most of the time, all those ships that could and should hunt down threats system-wide, only do so when under 'patrol' order. Still, even a 'retain stance from last mission' as I am assuming above, would be a global effect a bit different from the 'engage system targets' I would prefer for military ships not under my direct control (as of the default setting for 'Other').
< Message edited by sbach2o -- 12/6/2011 10:02:59 AM >
|