Swiftcast + Ruin II

[MyraOriales]

If you swiftcast then Scathe, it will consume it. Fire III has its own proc that is consumed instead of Swiftcast. Abilities are not spells. They aren't what swiftcast is looking for.

Firestarter isn't an ability, it's a trait that modifies the Fire 3 spell to be an instant cast if it procs. You can't put Firestarter on your hotbar.

That Firestarter procs on the Fire 3 spell don't consume Swiftcast because they're instant cast already is still inconsistent, because the same doesn't apply to spells like Ruin 2 or Bio, which have instant cast built in.

It's a mistake to focus on people screwing up by accidentally Swiftcasting an instant cast spell. If all instant cast spells had the same behaviour as Firestarter or Thundercloud, you would have more options for casting while moving, so it would allow for smart play. Basically, Firestarter or Thundercloud offer an advantage based on inconsistent Swiftcast behaviour. I would guess that it would be helpful for SMN to weave oGCDs as well, but I am better acquainted with BLM.

(That said - SMN is also pretty well equipped for casting while moving, so it's likely that this feature is intentional to support BLM mobility if you're lucky with procs or planned a proc using Sharpcast.)

[Rawrz]

Firestarter isn't an ability, it's a trait that modifies the Fire 3 spell to be an instant cast if it procs. You can't put Firestarter on your hotbar.

That Firestarter procs on the Fire 3 spell don't consume Swiftcast because they're instant cast already is still inconsistent, because the same doesn't apply to spells like Ruin 2 or Bio, which have instant cast built in.

It's a mistake to focus on people screwing up by accidentally Swiftcasting an instant cast spell. If all instant cast spells had the same behaviour as Firestarter or Thundercloud, you would have more options for casting while moving, so it would allow for smart play. Basically, Firestarter or Thundercloud offer an advantage based on inconsistent Swiftcast behaviour. I would guess that it would be helpful for SMN to weave oGCDs as well, but I am better acquainted with BLM.

(That said - SMN is also pretty well equipped for casting while moving, so it's likely that this feature is intentional to support BLM mobility if you're lucky with procs or planned a proc using Sharpcast.)

I don't think you understood what I was saying about fire starter. I never said it was an ability, I was saying that abilities won't consume it and that the Firestarter trait (as well as thunder cloud) are exceptions through procs that are consumed to make them instant. I was saying that because it had a proc already, swiftcast would not be consumed. Spells that are inherently instant cast will trigger swiftcast just the same.

Does it limit choice like it is? Yeah, but it's acceptable like it is.

[MyraOriales]

I don't think you understood what I was saying about fire starter. I never said it was an ability, I was saying that abilities won't consume it and that the Firestarter trait (as well as thunder cloud) are exceptions through procs that are consumed to make them instant. I was saying that because it had a proc already, swiftcast would not be consumed. Spells that are inherently instant cast will trigger swiftcast just the same.

Does it limit choice like it is? Yeah, but it's acceptable like it is.

Patronising "I don't think you understand" gambit aside, the details of what you're saying are correct, but the point is that Fire 3 is still a spell even it is proc'd and the fact that the proc overrides Swiftcast isn't explained anywhere, so it's still inconsistent behaviour. Whether it's acceptable or not is a different topic.

[Brindyr]

I've been thinking about it.
If a spell is an instant spell, it shoud be consuming swiftcast effect?

Firestarter trait says "no cast time" and swiftcast effect is not consumed when a fire 3 with proc ative is cast.

Swiftcast says "next spell is cast immediatly", but for instant spells wich are cast with no cast time swiftcast is consumed.

For me its not clear the difference between "instant", "immediatly" and "no cast time".

For me the behavior for those would be the same.

Is it an issue?