Results 1 to 7 of 7

Hybrid View

  1. #1
    Player
    Capn_Goggles's Avatar
    Join Date
    Jul 2017
    Posts
    175
    Character
    Yuri Goggles
    World
    Ultros
    Main Class
    Botanist Lv 80
    I don't know people are TRYING to weave 2x between heat blast. It's on a 1.5 second GCD and you get three charges of gauss round and ricochet; since WF isn't affected by oGCD abilities I see literally no reason to double-weave them during a 1.5 GCD burst window. The ping issue arises from the fact that both wildfire and hypercharge carry animation locks, have desynced durations, yet are entirely co-dependent and have fairly tight windows. The other issue with increasing WF duration and capping the damage is that it makes it far too easy for low ping players to comfortably do anything they want in that window, making it super easy.

    The best solution imo would be to have WF auto-trigger hypercharge if it's available since they're CLEARLY designed to go together, and further reduce (or eliminate entirely) the animation lock associated with it so you don't have that awkward delay.
    (1)

  2. #2
    Player
    CKNovel's Avatar
    Join Date
    Aug 2019
    Posts
    1,915
    Character
    Cassia Kaedhan
    World
    Ragnarok
    Main Class
    Gunbreaker Lv 100
    Quote Originally Posted by Capn_Goggles View Post
    I don't know people are TRYING to weave 2x between heat blast. It's on a 1.5 second GCD and you get three charges of gauss round and ricochet; since WF isn't affected by oGCD abilities I see literally no reason to double-weave them during a 1.5 GCD burst window. The ping issue arises from the fact that both wildfire and hypercharge carry animation locks, have desynced durations, yet are entirely co-dependent and have fairly tight windows. The other issue with increasing WF duration and capping the damage is that it makes it far too easy for low ping players to comfortably do anything they want in that window, making it super easy.

    The best solution imo would be to have WF auto-trigger hypercharge if it's available since they're CLEARLY designed to go together, and further reduce (or eliminate entirely) the animation lock associated with it so you don't have that awkward delay.
    You don't double weave between 1.5s GCD, that's impossible.
    Problems comes from that single weaving, it's actually easier to double weave between 2.4s GCD rather than single weave between 1.5s GCD.
    Also, due to raidbuff lasting 10-15s, you are required to weave between the Heatblast or you'll loose GR/Ricochets over the fight.

    Tying wildfire and hypercharge would change nothing as it has nothing to do with the current lag issue.
    (0)

  3. #3
    Player
    Mistyregions's Avatar
    Join Date
    Apr 2019
    Posts
    424
    Character
    Misty Regions
    World
    Brynhildr
    Main Class
    Warrior Lv 80
    Quote Originally Posted by Capn_Goggles View Post
    I don't know people are TRYING to weave 2x between heat blast. It's on a 1.5 second GCD and you get three charges of gauss round and ricochet; since WF isn't affected by oGCD abilities I see literally no reason to double-weave them during a 1.5 GCD burst window. The ping issue arises from the fact that both wildfire and hypercharge carry animation locks, have desynced durations, yet are entirely co-dependent and have fairly tight windows. The other issue with increasing WF duration and capping the damage is that it makes it far too easy for low ping players to comfortably do anything they want in that window, making it super easy.

    The best solution imo would be to have WF auto-trigger hypercharge if it's available since they're CLEARLY designed to go together, and further reduce (or eliminate entirely) the animation lock associated with it so you don't have that awkward delay.
    Ease and ability have nothing to do something because you have bad internet its not the same thing. If we fix it (5 HB) that way or extend the WF by 3 seconds but have it capped at 6 stacks , who cares if it easier for people with bad ping? You could have a direct line to it and it wont make you any better and it's just a QoL improvement.
    (0)