Results 1 to 7 of 7
  1. #1
    Player
    JohnnyDevo's Avatar
    Join Date
    Jun 2016
    Posts
    190
    Character
    J'majha Devo
    World
    Midgardsormr
    Main Class
    Red Mage Lv 80

    Red Mage: Some quality of life (or lack thereof) quirk that raiders will want to know

    If anyone has been doing any theorycrafting about red mage, they know that the pull countdown of red mage will consist of using acceleration and hard-casting thunder/aero at 5s to hit on pull, followed by using the dualcast to immediately cast the other.

    https://youtu.be/NwQE4g-2tuM?t=1m24s

    However, from the linked video bookmark, you can see something else happening. The player is hardcasting a verthunder and queueing up veraero. Consequently, veraero begins to cast before the server catches up with the dualcast proc.

    In addition, at 0:55 of the same video, you can see it work the opposite way. The player is hard-casting veraero and queuing up another veraero, and both cast immediately as would be expected.

    This may or may not be a bug, but it's something to be aware of. My suggestion is to not queue up the spell and tap the button when you see the cast bar finish, but the timing might need a little practice.

    Thoughts?
    (0)

  2. #2
    Player
    Antwan's Avatar
    Join Date
    Jan 2015
    Location
    Ul'Dah
    Posts
    40
    Character
    Antonar Avanti
    World
    Famfrit
    Main Class
    Scholar Lv 70
    That doesn't look like something that would have been intentional, at least from he dev's perspective. Queuing your next move is something all of us do and if the dualcast proc doesn't go off quickly enough we do end up in a situation where we're attempting to proc both mana spells (VerFire and VerStone) using dualcast procs only to be rather screwed when the server doesn't register it quick enough. Though we wouldn't be doing this because I believe you should be using Jolt/Jolt II for Dualcast procs, not the 4 second long spells.

    I don't know how everyone else feels about this but if you also notice when the RDM casts VerThunder at 1:25 the VerFire proc doesn't happen until a split second or so after the VerThunder cast. This reminds me of pre-buff MCH where we had to guess whether we got a proc or not. I hope this are issues just within the test build and won't show up in the actual game, it already gimps RDM quite a bit.
    (1)

  3. #3
    Player
    Anastacy's Avatar
    Join Date
    Jun 2015
    Posts
    39
    Character
    Vyndrian Larethil
    World
    Coeurl
    Main Class
    Conjurer Lv 70
    Was he auto-attacking?
    (0)

  4. #4
    Player
    JohnnyDevo's Avatar
    Join Date
    Jun 2016
    Posts
    190
    Character
    J'majha Devo
    World
    Midgardsormr
    Main Class
    Red Mage Lv 80
    Quote Originally Posted by Antwan View Post
    -snip-
    It's entirely correct that you use jolt/impact/stone/fire normally to get your dualcast procs. The play in the video is actually quite bad. It just brings up the fact that if you hardcast an aero into a thunder or similar situation, such as on pull, there's a chance server delay will mess that up. Otherwise, the flow works just fine due to the 2s cast of the other spells to the 2.5s gcd.

    Quote Originally Posted by Anastacy View Post
    Was he auto-attacking?
    If you watch the video, you'll notice that dualcast is still on his buffs bar while he's casting veraero, and the subsequent verfire that happens right after ends up consuming the dualcast proc and casts instantly. There was no autoattack damage. This is definitely an issue with server delay and spell queues.
    (0)

  5. #5
    Player
    Anastacy's Avatar
    Join Date
    Jun 2015
    Posts
    39
    Character
    Vyndrian Larethil
    World
    Coeurl
    Main Class
    Conjurer Lv 70
    Quote Originally Posted by JohnnyDevo View Post
    If you watch the video, you'll notice that dualcast is still on his buffs bar while he's casting veraero, and the subsequent verfire that happens right after ends up consuming the dualcast proc and casts instantly. There was no autoattack damage. This is definitely an issue with server delay and spell queues.
    I did watch. Sadly, I can't get perfect quality on my phone. Just saw that he was very close to the boss.
    (0)

  6. #6
    Player
    Antwan's Avatar
    Join Date
    Jan 2015
    Location
    Ul'Dah
    Posts
    40
    Character
    Antonar Avanti
    World
    Famfrit
    Main Class
    Scholar Lv 70
    Quote Originally Posted by JohnnyDevo View Post
    It's entirely correct that you use jolt/impact/stone/fire normally to get your dualcast procs. The play in the video is actually quite bad. It just brings up the fact that if you hardcast an aero into a thunder or similar situation, such as on pull, there's a chance server delay will mess that up. Otherwise, the flow works just fine due to the 2s cast of the other spells to the 2.5s gcd.
    I assume that's fine when it comes to the casts of the 2 second spells in comparison to the 2.5 GCD, but then that means that you wouldn't have a problem whatsoever right? I don't think there's any situation where you would want to hardcast the 4 second spells instead of using Jolt II for the Dualcast
    (0)

  7. #7
    Player
    JohnnyDevo's Avatar
    Join Date
    Jun 2016
    Posts
    190
    Character
    J'majha Devo
    World
    Midgardsormr
    Main Class
    Red Mage Lv 80
    Quote Originally Posted by Antwan View Post
    I assume that's fine when it comes to the casts of the 2 second spells in comparison to the 2.5 GCD, but then that means that you wouldn't have a problem whatsoever right? I don't think there's any situation where you would want to hardcast the 4 second spells instead of using Jolt II for the Dualcast
    Well, as I said in the OP, there is one situation where you want to. On pull, you start casting one of the spells when the countdown hits 5 seconds so that it'll hit on pull, then ideally you want to immediately use the dualcast proc on the other spell. It's strong opening burst and a small lead in mana generation, as well as proc generation.
    (0)