As shown in the video, inputting swap->wall too quickly prevents swap from coming out and only wall from activating. The combo is still possible by introducing a slight delay after inputting swap.
My guess as to why this happens is from her ult being activated by quick cast - as implied by the range radius briefly appearing when used. Since quick cast always has a slight delay before activation (I assume due to input release being the condition for casting), using an instant cast within that delay prevents the quick cast from happening. In this case, since I have wall set to instant cast, using it immediately after inputting swap prevents swap from activating.
Assuming that her ult is considered a quick cast, it feels clunky to have an interruptible delay before activation, and counterintuitive for the second button inputted (i.e. wall) to take priority in activation over the first button, especially since swap seems to activate briefly after a button press instead of a button release.
I believe this can be fixed by giving instant cast properties to Paradox's swap.
My guess as to why this happens is from her ult being activated by quick cast - as implied by the range radius briefly appearing when used. Since quick cast always has a slight delay before activation (I assume due to input release being the condition for casting), using an instant cast within that delay prevents the quick cast from happening. In this case, since I have wall set to instant cast, using it immediately after inputting swap prevents swap from activating.
Assuming that her ult is considered a quick cast, it feels clunky to have an interruptible delay before activation, and counterintuitive for the second button inputted (i.e. wall) to take priority in activation over the first button, especially since swap seems to activate briefly after a button press instead of a button release.
I believe this can be fixed by giving instant cast properties to Paradox's swap.
