The disparity between the SC2 and WC3R trigger editors (gui) is pretty huge - I’d love to see that gap closed more.
But for the love of God, can we please at least get Local Variables in gui for WC3R in a patch update? I’m aware that there are workarounds (using custom script (but also having to use CS for the rest of the trigger’s local variable mentions), or ‘global locals’ (don’t work in loops, if/then/elses ect).
I don’t think asking for local variables in the gui is a huge request or major undertaking to achieve; and yet the benefits of adding them are major for intermediate-advanced mapmakers.
Thanks.
Told them about this in 2018. They tried. Too much of a major undertaking. They must have given up.
I don’t know much about this: any idea why it is such a massive undertaking? When the map runs, doesn’t just compile all the gui to script anyway? Whats the big deal to build locals into the gui, i just don’t get it? And i don’t see how it would mess up older maps.
They also messed up badly not building the UI natives into gui. Its so unaccessible right now to the average and even above average mapper.
Currently many parts of the resulting code are generated as seperate functions, making locals (as they are in code) not useful. Locals don’t exist for the serpate functions hence they could not use them. It would require a big undertake to change that.
I would be more in favour for other not yet ported code only features, than UI. This features would require less skill and are less dangerous for the User/Mapper.