Paladins Invuln Capping in Onsal Hakkar

[InkB]

It would be so easy to fix too. Just change Cover to prevent 99% of damage. The 1% would stop the node capping and the covered target would still pretty much take no damage. You'd just lose on the ability to potion while covered but that's kind of a weird design.

Its not even that. Sage LB makes you take 100% less damage (its worded "negates all damage"), but you still take 0 damage that will interrupt your flag capture.

Its how cover is coded to transfer all damage instead of making you take 100% less. You are literally unable to take even 0 damage by press of a single button every 25 seconds (nodes last 30 seconds so its always up for next ones)

But im just nitpicking, your suggestion would work. You could make it so that target takes 100% less damage, but still "takes 0" so it would interrupt casts that you probably arent meant to use middle of brawl.

[Brill_]

FWIW, it's possible to be bad at PLD cheese. Last time we had Onsal(friday, I think). Red node spawns mid in the first group of nodes. People fought over that thing for almost half the match before someone finally claimed it.

[Rueby]

I'm going to bump this because the point of the mode according to my understanding: kill others, capture flag and not like 'fight and have a sneaky rat and his friend capture the flag under the noses of perhaps 24 people when most classes don't have sufficient counter and goodluck killing a PLD before his friend finishes interacting. Play X class to counter this play; no thanks. It might work in CC where there's some measure of visibility but in frontline when there's a literal pile on the ovoo, good luck spotting the PLD before it's too late. It's annoying, disheartening, and even when I switched to warrior and did my best to counter it- It wasn't fun. I got no joy out of it and I doubt the dude enjoyed getting focused all the game because you know I'm putting a mark on him.

I briefly enjoyed the new pvp because I previously felt like if I didn't play WHM then I'm helpless. Healing others was my way of like 'minimizing potential deaths/point loss'. I didn't enjoy that playstyle but I did it for the achievements. The new rework made it more like 'welp you can't do shit so focus on your own thing' which was nice. It made me try other classes and actually have a measure of fun without feeling like I must play a certain job to counter something or minimize potential rips.

Please make it so if you get hit your interact gets cancelled. That's all.

[jaytabox]

Bumping it too.


I seriously wonder if this information is reaching the devs in JP, the ones who can do something about it (and for which Yoshi P has asked english Youtube content creators to activate JP auto translate in their videos for). Because I feel US/EU threads are mostly taken care of US/EU community managers, who as long as they don't get a PM stating "this thing is a bug/an exploit", will always classify this as "working as intended". Which isn't bad per se, but for some things I think the dev team should take a more direct stance about.



I wish we could get direct information from the dev team in a LL or a special post in Lodestone. They've started giving more info in regards to job balance changes, would be nice to do so with controversial (to say the least) job abilities too.

[GordonGeeko]

What really bothers me is that they'll fix some weird thing that barely affects anyone, but not the PLD cheese.

Like you look at hotfixes and it's stuff like :

An issue when playing as paladin in PvP wherein the healing effect of Confiteor was affected by opponent's status effects.

And it's like: Ok, you fix these insignificant things, but not the PLD cheese. Really ?

[Sidamel]

It has always been like that...

[Genz]

onsal day bump

(i'd be ashamed to make a game and let this kind of shit rot for months)

[Genz]

[Kuroka]

So now imma post here every 3 days after premades of Pala and ranged or reaper stomped us with little to no chance..

FIX IT its been weeks...

[Xylira]

It hasn't just been weeks, it's been months now. SE needs to at the very least make a statement about the issue.

Even if it's coming out and stating that they think this is 'intended gameplay', fine, then at least we can have confirmation that they have no clue what they're doing.