I'm going off of what Maelwys says he's experienced.I do not see anytihng mentioned abouts word oath having an increased enmity component to it in the tooltip, nor in any of the patch notes.
Are you sure you are not mistaking the fact that Sowrd Oath Paladin's damage isn't reduced and thus, its threat gen is greater than Shield Oath Paladin?
At least in 2.0 this was the case, 2.1 I don't believe this applies anymore.
Because with the patch 2.1, the enmity buff that was applied to Shield Oath was ALSO applied to Sword Oath.
I realise Sword Oath wasn't flagged as such in the patch notes, but this increase has been noticed and demonstrated pretty thoroughly by myself and others.
Prior to the patch, a PLD using the RoH rotation in Sword Oath generated slightly more threat than the same PLD in Shield Oath, and this is STILL the case after the patch. The only difference is with Flash - because Flash has no damage component, Shield Oath is better for generating AoE threat.
I actually had a genuine encounter where this issue cropped up on Monday when clearing Turn 4 - the other PLD was ripping threat off me on the Phase 3 Dreadnaught, despite being slightly lesser-geared and using exactly the same rotation. The difference? I was MTing in Shield Oath, he was DDing in Sword Oath.
The same threat multiplier does NOT appear to be in effect (or at least not to the same degree!) when no Stance buff is active, which would be the case whenever a WAR disables Defiance.
A War naturally generates higher ST damage on a target than a PLD does, but this is primarily due to the Storm's Eye debuff (which WARS inflict, but which also affects PLD's attack damage). If both tanks are focussing on the same target, it's pretty even with equal-gearing.
Odd.
I've had the opposite scenario.
I've been seeing Paladin in Shield Oath being equal to or greater than that of a Paladin in sword oath during t2.
Wasn't seeing them creep up in terms of agro like they used to.
Is there a way to see the actual enmity numbers?
Flash (and to a lesser extent Spirits Within) were used way back to get raw enmity comparisons between two tanks - it's how we figured out something was wrong with Lalafel threat. But if you want to compare threat generation between Oaths it'd probably be better to have two tanks equip equal gear/stats (raw AF and a level one sword is useful) and use the same potency ability (e.g. "Fast Blade") a set number of times to test the raw enmity... and then an enmity-multiplier combo (like Fast Blade-Savage Blade) to test the multipliers. Unfortunately this method will not be as reliable due to random damage variance, so the sample size would probably have to be quite large.
Also, I noticed in testing Cover mechanics that there is a discrepancy sometimes in WHEN you triggered your Oath. If one PLD has Shield Oath up BEFORE going into a new instance, and another PLD puts their Oath up AFTERWARDS then it may also make a difference (sounds stupid I know, but it happens with Cover).
My suspicions are that both Oaths generate roughly the same level of raw threat on each swing and weaponskill, but the more frequent Autoattacks in Sword Oath put it slightly ahead.
Last edited by Maelwys; 01-03-2014 at 06:27 PM.
Sorry had 75 characters over the limit so I snipped you.
Thats what we did during t2.
My gear is roughly equal to the other Paladin's. (his shield was better and his gloves).
But the enmity generation for him was lesser, he wasn't generating the same amount or coming close to it.
He always dropped further and further away.
Of course judging from the other posts, he hadn't swapped from shield oath to sword oath.
|
![]() |
![]() |
![]() |
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.