Paladin Cover Exploit - something needs to be done!

[Xylira]

I did a match today where i saw a dancer lb and a reaper lb not working. In another One i was a Warrior and in One oovoo i tried puling the covering tank, that did not work too.. (i tried going farther than 10 yalms but apparently the game did not recongnize the distance in time?).
I challenge everyone to post a video on a working counter to this strategy.
The only two that i found so far are:
-doing the same
-killing/stopping all pld while they are still far from node

Guardian transfers all CC effects to the paladin doing the covering, so the Dancer and Reaper LB do literally nothing to interrupt the person capping since it just transfers to the Paladin. Which actually kind of proves that this is an exploit given that guardian's tooltip clearly states that only damage is supposed to transfer to the paladin. What it does do however, is break the paladin's guard, which at most lets another player on a monk or warrior try to move the paladin far enough away from the person they're covering that's capping the point.

While it is technically possible to counter by coordinating with all the right players on your team with all the right jobs, with limit breaks ready and CC skills off cooldown at the right time to be able to guard break, then move the paladin far enough away, and then to interrupt the capper all in the span of the 5 seconds it takes to cap, it's absolutely not realistically feasible. This is especially true when you add the game's crappy netcode and server tick rate making the near perfect timing required to interrupt this tactic even harder to pull off. It technically can be done, I've actually had it happen as a fluke before, but it's so incredibly difficult pull off intentionally as a coordinated effort that it might as well be considered impossible, never mind it ever being anything near a reliable counter.

As for ways to play against it, the only somewhat effective method I've found is to play absolutely obnoxiously on a warrior to harass known Paladin cap coverers as much as possible before they even get close to any points.

[Garten]

Guardian transfers all CC effects to the paladin doing the covering, so the Dancer and Reaper LB do literally nothing to interrupt the person capping since it just transfers to the Paladin. Which actually kind of proves that this is an exploit given that guardian's tooltip clearly states that only damage is supposed to transfer to the paladin. What it does do however, is break the paladin's guard, which at most lets another player on a monk or warrior try to move the paladin far enough away from the person they're covering that's capping the point.

While it is technically possible to counter by coordinating with all the right players on your team with all the right jobs, with limit breaks ready and CC skills off cooldown at the right time to be able to guard break, then move the paladin far enough away, and then to interrupt the capper all in the span of the 5 seconds it takes to cap, it's absolutely not realistically feasible. This is especially true when you add the game's crappy netcode and server tick rate making the near perfect timing required to interrupt this tactic even harder to pull off. It technically can be done, I've actually had it happen as a fluke before, but it's so incredibly difficult pull off intentionally as a coordinated effort that it might as well be considered impossible, never mind it ever being anything near a reliable counter.

As for ways to play against it, the only somewhat effective method I've found is to play absolutely obnoxiously on a warrior to harass known Paladin cap coverers as much as possible before they even get close to any points.

Tnx i didnt know that. So yes.. or the tooltip on pld is wrong or it is a bug.

[Karasio]

Instead of defending this shit or going "HURR DURR DO THE SAME" maybe SE should do PvP patches more often because this is probably not the intended way to use the ability LMAO

[Deveryn]

Instead of defending this shit or going "HURR DURR DO THE SAME" maybe SE should do PvP patches more often because this is probably not the intended way to use the ability LMAO

It's not really being defended. We're just encouraging people to take initiative instead of giving up. It would've been nice to see an update or hotfix, but it apparently wasn't a big enough issue from their perspective.

I was in a run yesterday and we were up against around 10 PLD on an opposing team. My team just kept on fighting these people without trying to match the cheese and we eventually got the win. It's clearly not an unbeatable strat.

[ShaiPie]

Reworking Frontline was on the timeline for after Rival Wings was it not? Honestly the easiest fix for this IMHO is to remove Onsal Hakair and Seal Rock for now That way square doesn't have to think about how to balance pvp for Crystalline Conflict and also older content that doesn't work with the new PVP design philosophy.

Until SE takes some sort of formal action I guess report people you see doing it for Nuisance Behavior. The people who are doing this in Frontline matches know that this is obstructing normal gameplay.

[NightHour]

Just make it so you cannot capture a point while under the effects of Cover.

[ShaiPie]

After speaking with someone who was doing this it seems people are pointing to a reddit article in which a GM states "the ability is working as intended". Though the reddit article doesn't show the question that was asked of the GM, nor does the answer from the GM indicated that the way that Guardian interacts with Ovoos is working as intended.

I opened a ticked and the response I got was not one of "working as intended" but that they would be investigating further.

In other words, don't use the random reddit post as justification for using this.

If SE doesn't think that the issue is "bad enough" to warrant a response, the only way to get eyes on it is to report for nuisance behavior when you see it happening IMHO. If there's enough reporting around it, then maybe someone at SE will take notice.

[Divinemights]

I opened a ticked and the response I got was not one of "working as intended" but that they would be investigating further.
In other words, don't use the random reddit post as justification for using this.

If SE doesn't think that the issue is "bad enough" to warrant a response, the only way to get eyes on it is to report for nuisance behavior when you see it happening IMHO. If there's enough reporting around it, then maybe someone at SE will take notice.

That Reddit post has solid evidence to back it up
Japanese player has reported it as a bug on May 2022 and that report is now sitting at working as intended section
Just FYI, “we will investigate further” is just a generic phase customer service would use on something they are not sure, it literally means nothing

[Deveryn]

It's sad. You can literally fight back against this, but snitching continues to come up as the response. Maybe PvP isn't for you.

Still... Tuesday might find us free of this cheese.

[Towa-Musa]

It's sad. You can literally fight back against this, but snitching continues to come up as the response. Maybe PvP isn't for you.

Still... Tuesday might find us free of this cheese.

The fact you used the word 'Snitching' makes me lead to believe that you KNOW this is a exploit but you continue to defend it.