release problem

[Volcano Man]

OK, Everyone stop; I think you are both talking past each other. Here is the one post that should settle the issue (as mentioned, I already tested it and confirmed it). Firstly, it is not a bug. Here is the step by step procedure on how this whole mess happened:

1) A corps organization is assigned a fix (or begins the scenario as fixed already)

2) The user assigns the subunits of that fixed corps to another corps (ie. moves the divisions to another corps)

3) The original corps that the subunits came from has a release and when it comes up the fixed sub units (as per #2), which are now assigned to a different corps, do not get released.

----------------

There is only one way to make this issue "better" for scenario designers. In the release dialog, it would be nice if there was a check box (that is "on" by default), something like "Apply to attached units". When that is selected, then releases apply to the formation and those that are currently attached to it (ie. this is only applicable if the fix/release is set at corps level). With the check box not ticked, then it means that fixes and releases apply only to the corps original unmodified structure according to the OOB (ie. the original divisions of a corps could be fixed and released even if they are not currently under that corps anymore).

Anyway, barring a change like that to the editor, the solution here is the following:

A) As a user playing a scenario, do not change corps attachments for divisions that are fixed -- if you do, then you better reference the releases dialog first.

B) As a user playing a scenario, do not cheat by moving divisions between corps that will get released earlier.

C) As a scenario designer, avoid creating releases at the corps level at all costs.

Case closed really. No bug per se, just follow A, B and C above. There really isn't much else that can be said about it.