Red Mages need some love

[Dualgunner]

Personally I consider Impact a useless ability and a waste of slot, since realistically speaking you'd rather not use it unless you want to keep your mana to a certian point, but even so I'd rather it overtake jolt II on the bar, but who knows maybe in the expansion there'll be a complete new proc off impact and w/e.

Question for clarification, just making sure I'm not misunderstanding you: realistically you'd rather not use Impact? Everything I know about RDM is "Use Impact at the next available longcast you can, even if both fire and stone are procced." It's theoretical loss versus absolute loss-that absolute loss being if you let Impact fall off.

[Mhaeric]

Question for clarification, just making sure I'm not misunderstanding you: realistically you'd rather not use Impact? Everything I know about RDM is "Use Impact at the next available longcast you can, even if both fire and stone are procced." It's theoretical loss versus absolute loss-that absolute loss being if you let Impact fall off.

Not quite. The only time you should cast Impact if you have both Verprocs is if there's less than 8 seconds left on Impactful. Otherwise, use Impact as a proc fisher when you have 1 or no procs.

From https://www.mooglemedia.com/rdm-guide/ (bolded emphasis mine)

NEVER let Impactful fall off. Always use it to fish for another proc. If you have both Verstone and Verfire and Impactful has <8 seconds left, use Impact anyways. This will still result in a net DPS gain.

Inevitably, you will end up having to cast Jolt II at some point in the fight. Jolt II will grant you the Impactful buff, allowing you to use Impact. At first glance, Impact appears to be a “cast me instead of Jolt II” button when you run out of Verstone/fire procs. However, in most cases you’re actually going to want to prioritize Impact over Verstone/fire. Impact should be considered a “proc fisher” just like Swiftcast and be used as often as possible. Furthermore, you should NEVER let Impactful fall off. Even if you have both Verstone/fire procs up, it is still a DPS gain to use Impact. Ideally, you would want to use Verstone/fire procs until one of them falls off and then use Impact to fish for the proc that just fell off, but if you have less than 8 seconds left on Impactful, go ahead and use Impact, regardless of how many procs you have.

The coles notes Impact/verproc priority from highest to lowest is as follows, but there's a much more in depth proc fishing priority list in the guide I linked above that goes into how other abilities and balance levels interact with it:
1. If there is less than 8 seconds remaining on Impactful then cast Impact regardless of the number of procs you have.
2. If you have 1 or fewer procs, cast Impact.
3. If you have 2 procs, cast your Verproc spells until you lose one of them or Impactful is about to fall off.

[Remedi]

Question for clarification, just making sure I'm not misunderstanding you: realistically you'd rather not use Impact? Everything I know about RDM is "Use Impact at the next available longcast you can, even if both fire and stone are procced." It's theoretical loss versus absolute loss-that absolute loss being if you let Impact fall off.

I'm saying that Impact doesn't really feel good as an ability especially need it's own button, I'd rather have it take over Jolt II for the duration like Ruin IV does to RuinII.
In short I feel like something it's missing out of it

[MoroMurasaki]

I'm saying that Impact doesn't really feel good as an ability especially need it's own button, I'd rather have it take over Jolt II for the duration like Ruin IV does to RuinII.
In short I feel like something it's missing out of it

The issue with this is when Impactful is going to fall off you can potentially create some dead time where there is nothing but 5sec spells or Vercure to cast.

If you've not got any procs, don't have melee up and have used SC recently you would have to stand there waiting for Impactful to fall off. No one wants to do that. Vercure would be on the table but Jolt II does still do more damage than nothing.

[Remedi]

The issue with this is when Impactful is going to fall off you can potentially create some dead time where there is nothing but 5sec spells or Vercure to cast.

If you've not got any procs, don't have melee up and have used SC recently you would have to stand there waiting for Impactful to fall off. No one wants to do that. Vercure would be on the table but Jolt II does still do more damage than nothing.

What you mean? if you have no proc you should fire off impact anyway

[Mhaeric]

What you mean? if you have no proc you should fire off impact anyway

If Impactful has <2.5 or so seconds remaining (effectively 3 since we can't see fractions of seconds remaining) then you won't be able to get the cast off in time before the proc drops. Currently we can cast Jolt II, Verfire, or Verstone instead to account for this if we know we won't have time, but if Jolt and Impact become a single button then if we don't have either Verfire or Verstone procced we lose that option and would have to either wait that up to 3 seconds before being able to cast Jolt or resort to casting Vercure.

It's not likely to happen if casting Impact properly, since you'd need to get 100% procs for ~25s and miss casting it at the ~8s remaining mark, but it does introduce that bit of potential clunkiness.

[Remedi]

If Impactful has <2.5 or so seconds remaining (effectively 3 since we can't see fractions of seconds remaining) then you won't be able to get the cast off in time before the proc drops. Currently we can cast Jolt II, Verfire, or Verstone instead to account for this if we know we won't have time, but if Jolt and Impact become a single button then if we don't have either Verfire or Verstone procced we lose that option and would have to either wait that up to 3 seconds before being able to cast Jolt or resort to casting Vercure.

It's not likely to happen if casting Impact properly, since you'd need to get 100% procs for ~25s and miss casting it at the ~8s remaining mark, but it does introduce that bit of potential clunkiness.

I see, havent' tought of that scenario