We have detected that cookies are not enabled on your browser. Please enable cookies to ensure the proper experience.
Results 1 to 6 of 6

Threaded View

  1. #1
    Join Date
    Mar 2019
    Posts
    664

    Master of War petition thread

    Hello captains!

    Recently the update dropped, this meant that there were some changes made to our rotation and without toomuch getting lost into details I'll cut straight to the point.

    MoW = Master of War

    What has happened to MoW?

    MoW has its crit chance set to +25% for 5 seconds. It also only procs from inspire now when crit. This means you'll have about 33+2+5.5% (40.5) crit chance to proc MoW from inspire.

    For the duration, you'll have 65.5% crit chance to crit lament as your cashout skill.

    Before the change

    Before the change, MoW gave our next melee attack a 100% crit chance but only for one count. However, it worked on both inspire and lament, meaning if you did crit inspire, your next crit on lament would give you another MoW proc to use on devastating blow (though deva blow crit chance got significantly up after the LI rework.) Nonetheless, it provided absolute surety that if you had MoW from inspire, lament would crit 100% followed by whatever melee attack after that. This allowed the captain to get burst combo's off reliably, which was part of its rotation.

    The chance of you generating such chance was around 60% through a double dice cast. (without counting the banner in at the time). This meant you were allowed to throw OB in between inspire (mow) and lament to have guaranteed burst damage.

    The problem with the current MoW

    I'm just going to state what its current form is. It is a slot machine, you have no absolute surety to get your burst off. Yes, as a captain we do marginally more damage than we've ever done before and I am thankful for that, but the way you do damage can no longer be trusted as there's RNG involved. The RNG however may resolve itself over a longer period of combat due to damage getting an overall consistency.

    Why do you not get your burst off? Because even if you have MoW proc with the slim chance we have, it's still only 65.5% you'll crit skills like Lament, which was one of your most reliable burst skills due the old MoW mechanic combined with your buffs.

    The absolute surety the previous MoW gave allowed you to get creative and flexible, especially in circumstances of PvP.

    Solution

    There's a couple solutions I'd like to bring up. But before I'd like to make clear this is only in regards to MoW directed at the captain himself, meaning you as captain in stand alone.

    1. Buff MoW Crit chance in stand alone by 25%, meaning we get 50% crit chance to combat the amount of RNG and give Stand Alone a slight edge over Blade Brother stance in terms of raw DPS output and reliability of that.
    2. Create a tracery that buffs inspire crit chance by 15-20% to deal with unreliability.
      • If possible, I'd like to see the old MoW mechanic return with this tracery, meaning next melee-skill = 100% crit
    3. Create a tracery that buffs MoW crit chance by 20-25%



    I may edit some stuff later

    Suggestions by the community:

    Suggestions coming from the community in ghyniverse

    https://discord.gg/hAZcHspM35

    Bailey — Yesterday at 11:37 PM
    I wouldn't suggest more traceries unless it is very clear they are only Solo stance
    And even then, traceries for only solo stance are kinda weird slot bloat
    "Oh sorry, I don't do enough damage on my red captain because I gear his LI for raids, not solo stance"
    I'd rather just have the cashout be tied to a separate skill that doesn't require any RNG, even if the RNG is still present overall
    Give MoW a standalone skill; make inspire proc give you a stack to cash out and use that skill
    Last edited by Zaheer; Apr 02 2023 at 01:17 PM.
    WhiteGoliath

 

 

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

This form's session has expired. You need to reload the page.

Reload