Better, quick&easy randomization options without lua

[twistking]

I often think that randomization is unnecessary complex in the ME.
I would like some simple tools and functions that allow basic randomization when you just want to slap a basic missions together rather quickly without utilizing lua framework or setting up a lot of triggers.
For example:

-> Have a field "condition of presence of group" where you can set a required flag, that is checked only in the first seconds after mission start to determine if the group is created at all.

-> Have a group option for "random start location", which would allow you to draw out multiple lines from the unit (similar to fire missions / cap areas etc.). On mission start one of the locations would then be used to spawn the unit on. Could have different options to spawn groups in formation (around choosen group leader position) or maybe even spawn each unit of the group individually on one of the dedicated positions.

-> Have similar options for Waypoint positions. This could be just a defined creation radius per waypoint, which would create the waypoint randomly within the specified radius, or a solution similar to the proposed random start position, where you could use an option on the waypoint and designate different position for the waypoint, where the game would then choose one randomly, either once on mission start, or everytime the waypoint is activated (when doing waypoint loops)

-> have either/or conditions for unit tasks/options in order for the game to randomly select one of a set of preset task/options. At the moment, you can only set a chance for the task/option to trigger, but it would be very helpful to have an easy way for the game to randomly pick one. Alternatively have more randomizations options within the unit tasks/options setting. For example: Randomize CAP search area between min/max values...

-> generally add "random between" min / max values instead of a single value to all ME fields, where it could be useful. This could be airspeed, flight height, (end) conditions for tasks, timers, unit task properties etc. In order not to clutter the UI it would also be possible to support a certain syntax for the field, so you could just put in f.e.: "15-30" and the game would select a number between 15 and 30 whenever that value is read by the game.

-> generally add "value a OR value b" syntax to all ME fields, where it could be useful. This could be airspeed, flight height, (end) conditions for tasks, timers, unit task properties etc. So you could just put in f.e.: "15 or 30 or 45" and the game would select either one whenever that value is read by the game.

Edited December 31, 2023 by twistking

[twistking]

*bumb*
I think that besides the missing undo function, the lack of quick and easy randomization is what makes the editor feel so archaic.