Blindspot

You're welcome!

I hope so! Thank you Case! We will see if there is anything left to do in the future... :)

The random thing should be no problem. Would be a kind of "DO_ONE_OF" extention to the action list box, what means it would not affect the rules. So one could create a trigger, that if all rules evaluate to "true", would randomly pick one of the actions and execute it. For your example this would be like that: MISSION START -> IF (nothing) -> PICK ONE(SET FLAG(1), SET FLAG(2), SET FLAG(3), ...

Just combine Case's probability handling with my post, that is how it was meant. Currently triggers, rules and actions ARE run in the order they appear within the lists. I think to add IF-THEN-ELSE blocks for most users adds a lot of confusion too, especially when built into "dialogs" and "forms". Also the "workload" you have as a user to create triggers and rules will not be less. Maybe it would be better to make an expert mode, where experienced users can write down their LUA script directly.

Case, you are right. Why simple, when you can make it complicated. (clumsy translated from German) :doh:

In your case, an action "RANDOMLY SET ONE FLAG BETWEEN (1, 5)" would be more helpful, because step-by-step evaluation of different RANDOMs will never be fair. You will always need to have a static default action as a fall back, in case every RANDOM call is "false". As a work aroud I would suggest the following: If you want to have one of a number of 5 flags to be set, giving each of them a individual chance of 20%, do this: 1) Create a new MISSION START trigger 1.a) Select trigger logic button "(A) OR (B)" 1.b) Insert rules "RANDOM(20%)" and "FLAG IS FALSE(x)" into list A 1.c) Insert action of your choice (set a flag or activate a group...) 1.d) Insert action SET FLAG (x) 2) Hit the trigger clone button 2.a) Change the action to be performed 2.b) ..repeat 2) 3 more times 3) Create a new MISSION START trigger 3.a) Insert rule FLAG IS FALSE(x) 3.b) Insert default action of your choice If you activate the SAM groups directly, all is done only once during mission start.

I believe, I did not understand what you want the triggers to do because to trigger "one and only one action" only one flag and no SubTrigger is needed.

Aha. So just use the mod like shown in your screenshot. It's exactly what it does already.

@HiJack: You mean the "eye candy", rendering a "OR" symbol into each list entry? Or what do you mean?

@Nomdeplume: Please tell me, what do you want to do?

Maybe, yes. But I hope they will extend the runtime by creating more flexible trigger conditions. 1) The discussion you reffered to concerns runtime features not the editor. You can easily create the wanted effect using triggers and it's not sooo time consuming to insert some of them. 2) This feature is already there - twice - also without any mod. ("Time hold" for objects, rule "Time more" for triggers)

I could have a look at this. If it's really the editor that "corrects" the height, this could be fixed easily.

Yes, I like these "debugging features". My original idea was to allow the user to simply name the flags, but tracing references is a good idea too.

Please give me an example.

Wow! That's cool! :thumbup:

It would be possible to place the buttons below the checkboxes but that "wastes" space and makes the already short group list even shorter. Would this be really neccessary? Please use 1280pix or above hor resolution ... and now you know that "CL.." means "CLONE". :)

"Detected by coalition" is not achievable by simply combining existing functionality. This would require changing the game runtime what is not wanted because of compatibility and integrity reasons. I'm sorry, the answer is NO at present. Rules like coalition- or group-zone combinations are possible because they are only a shortcut (like a macro) to existing rules and therefore only require the extention of the editor logic. They make life easier because you don't have to hack all these existing units into OR-combined "UNIT IN ZONE" lists and you do not have to take care of recently added units you maybe forgot to add to those lists. You simply have to add one smart "COALITION.." or "BLUE GROUND UNITS IN ZONE" rule and the editor does the rest. That's the idea.

Next features could be some more complex rules like "GROUP INSIDE ZONE" or "COALITION INSIDE ZONE" or "ANY UNIT IN ANY ZONE" or smth like that. Also I find it's a good idea to track rule dependencies. (->nomedeplume :thumbup:). I think about to implement this a bit more "space saving". Would this be ok?

You're welcome

Thank you and have fun! :joystick:

Yes and you can choose between 1) (AND) OR (AND) 2) (OR) AND (OR) This means for the scenario in the picture, that Flag2 will be set IF simulation time is greater 60 seconds AND EITHER FLAG1 is true OR Unit#1 is inside zone Z1. In other words, "at the earliest of 60 seconds after mission start, Flag2 will be set to true if either Flag1 is set or the unit is inside the zone, what ever will be true first". If you now hit the button "(A) OR (B)" leaving everything else as it is, Flag2 will be set IF EITHER time is greater 60 Seconds OR all of the conditions in list A (Flag1 is true AND Unit#1 is inside zone Z1) are met. This means "what ever will happen to Flag1 or the unit, at least after 60 seconds mission time Flag2 will be set true. If the unit is inside the zone AND Flag1 is true at the same time, Flag2 is set to true even before 60 seconds are over." I implemented two lists because simply changing between AND and OR in one list does not allow what is needed so often: a set of OR combined conditions (like "player 1-8 penetrate trigger zone") under certain circumstances (like "we are in war").

ModdedME Mission Editor MOD V1.7 is ready for download. http://forums.eagle.ru/showthread.php?t=55463

Thanks Dragon! [i just edited first posting]

Version 1.7 will be available this evening. It features <51>Case's bearing bugfix, introduces AND/OR trigger logic and more. Please see 1st posting for details and links.

FLAKs? You mean "Flugabwehrkanone"? Cloning zones would be possible, but why should I do this? Zones are created with two clicks.