Nerf smite

[Divinemights]

The only saving grace with EES is it has a cooldown and it's relatively weak (only 12k compared to 18k max on smite), especially considering melee damage reduction.
But yeah nerf bravery ofc.

From my perspective as a Monk, or really as any melee job, I tend to use Guard as a preventive tool rather than a reactionary one.
For example, I often use Guard to block the initial CC and burst damage before committing to an engagement.
By the time I launch my own KO burst, I usually try to create a situation where the target does not even have a chance to use Guard.
Under those circumstances, whether Smite can break through Guard is largely irrelevant to me.

I am not trying to judge whether your view about Smite being overtuned is right or wrong.
I just want to share my thoughts on the relationship between Guard and Smite.
I believe many players treat Guard as their last resort bailout button: I'm about to die, so I press Guard.
But I don't think Guard should be treated as a gimped version of Hallowed Ground.

If you always save Guard until you are already in serious trouble, your Guard timing becomes predictable.
And under the typical NA/EU horde stampede, I find that whether Smite goes through Guard often has very little impact on the final outcome anyway.
Unless you are a tank, or have teammates ready to bail you out, once an entire group collapses on you, you are probably going to die regardless.

From a gameplay perspective, I actually think allowing Smite to go through Guard can add some diversity to Frontline.
It means Guard is not an absolute answer that you can always fall back on after getting caught.
There is more incentive to use it proactively such as to prevent the initial CC and burst, reposition, or create an opening; rather than simply holding it until your HP gets low.

At the same time, Smite gives certain jobs a way to punish someone who relies too heavily on Guard as an emergency escape.
So for me, the interesting question isn't simply whether Smite should or shouldn't break Guard. It's whether that interaction creates more meaningful decisions for both players
As a melee player, I think it can.

[VictorSpoils]

literally

they should add a second charge

[Sunhwapark]

So for me, the interesting question isn't simply whether Smite should or shouldn't break Guard. It's whether that interaction creates more meaningful decisions for both players
As a melee player, I think it can.

I agree with this sort of thought. Prior to the penetration change, there was at least a bit more consideration for when I press smite since if you smited into a shield it raises the person's chance for survival a little bit, but now I honestly just use it on cooldown whenever someone's HP is low and it's usually more than enough, unless others are babysitting the individual. I suppose on the one hand it makes the skill more easily usable by non regular pvp players, but if people are really picking swift over anything else then that's more a problem with Swift.

Though to be honest, I was under the impression that Swift was the default skill you get assigned when entering PvP zones so I just assumed that Swift is always going to be the most popular action always. Or at least, I'm sure that something was happening to me when I was crashing in my games a few months ago, my role action was being reset to something else, I wasn't playing melee DPS during that time though so I couldn't say for certain.

[Valence]

It means Guard is not an absolute answer that you can always fall back on after getting caught.

There is already tools everywhere vs guard.
And guard cracks if that wasn't enough.

Also being caught means dead in FL the majority of the time anyway, guard or no guard.

[TofuLove]

they should add a second charge

It's alright they don't read these forums anyway.

[AyaMinn]

I am going to highly disagree here. Smite helps melee gain bh faster since we cannot aoe as effective as a ranged can.

Smite is essentially just a kill confirm button and on the off chance it doesn't the follow up surely will.

If you are guarding at low hp the problem there is not in smite...

Just saying~

Love,
Aya

[ChrysOCE]

Though to be honest, I was under the impression that Swift was the default skill you get assigned when entering PvP zones so I just assumed that Swift is always going to be the most popular action always. Or at least, I'm sure that something was happening to me when I was crashing in my games a few months ago, my role action was being reset to something else, I wasn't playing melee DPS during that time though so I couldn't say for certain.

Bloodbath is the default role action. When all those (allegedly) DDoS happened, every time I logged back in, I was on bloodbath. It was infuriating.

[TofuLove]

Smite helps melee gain bh faster since we cannot aoe as effective as a ranged can.

did we just collectively forget how every job basically has on demand aoe skills that they keep adding?

sam spins around like a beyblade...

viper exists

and is ninja and dragoon really melee?

does reaper not have enough aoes?

monk has earth reply and fire reply and wind reply and that whole phoenix thing...

comeee oooon....that's a lazy arguement. melees got bh just fine when smite didn't go through guard.

Smite is essentially just a kill confirm button and on the off chance it doesn't the follow up surely will.

Well yeah, exactly, so many people have smite that you get slapped around with it silly, that if this 12k smite didn't kill you, the next one might just.
AND it gets reset ready for the next target. Come on, I know how it is.

If you are guarding at low hp the problem there is not in smite...

This is similar to the conversation that DivineMights brought up.
And we can talk about the point of guarding - sure - but i kind of think it's beside the point.
it sort of devolves the dialogue into "lol skill issue"

But I don't think Guard should be treated as a gimped version of Hallowed Ground.

Agreed, but it already isn't, and already wasn't.

It's whether that interaction creates more meaningful decisions for both players
As a melee player, I think it can.

there is no meaningful interaction between smite and guard right now - you just press smite whenever. its great.


p.s.
I will be happy if they just make it so it doesn't reset on kill/assist, but it reduced the CD on assist.
It shouldn't be a spammable omnipotent kill confirm button.

[Sunhwapark]

Bloodbath is the default role action. When all those (allegedly) DDoS happened, every time I logged back in, I was on bloodbath. It was infuriating.

Thank you for the confirmation, I remember during those times it was driving me up the walls so much that I was questioning my own sanity when I would try to queue up.

did we just collectively forget how every job basically has on demand aoe skills that they keep adding?

Clearly this means that the next buff for Smite will increase the target range to 25 yalms with a 30yalm radius while also retaining its current benefits.
Justification for this will be tied to Melee's apparent lack of AoE compared to ranged players. (I'm joking, I hope...)

[Aidorouge]

Balance was never Frontline's strong suit, and it's only gotten worse over time with Role skills where most are worthless placebos, while the remaining few determine which team walks away with the win uncontested.