Paladin Cover Exploit - something needs to be done!

[punki]

First up an explanation for everyone who isn't aware of whats going on lately in Frontlines

Paladins have the option to Cover people and making them immune to every way of being interrupted while still being able to interact with hotspots.
This means that in Frontlines like Osnal Hakkair two premade people can win an entire match on their own while the rest just stands there and just has to take it.

Imagine it like this:
There is a big fight over a flag, Team Yellow with 15 people against Team Red with 20 people, Team Blue comes in with a Paladin and a random other player, the Paladin simply uses all of his cooldowns including Guard, Covers the other random blue player and they can simply take the flag before anyone can really realize or even do something about it, since the duration of Cover is way more than enough to get the job done.

Sure, you can now say that Monk for example might have a way to counter this play, but lets be real here. Until the Monk even notices whats going on, the time to counter the play is already over.

This gameplay exploit gives way to much of an advantage by almost no risk involved at all. Some might call it "clever use of gameplay mechanics".. you will call it that until you lose 7 matches in a row to that crap.

Something needs to be done about this, change Cover that you cant interact with hotspots while being covered, there is no need to be able to do this in the first place.

Some people might now complain that i spread the knowledge about this even more, but thats exactly what i want, more people to complain about it, spread the awareness that Square Enix starts to notice the issue and does something about it

[Nikoto]

It's a known issue, will probably be fixed. There's like two other threads recently on this. One was bumped just yesterday.

[Deveryn]

Now it's well known and there's more of a tendency to try and fight cheese with cheese.

[Cidel]

If you took the time to look only like 6 threads down on the PvP boards, you'd see this issue already has a couple threads and discussion.

https://forum.square-enix.com/ffxiv/...n-Onsal-Hakkar
https://forum.square-enix.com/ffxiv/...sal-Hakair-Map

[tsuchii]

Fight fire with fire. Get into the strat too.
It's not an exploit if the ability is built that way.
Git gud and counter it. Warrior pull, dancer and reaper fear, kill the guardian pally asap etc.

[Yukimin]

Git gud.

This. Enough said.

[Mandudez]

Fight fire with fire. Get into the strat too.
It's not an exploit if the ability is built that way.
Git gud and counter it. Warrior pull, dancer and reaper fear, kill the guardian pally asap etc.

It's an accepted bug. That is literally the definition of exploit lol...

[Garten]

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

[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.