64FYX5
If you slow down the end of the game, rein’s charge goes through our rein’s body and clips me. This is not the only time reins charge has had a bug/glitch.
I watched it. If you slow it down to 0.1 speed, you’ll see the other Rein (your Rein) stepped aside from the main path of the initial charge, which causes it to not count as a pin stick, then the server appears to self correct and pull him back (or maybe he stepped back) in the main path, but by then the charging Rein is already past him, so it only results in a bump slide instead of a pin.
In my very unprofessional guess, it’s most likely a latency/IND issue. Maybe server hiccup too (processing slowdown for whatever reason), noticed a lot of those this weekend, near end of season. But if it’s more than just a temporary server hiccup, then they definitely need to tweak the code. A couple of latency sensitive abilities have been affected since something they changed a few seasons ago, like Kiriko’s Protection Suzu. It wasn’t enough to repeatedly lower the invulnerability duration, but they also apparently changed something with the way it was being registered, so that it’s been frequently terrible with the last second usage registers for player side. It’s not just the millisecond of invulnerability either, but the entire ability’s activation (including heal). The number of times I’ve used it and had someone not get healed/protected/cleansed and die anyway has gone up significantly, and you can tell just from the sheer number of reports in here, it’s definitely become a lot more prevalent after a certain patch. The same thing goes for her Swift Step.