I totally dominate this spark runner right? That is.... until he scores by igniting our rift... while I'm shooting him in the head repeatedly.
This is why matchmaking needs fixed.
EDIT: It's obvious there are some really incredible network engineers in this thread who weren't in the game, didn't see anything before or after the clip and yet know exactly what happened. Some are saying that the guy lagged out of the game since it said so in the bottom left of the screen. I can see that, HOWEVER if he didn't ignite the rift, which was ALSO ON THE SCREEN, then why did the game report that he did? Others are saying the score didn't reflect the rift being ignited, well it doesn't in this clip, but haven't you ever gotten a kill but didn't get credited with it for 5 or more seconds?
In the end, it really doesn't matter whether it was player induced lag or a terrible result of the current matchmaking model, IT STILL NEEDS FIXED.
-
1 AntwortenBearbeitet von ashesofman: 1/27/2016 1:07:20 PMIt looks like a lagswitch or an attempted but failed lagswitch to me. People used to do that in Dark Souls II. They'd be frozen and invincible and you'd assume they'd lagged out, but then they would all of a sudden teleport and kill you extremely rapidly. Some people did it habitually, so you knew it was coming as soon as they invaded you.