Ahhh thanks, Lucky - yes, I was testing it yesterday and had to turn that on to see everything. I will get that back to Allies Only.
Well, stick my foot in my mouth (again, sort of). I set up a little mission to do more testing on Clients triggering stuff. I have said a few times that Clients cannot affect trigger events just by being someplace - rather, the Client has to kill something to trigger an event.
After I made the half-joke about an OpFor warning message, above, I thought I'd test it to be sure. I set up both a Red and a Blue A-10C as Clients and had them enter a zone that triggers a message and sets a timer flag, and then 20 seconds later the a/c explodes.
This worked! I was surprised. I got back in the slot and flew through the zone again and it did not work the second time or third... Only if I restarted the server would it work, the first time only. But, the trigger event was set to 'ONCE'.
I changed the trigger event to 'Switched Condition' and on the explode trigger I added an action to turn off the timer flag. Now it works every time I fly through the zone without having to restart the server.
This is really news to me. I recall testing this while developing 'Riders ot Storm' for flying through the valley and setting off the mountain festival flares - and obviously I did not go far enough with the options to see it work. Most likely I was using 'Once' type triggers and maybe, too, I was having issues with flare height such that the flares were not visible at the altitude I'd used (I think I was way too high in altitude when I started that testing - 5,000').
Now that I think about why the 'Once' won't work even after I re-join the slot, it is prolly because the a/c Client Group/Unit (they are 1 in the same) retains the Once events regardless of how many times their slots are joined.
This opens a lot more possibilities that I had thought were not possible.