2.5.6.49798 - trigger "once", "mission start" do no longer work

[Wolkenbeisser]

Hi I'm new to this forum

 

 

Sorry if I didn't get the correct section to post this problem. Feel free to move the threat if needed.

 

 

I searched the forums, but I couldn't find another post which mentions this problem.

 

 

 

 

PROBLEM:

I built several missions under 2.5.5 for my small MP-squadron (6 pilots). In many of them I use the following trigger configuration to do some randomization at the beginning of the mission:

 

 

- once / at mission start

- random 50

- set Flag 1 to value 1

 

 

These triggers do no longer work with 2.5.6.49798. :(

 

 

 

WORKAROUND:

In one of my missions I changed the trigger configuration to this:

 

 

- mission start

- random 50

- set Flag 1 to value 1

 

 

With this it works again.

 

 

QUESTION:

Is there a fix planned for this issue or do I really have to amend all my old missions (would be about 20) :cry:?

 

 

As the mentioned trigger configuration is still provided in 2.5.6 to the users via drop down menues, I really hope that it will get fixed. Otherwise it would have been removed, wouldn't it (I mean many people would otherwise try to use a broken configuration)?

 

 

Thanks for a short reply and kind regards from Switzerland.

[discwalker]

Welcome to the forums

 

I tested a simple mission in Singleplayer, MP as host and MP with norender server in

2.5.6.49798 and everything is worked as intended. (Both messages appear, and both uncontrolled AI got the push start command.)

 

If we use random in the once type trigger conditions

it will continually evaluated until became true! At every seconds evaluated until fire!

 

Once type at mission start functioning only without conditions.

mStart_trig_test.miz

mStart_trig_test_rnd.miz

Edited June 7, 2020 by discwalker
rnd+mission edit

[discwalker]

the point is yours

 

both 2.5.6 stable and current openbeta

cannot handle a "ONCE" type trigger with event "ON MISSION START".

but old 2.5.5 stable can handle, but only for flag set not for message to all in this mission:

mStart_trig_test_onMissionStartEvent.miz

[Wolkenbeisser]

Thanks for the confirmation discwalker. I was indeed using this trigger method to set a flag.

 

 

I'm not sure now if I should wait for a patch or if I should amend all missions (by by spare time, then).