Allow UI fields for numbers (airspeed, altitude etc.) to accept variable and math instead

[twistking]

It's terrible design to have to adjust every waypoint's values, if you want to tune a flightpath for ToT or just change altitude for a complex flightplan.

I propose that instead of needing a number input on those fields, the editor would accept variables and basic operation. For example you could put "blu_cap_1_alt" in every altitude field of the flightpath. For certain waypoints you could put f.e. "blu_cap_1_alt + 1000" to modify the altitude per waypoint relative to the base value. The variable would need to be set at mission start. This way you could easily change while complex flightpath with only a single edit.

You could maybe also change the variable during mission for the change to take effect once the flight passes the next waypoint and the fields get read again with updated variable.

With this you could also do some quick randomization by having the variable value be selected from different possible values at mission start.