The Ninja Superthread

[LordTiberiusRex]

FFXIV Version 2.45
[*]If you have a Warrior in your party and they are using Storm's Eye with any consistancy, you can drop Dancing Edge in favor of Aeolian Edge. You may also drop Dancing Edge in favor of Aeolian Edge if you have another Ninja in your party and they are using Dancing Edge with consistency.

Changed that.

Now to add some other tid-bits.


DoT effects:

DoT’s on ninjas work a little “funny” in this game. Buffs such as the Kisses and Blood for Blood directly affect DoT damage. Dancing Edge’s slashing bonus does not increase the damage of the DoT effect, regardless of if it is applied before or after DE’s application, but it does increase the damage of the application strike on skills such as Shadow Fang and Mutilate. The tick count is as follows: [(DoT Effect Duration)/3].

Disclaimer: DoT's work on a "server-wide tick." This means that while the tick count of the skill does not change, the point in the spell where it occurs at may fluctuate (e.g. first ping in Mutilate occurs at 28 seconds rather than 27 seconds). The interval between ticks stays a constant three seconds, however.

Let’s use Shadow Fang, Mutilate, and Doton as our examples below:

Shadow Fang:

The DoT effect occurs once every 3 seconds. There are six ticks. An example visual below:

200 (18s) -> 40 (15s) -> 40 (12s) -> 40 (9s) -> 40 (6s) -> 40 (3s) -> 40 (0s)

Mutilate:

The DoT effect occurs once every 3 seconds. There are 10 ticks. An example visual below:

60 (30s) -> 30 (27s) -> 30 (24s) -> 30 (21s) -> 30 (18s) -> 30 (15s) -> 30 (12s) -> 30 (9s) -> 30 (6s) -> 30 (3s) -> 30 (0s)

Doton:

The DoT effect occurs once every 3 seconds. Note: Skill has duration of 24 seconds. There are eight ticks. The Heavy effect is applied upon the first tick and lasts for three seconds after the last tick. An example visual below:

30 [Heavy on] (22s) -> 30 (19s) -> 30 (16s) -> 30 (13s) -> 30 (10s) -> 30 (7s) -> 30 (4s) -> 30 (1s) -> 0 [Heavy off] (-2s)



Another "water under the bridge" topic concerns Goad usage:

Goad!

Is what I would like to say to get my fellow party members into action as a ninja. And you can too! Just... well, you cannot Goad yourself to action. That’s why many ninjas will choose Invigorate as a cross-class skill to make up for that. This leaves us with an important question: When do you Goad?

Let’s put this into a Do, Don’t, and Please Don’t format:

Do:

- Cast Goad on a Warrior if he/she is spamming Overpower (Animation looks like an Austin Power’s karate chop with an axe that spews enough flames to make even Ifrit proud).

- Cast Goad on a Warrior after some time fighting a mob, or pulling a large mob right after you eliminate a group.

- Cast Goad on a TP-based ranged/melee class only on request from them. Any other time it is used on them would fall under the “Don’t” section.

Don’t:

- Cast Goad on a Monk, Dragoon, Bard, or Ninja if a warrior tank needs it instead. Monks and Dragoons can use Invigorate, Bards have Army’s Paeon to restore their TP, and Ninjas can cross-class into Invigorate. Additionally, Paladins won’t need to be Goaded as they can use MP-based enmity generating skills.

Please don’t:

- Cast Goad on any class that uses MP as its primary resource. Big hint for what a MP class is: Someone with a book or staff in their hands. Don’t do it; save yourself the ridicule.

[Viridiana]

Err, dot damage occurs every three seconds game time on a server-wide tick that has nothing to do with how long is left on the dot. You're just as likely to see Shadow Fang ticking at 17 or 16 seconds as at 15. Same thing with Mutilate and Doton.

[LordTiberiusRex]

Err, dot damage occurs every three seconds game time on a server-wide tick that has nothing to do with how long is left on the dot. You're just as likely to see Shadow Fang ticking at 17 or 16 seconds as at 15. Same thing with Mutilate and Doton.

Just re-tested this statement. Yep; I'll have to edit it in there. Thank you for catching that.

Nevertheless, the number of ticks that occur (i.e. DoT duration effect/3 = tick count) stays constant regardless of where it occurs at in the server-wide tick.