Results -9 to 0 of 170

Threaded View

  1. #29
    Player
    RiceisNice's Avatar
    Join Date
    Jul 2014
    Posts
    3,514
    Character
    Flo Fyloord
    World
    Famfrit
    Main Class
    Machinist Lv 80
    Quote Originally Posted by RyuDragnier View Post
    Aside from a oGCD taking a little longer to use after certain finished casts than others, I haven't noticed any clunkiness while casting. Then again, I have almost every class at least at level 51 (save for Astrologian, still need to level that one) so I'm used to cast bars.
    Try using two oGCDs inbetween a weaponskills, using bloodletter as soon as it comes off cooldown, and catching straighter shot procs as soon as it pops. I played blm, and firestarter aside, blm still flows coherently and smooth compared to how bard is with how fragmented it can get with oGCD resets and catching straighter shots ( when ss is also a regular part of our rotation, it leads to you hard casting ss worth the buff active, losing both dps and tp).

    It's not breaking to the point that it's that much of a detriment to dps, but it's clear enough that they haven't done any play testing to see how wm actually interacts with bards skill set, versus slapping it on them because they gave it to mch as well. It's just not fun, esp when mch plays pretty much the same with GB but is designed around it.

    As a bard main that enjoyed their fast-flowing moveset and reactive procs, it's incredibly cumbersome to try to catch procs (bloodletter specifically) that occur either during the middle of my cast or after I used a oGCD, I have to either delay my oGCD or next weaponskill. You get that moment of time where you're not casting anything despite your GCD being off cooldown, pauses where I'm literally standing there unable to do anything due to animation locks or a internal CD that prevents you from popping two oGCDs at the same time or too close to each other. It's a complete pace-breaker and really could've been handled better, like giving oGCDs a cast time (such as empyreal arrow) or redoing the function of river in WM. It'd keep the overall pacing of bard similiar to how it was 2.0; constant uptime with no fragmented pauses inbetween because of procs.
    (5)
    Last edited by RiceisNice; 08-03-2015 at 12:33 AM.