[{quoted}](name=Riot Reinboom,realm=NA,application-id=3ErqAdtq,discussion-id=WYciMlb1,comment-id=0059,timestamp=2015-03-07T05:37:44.156+0000)
Hi guys!
First up: I don't usually jump into the thick of things on champions. However! Sometimes a red posting will bring visibility to those who needs it. (Also sent this to someone who would be better able to handle the other issues). Thanks for the very detailed write up.
With that said... there is one of these bugs that specifically caught my eye: The blind bug. A bug like that tends to not be a bug with a champion but instead something more systemic. (Incidentally might explain why it has gone unfixed. Systemic bugs tend to hide much lower than others)
So I'm now looking into that.
And I have results. Usually sharing the details of working on a bug is blegh (unless it's a big one) but this one has some gameplay concerns and insight.
With that, some details:
> 1. In the system as written... it's not actually a bug. It's just a VERY arcane mechanic. That used to have very good reasons to be there.
Ultimatum hit outcomes (Dodge or Miss) are defined at "start attack". Like very start. Like on the client before you even start to see the windup frame.
Basically the moment the server even begins to start piecing together what your attack might look like it figures out whether or not it will hit.
This means when you "launch attack" (actually have the attack committed after the initial windup / when the missile is created for most ranged characters), it's already been determined awhile ago whether or not it will miss.
There's actually very good reasons to do this. You can't "cheat" the miss by rerolling the random miss chance or the random dodge chance. It's committed to it.
But wait...
2. The expectations of the system should PROBABLY change.
Note the "random miss chance" / "random dodge chance" thing mentioned and note what's not in League anymore.
The reason why #1 exists is no longer there and there is no reason to have arcane behavior when the reason for it is gone.
But after digging into the code some more...
3. This whole thing is set really early into the whole back and forth required to do a full attack and it's super risky to change.
It's actually a hard move (for any game) to pull an expectation out from a deep stack of conditionals. That deep stack of conditionals is "there's a lot of champions and all of them attack."
What this means is that changing this will take time. Not necessarily from a coding difficulty standpoint from a double checking to make sure nothing snapped elsewhere difficulty standpoint.
It will take a bit of time to figure this out from both standpoints.
The original post was about blind - but since it sounds like exactly the same thing happening with fear, I'd be willing to bet that's your problem right there - the first likely registered as a hit around half a second before the fear, and the second was probably uncancelable.
