Erik2 wrote: ↑Wed Sep 18, 2019 7:55 am
I hope someone pays you overtime for the Extra editions...
I have not checked every scenario in your list, but I got a general concern.
I usually use 'scenario end turn' conditions for rewarding sec objs. As far as I know this is the only way to check if for instance units have survived etc.
What do you suggest instead of this condition?
The pri objs probably need to stay as is in these scenarios.
Yes, I know you do "use 'scenario end turn' conditions for rewarding sec objs." Fortunately, I hope, there is a workaround because I don't want you to have to revise any primary objectives.
In the "CSI Sweep: Germany West 1944" thread (which is finished, by the way), I was reviewing Falaise when this matter was uncovered. In conjunction with that scenario, I said the following:
So. Here is the first instance [I meant, while doing that CSI sweep]
of the new "What does 'Scenario turn limit' mean, exactly?" rule:
- Screenshot 4.jpg (203.75 KiB) Viewed 1970 times
Unless somebody comes along to negate what I showed in that thread and what Gabe confirmed, we need to keep this in mind: To use Gabe's words, "awarding secondary objectives at scen turn limit without the primaries being awarded only at the end also, makes no sense." Thinking positively about this "hopeless scenario," 
"The scenario will end when 8 objectives are on German hands." Unless that happens on the very last turn, this "Units survive" trigger will never fire because it is set for "Scenario turn limit" which is literally "Turn = 20."
Wow, how many times have you used this sort of secondary objective design using "Scenario turn limit" with early-ending scenarios? Well, the question is moot. [Well, I chose to "unmoot" it, as you can see.]
At least we will know what to look for in the future.
So how to design this type of thing where a condition must persist until the scenario ends, whenever it does, so that a reward may be given? Here's a suggestion; remember it's based on the objective being marked as competed to begin with, only to fail if more than 3 units are destroyed:
- Screenshot 8.jpg (218.08 KiB) Viewed 1970 times
- Screenshot 9.jpg (208.32 KiB) Viewed 1970 times
First, the fail trigger turns off the rewards trigger.
Second, the rewards trigger checks for the primary objective being completed.
Third, the rewards trigger is set for the same event that triggers the primary objective and ends the scenario; in this case, "Capture VP Event."
In the following post in that thread, I included a report of instances of this issue that I saw in Germany West 1944 upon revisiting prior scenarios. There weren't very many. You can pick up the thread from that point on as to whether there were any more.
So in general, in the secondary objective trigger, you would need a "Check [Primary] Objective State" condition for each primary objective trigger that could possibly end the scenario early. Basically, you are timing the secondary objective trigger to fire as soon as every scenario-ending primary objective has been completed. Try to use the same Trigger Event if you can or, if more than one event is involved, fall back on "Any Event."
