What was the reason to take Command: Dissonance input buffering off of Orianna?

MinaZer0·Nov 29, 2016·1 votes·832 views

As soon as someone in Pro play (Faker) decides to play her (and succeeds) and she gets attention she gets a QoL(??) nerf? Also how it is considered a bug at all? Input buffering is on every champion. Its the same concept of {Spell + Flash} and it instantly happens once your character model gets within that parameter, in this case because of the special interaction "We are as one" , the Ball IS Orianna so once the ball(Orianna) gets within that parameter the spell is released, also how can you say "We’re reverting a 'bug' we introduced that allowed Orianna to chain her abilities in a way that was TOO HARD TO REACT TO" WHATT?!? . I haven't even tested it yet but it sounds like unneeded amounts of replacement W keys, and missed kills.

5 Comments

Alicorn TwilightNov 29, 20163 votes

The bug was that if you cast Q then W, the W would trigger before Q completed its movement. The patch changed it to wait until the ball gets to its destination, which is consistent with how other input buffering works.

MinaZer0Nov 29, 20161 votes

read the patch notes that I posted. That isn't what was reverted.

MiraweaveNov 29, 20162 votes

[{quoted}](name=ILittle IMonster,realm=NA,application-id=3ErqAdtq,discussion-id=4HeHBxKi,comment-id=00000000,timestamp=2016-11-29T01:42:41.623+0000)

read the patch notes that I posted. That isn't what was reverted.

Yes it is.

MiraweaveNov 29, 20161 votes

They didn't take off the buffering. They fixed a bug where it would finish casting before Q actually finished moving.

It still works like it has for the last three years.

MinaZer0Nov 29, 20161 votes

The patch notes says nothjng about that.. you guys realize those two are completely different things.. right..? You wouldnt allow a bug as that, they are talking about the pressing Q then W and the W then lands on target and activates instantly or buffering, the Q moves to the location and then lands THEN you have to press W, if that is what the patch notes are MEANING by talking about a seperate 'bug'. Then it isnt described for that particular scenario, why would they word it as that if they meant something else?