Allow 1 Mage Ultimate to be placed in a skill macro

A few balance patches ago we got a change where we are unable to macro the skills blizzard, genesis, meteor, roar, and DASH (i have no idea why dash was banned from macro).

The given reason for this change was "It was too easy to multiclient mages". I suggest to allow the above skills to be present in macros, but only once. This will keep the original intention of 1 key press = 1 ultimate, while restoring some quality of life features we had previously.

Quality of life applications restored:
1) ability to set different keys to the same skill
-One of the biggest use of in game macros is to have multiple keys perform the same action. Currently this isn't possible without third party tools (which can be against terms of service).

2) ability to bind in game command to ultimate skill
-Sometimes when you are grinding, you may want to check your eph. Instead of typing @epm, you can place this as the text your character shouts when using the skill macro.

3) ability to "buffer" input(s)
-Macros behave a bit differently compared to non macro skills. If you use a macro skill while your character is using another skill, your character will finish using the current skill and then start the macro skill. This is useful if you are rebuffing and then want to cast your skill ASAP or you just want to perform some actions ahead of time so you have a few more seconds to chat with your friends (without taking a hit to your grinding efficiency).

 

booster booster ultimate lets you hold down 1 button and clear spawn wave (while conserving pots), but the results will always be sub par to actually timing your ults. This doesn't help multiclient since in multiclient you can't "hold down" a key for 1 client, you don't have enough time since you are trying to manage multiple. So in theory this lets you attempt "afk" gameplay at the cost of exp and pots.

As for the buffering inputs, its a quality of life buff across all players single and multiclient. I understand if this ends up being the reason this suggestion gets rejected, but it is sad that the other two quality of life applications need to be sacrificed because of this.

 

I now understand what you meant earlier. I agree with you that it extends the window for input, but it does come with the tradeoff not timing ultimates on spawn (hence leading to knockback and the need to reposition).