Paladins Invuln Capping in Onsal Hakkar

[Naphtha]

Why does he keep saying SINGLE node as if the people doing the exploit only have 1 charge of Hallowed Ground? It's a limit break combined with a what, 20s CD skill? You can basically get a node on every spawn cycle under the right conditions, if that doesn't drastically improve your odds of winning then I don't know what would.

But yeah I guess if you massacre the team doing this exploit repeatedly for 10 minutes you would easily win, just win guys, it's not hard.

[Garten]

Why does he keep saying SINGLE node as if the people doing the exploit only have 1 charge of Hallowed Ground? It's a limit break combined with a what, 20s CD skill? You can basically get a node on every spawn cycle under the right conditions, if that doesn't drastically improve your odds of winning then I don't know what would.

But yeah I guess if you massacre the team doing this exploit repeatedly for 10 minutes you would easily win, just win guys, it's not hard.

Exactly this, did a match the other day where 2 PLD capped at least 4 A ranks. Honestly they lost but only because our team let the 3rd one win out of spite

[Gserpent]

Exactly this, did a match the other day where 2 PLD capped at least 4 A ranks. Honestly they lost but only because our team let the 3rd one win out of spite

They can't be everywhere at once. 4 A ranks is 400 points out of 1600. That's not really much of anything.

[Xylira]

They can't be everywhere at once. 4 A ranks is 400 points out of 1600. That's not really much of anything.

It is when they're capping nodes their team otherwise would have had zero ability to cap because of spawn location and the presence of enemy teams. I've seen teams that were otherwise outmatched still win because of this being repeatedly exploited to steal nodes by even just two of their players. The most egregious of times was in the middle of the entirety of my team slugging it out with the entirety of one of the other teams over an S rank, and then two players from the third team run in and abuse this horribly broken mechanic to steal the node from under 48 enemy players.

This is very clearly not balanced and needs to be corrected ASAP. Two players should not be able to abuse a mechanic to cap unimpeded like this. Yes there are counters in the form of limit breaks on a small number of classes, but having to rely on happening to be the right class at the right time with your limit break left available specifically to counter this is not reasonable or reliable enough for how easy it is to pull off this nonsense. Which is especially true if it's a pair of paladins doing it because they just swap who caps and who guards immediately after and you can't stop them because you've already blown your limit break.

[Gserpent]

It is when they're capping nodes their team otherwise would have had zero ability to cap because of spawn location and the presence of enemy teams. I've seen teams that were otherwise outmatched still win because of this being repeatedly exploited to steal nodes by even just two of their players. The most egregious of times was in the middle of the entirety of my team slugging it out with the entirety of one of the other teams over an S rank, and then two players from the third team run in and abuse this horribly broken mechanic to steal the node from under 48 enemy players.

This is very clearly not balanced and needs to be corrected ASAP. Two players should not be able to abuse a mechanic to cap unimpeded like this. Yes there are counters in the form of limit breaks on a small number of classes, but having to rely on happening to be the right class at the right time with your limit break left available specifically to counter this is not reasonable or reliable enough for how easy it is to pull off this nonsense. Which is especially true if it's a pair of paladins doing it because they just swap who caps and who guards immediately after and you can't stop them because you've already blown your limit break.

10 sec of invuln isn't enough time to run up to a node from outside of attack range and capture it.

If your team is letting them that close to the node *before* engaging them, you have a different problem you should focus on rectifying first, before complaining about some dumb cheese.

[Xylira]

10 sec of invuln isn't enough time to run up to a node from outside of attack range and capture it.

If your team is letting them that close to the node *before* engaging them, you have a different problem you should focus on rectifying first, before complaining about some dumb cheese.

Nice try attempting to move the goal posts to avoid the issue. In many cases you don't even need to pop your invuln before even getting to the node with how tanky paladin is. Even if you would have to pop invuln beforehand, you can still take a beating on the way to the node before going invuln and get about 4 seconds of invuln travel time to get to the node and start capping to abuse this nonsense because of how long the invuln is and how short the cap time is comparatively.

It's very obviously unintended and unbalanced design, very likely because SE seems to have put in virtually no effort into trying to balance any of the pvp changes for Frontlines. It's honestly pretty laughable that anyone would actually attempt to defend this as being 'intended and balanced', unless of course they're trying to cover for their own abuse of it, or they're just trying to be contrarian.

[Gserpent]

Nice try attempting to move the goal posts to avoid the issue. In many cases you don't even need to pop your invuln before even getting to the node with how tanky paladin is. Even if you would have to pop invuln beforehand, you can still take a beating on the way to the node before going invuln and get about 4 seconds of invuln travel time to get to the node and start capping to abuse this nonsense because of how long the invuln is and how short the cap time is comparatively.

It's very obviously unintended and unbalanced design, very likely because SE seems to have put in virtually no effort into trying to balance any of the pvp changes for Frontlines. It's honestly pretty laughable that anyone would actually attempt to defend this as being 'intended and balanced', unless of course they're trying to cover for their own abuse of it, or they're just trying to be contrarian.

That isn't moving the goalposts, it is directly responding to your claims. You may want to look up the precise definition of "moving the goalposts," because you misunderstand it.

If your team is letting a PLD, or even a pair of PLD, just walk up to the node without CC chaining them, pushing them back, slowing them, or otherwise killing them... that's on you, dude. If you force them to pop invuln 40 yards out, they won't have enough invuln left to cap the point before you can stun them again.

It is a problem, but not one nearly to the magnitude you portray it as. As with so many complaints here, there's a lot of PEBKAC stuff that needs to be addressed.

[Nanne]

It's very obviously unintended and unbalanced design

It is literally the same interaction it had for years when Cover was in PvP before it got taken out