Results 1 to 10 of 11

Hybrid View

  1. #1
    Player
    OneTrueMiqote's Avatar
    Join Date
    Jul 2019
    Posts
    32
    Character
    Reina Kousaka
    World
    Leviathan
    Main Class
    Thaumaturge Lv 80
    Reducing F1's cast time to 2 seconds wouldn't give you 1 extra weave slot btw. There isn't enough time to weave without clipping. But I do like your idea. This helps mitigate the lack of movement tools at low levels to a degree and a bit more time to react for F3 proc is comfortable.

    I'm not sure how increasing F3 proc's stack to 2 would be implemented as there is a timer. If this timer was removed then it would absolutely make a difference at max level. Or if it resets per every new F3 proc? Neither wouldn't totally solve the problem because then you would ideally want to have 1 F3 proc on hold before the timer runs out for movement, which still means you need to react as quick to the second F3 proc stack as you do now. Either way, it seems like a bit of a clunky design when OP's idea already largely solves the problem.
    (0)

  2. #2
    Player
    Kabooa's Avatar
    Join Date
    Sep 2013
    Posts
    4,392
    Character
    Jace Ossura
    World
    Gilgamesh
    Main Class
    Goldsmith Lv 100
    Quote Originally Posted by OneTrueMiqote View Post
    Reducing F1's cast time to 2 seconds wouldn't give you 1 extra weave slot btw. There isn't enough time to weave without clipping. But I do like your idea. This helps mitigate the lack of movement tools at low levels to a degree and a bit more time to react for F3 proc is comfortable.

    I'm not sure how increasing F3 proc's stack to 2 would be implemented as there is a timer. If this timer was removed then it would absolutely make a difference at max level. Or if it resets per every new F3 proc? Neither wouldn't totally solve the problem because then you would ideally want to have 1 F3 proc on hold before the timer runs out for movement, which still means you need to react as quick to the second F3 proc stack as you do now. Either way, it seems like a bit of a clunky design when OP's idea already largely solves the problem.
    What's clunky about letting it stack to 2?

    Issue: You overwrite firestarters unless you stop a Fire 1 cast to use the Firestarter.

    If Firestarter stacks -to 2-, then you never waste a firestarter back to back and never have to stop Fire 1.

    It has no implications at max level because using a Fire 1 in place of a Fire 4 to maybe proc a Firestarter in order to have it during movement is a DPS loss. You will lose any DPS you could potentially gain by doing this.

    There is precedent in game of Stack/Timer mechanics, and given the initial problem is about potentially losing a back-to-back cast, the timer is irrelevant.
    (1)