PVP Lag/Possible Hack Turned Up to Redonkulous Levels

Adamon2

Last night AD had the outer wall down on a keep. Team went in with about twenty players. One guy from the EP came out of the Keep and no one could hit him. Lag was tremendous. He wasn't dodge rolling or really trying to evade. We all kept firing at him to no avail. Then it got redonkulous. Right in front of us he does the /sitchair emote. Still no ones attacks could hit him. Then two more from EP came out of the Keep and began to repair the walls. No one could hit them either. Lag was still in full force. I setup a ballista to try and hit the wall to prevent repair; but, once it was setup I wouldn't let me fire it or enter it to pack up. Wall got fully repaired. All three of these guys couldn't be touched. I got screenshots of the guy sitting in the chair; but, as I understand they can't be posted with names on them due to policy. I sent a report to ZOS. The reply today said they would look into it.

I don't mind loosing to a good player; but, to loose to this was Redonkulous.

Robbmrp

What platform and server was that on? For someone to come out like that and sit down you know full well they had to be doing something to increase the lag. How else would they have known they could do that? This really needs to be investigated by @ZOS.

@ZOS_GinaBruno, @ZOS_JessicaFolsom, @ZOS_BrianWheeler how is that possible???????

This isn't the first post I've seen also, where an attacking army had lag issues so bad that the opposing enemy was able to fully repair their keep while the other army couldn't do anything except watch.

This kind of situation SHOULD NEVER HAPPEN.....

jcasini222ub17_ESO

Gotta love players are confident enough to know they might miss the banhammer to straight up /sitchair. By any chance could you black out the names? Would love to see for the absurdity.

Alcast

get used to it, lag is real

its not a hack, its Zenimaxs incapability to fix broken pvp laggin

Leandor

Alcast wrote: »

get used to it, lag is real

its not a hack, its Zenimaxs incapability to fix broken pvp laggin

Hm. How then to explain following situation?

Bleakers, red defending with a small group (I think we were 8 plus a couple of non-grouped randoms). A trio attacking, not to take the outpost only to bother us and try to gank those that could be lured out. None of us were that stupid, but the randoms went against better judgement took the bait.

Naturally, we wanted to help. So I stood on top and did the cowardly thing: Snipe from above (hey, don't judge me). All our ping ratings are fine (mine is the usual 90-something). I target one of the two sorcs down there, get my snipe off and of course he streaks away. All normal so far. I see the second sorc incoming, line up and again snipe to hit his shieldstack. As usual with any competent sorcerer, he streaked away as soon as I was close to breaking his shell.

Then I see the nightblade lining up a snipe from below, point my reticle at him and press snip. Instantly stuck in animation, I retreat back to get out of LOS, still stuck in animation, I wait... for about 25 seconds. The snipe goes off, hits the nightblade somewhere (since I was still out of LOS I didn't even see where).

Okay, let's try that again, maybe somewhere else one of the hated lagtrains did their thing. Back to front ledge, hide, look for them, find sorceror, line up, fire, all normal. The nightblade pops up again, and as soon as I have him targeted, stuck in animation again. Exact same thing happens again.

I then proceeded to scratch my head and test this in detail for about 10 minutes they were there. Conclusion: I was only stuck in animation if I had that nightblade targeted. If I cancelled the stuck animation and immediately switched over to a sorc, no issue. Back to the nightblade, stuck again.

Not once, not twice in a row, for a solid 10 Minutes of testing. I so wish I had made a video of that, sadly I didn't think of that at the time. I reported him asking for a detailed evaluation of his account, giving time, location and campaign data together with a detailed verbal description.

Seemingly, nothing has happened yet or the issue was due to some really strange star alignment, since I have seen that selfsame nightblade yesterday again. This time strangely without this happening, so something changed.

Point being, how can this behaviour be explained? There cannot be a serverside nor a clientside lag/latency issue involved, since my ping rating did not change in the slightest while I experienced this and it was with absolute 100% repeatability only happening if that specific player was targeted.

Enlighten me, please.

Robbmrp

Leandor wrote: »

Alcast wrote: »

get used to it, lag is real

its not a hack, its Zenimaxs incapability to fix broken pvp laggin

Hm. How then to explain following situation?

Bleakers, red defending with a small group (I think we were 8 plus a couple of non-grouped randoms). A trio attacking, not to take the outpost only to bother us and try to gank those that could be lured out. None of us were that stupid, but the randoms went against better judgement took the bait.

Naturally, we wanted to help. So I stood on top and did the cowardly thing: Snipe from above (hey, don't judge me). All our ping ratings are fine (mine is the usual 90-something). I target one of the two sorcs down there, get my snipe off and of course he streaks away. All normal so far. I see the second sorc incoming, line up and again snipe to hit his shieldstack. As usual with any competent sorcerer, he streaked away as soon as I was close to breaking his shell.

Then I see the nightblade lining up a snipe from below, point my reticle at him and press snip. Instantly stuck in animation, I retreat back to get out of LOS, still stuck in animation, I wait... for about 25 seconds. The snipe goes off, hits the nightblade somewhere (since I was still out of LOS I didn't even see where).

Okay, let's try that again, maybe somewhere else one of the hated lagtrains did their thing. Back to front ledge, hide, look for them, find sorceror, line up, fire, all normal. The nightblade pops up again, and as soon as I have him targeted, stuck in animation again. Exact same thing happens again.

I then proceeded to scratch my head and test this in detail for about 10 minutes they were there. Conclusion: I was only stuck in animation if I had that nightblade targeted. If I cancelled the stuck animation and immediately switched over to a sorc, no issue. Back to the nightblade, stuck again.

Not once, not twice in a row, for a solid 10 Minutes of testing. I so wish I had made a video of that, sadly I didn't think of that at the time. I reported him asking for a detailed evaluation of his account, giving time, location and campaign data together with a detailed verbal description.

Seemingly, nothing has happened yet or the issue was due to some really strange star alignment, since I have seen that selfsame nightblade yesterday again. This time strangely without this happening, so something changed.

Point being, how can this behaviour be explained? There cannot be a serverside nor a clientside lag/latency issue involved, since my ping rating did not change in the slightest while I experienced this and it was with absolute 100% repeatability only happening if that specific player was targeted.

Enlighten me, please.

It doesn't make sense that it only happened with that exact same player over and over again to be anything but some sort of a hack. IF it's not a hack, then it's specifically related to his gear. Maybe something on the back end of the system that doesn't know how to calculate damage of some sort so it "freezes" the one doing the damage. Even that's a long shot. This is very suspicious indeed. I really hope that @ZOS takes a look at that person's setup.

cozmon3c_ESO

Wow, if this NB was on NA server a week ago, he's the one who made me rage quit. I thought it was ZOS incompetence with wrecking blow. I tried to hit said NB 15 time but WB would just stutter stop even though I was directly on target. He killed me so I went back, and same thing happened again 15 WB stutter stopping on this NB while directly lined up. Died again, rage quit and haven't been in pvp since that night.

Either way I'm pissed, whether the dude is hacking or zoo's neglect of the pc version is so f'ed there is no point in playing til they fix it.

OdinForge

This happens on PC a lot, when many players converge on one keep and AoE / ulti spam until the server gives up on life.

You can sit in a raid of people trying to kill you, and nothing will happen.

kkravaritieb17_ESO

Get used to it...no hacks...just crappy coding from ZoS's side.

Leandor

OdinForge wrote: »

This happens on PC a lot, when many players converge on one keep and AoE / ulti spam until the server gives up on life.

You can sit in a raid of people trying to kill you, and nothing will happen.

Please re-read my description. That was in a scenario where there was no realm lag (less than 100ms ping rating), with approx 8 players on our side and three attackers, without blob and healing springs or ultimate spam.

cozmon3c_ESO wrote: »

Wow, if this NB was on NA server a week ago, he's the one who made me rage quit. I thought it was ZOS incompetence with wrecking blow. I tried to hit said NB 15 time but WB would just stutter stop even though I was directly on target. He killed me so I went back, and same thing happened again 15 WB stutter stopping on this NB while directly lined up. Died again, rage quit and haven't been in pvp since that night.

Either way I'm pissed, whether the dude is hacking or zoo's neglect of the pc version is so f'ed there is no point in playing til they fix it.

No, this was on EU servers. But I am pretty sure that this is something that more than one player uses, since I have had it on other occasions as well, only not in such a well suited for tests situation. It only happens if you use a cast-time ability (instant casts work fine) but since those are the ones that usually hurt with a capital H, it makes sense. Also, the damage is not negated, only postponed, but that gives exactly these few seconds to recover/heal up for it to not result in death.

SturgeHammer

Adamon2 wrote: »

I setup a ballista to try and hit the wall to prevent repair; but, once it was setup I wouldn't let me fire it or enter it to pack it up.

I don't know about any of that other stuff, but I know that the inoperable siege bug is one of the most frustrating thing in the game. The only way I have found to work around this is to Not Move once you click to setup up the siege. Don't take a single step, activate any abilities, or as I've been doing lately don't even rotate the camera until the siege is in place and you have the targeting arc on screen. It'll still happen occasionally if the lag is really bad, but it will greatly reduce the number of siege weapons wasted. Also, place even more distance between you and your target than your normally would to lessen you chance of getting interrupted by an enemy.