We have detected that cookies are not enabled on your browser. Please enable cookies to ensure the proper experience.
Results 1 to 3 of 3
  1. #1
    Join Date
    Dec 2009
    Posts
    46

    Anvil first boss suggestions

    The rest of the raid is one of the better raiding experiences i've had in the game. Just please take your time to work on the first boss, or even just disable the boss or do a full rework on the boss if necessary.

    How I would fix it:

    1. Make the adds only spawn a set amount of times. It's a lot easier to balance a boss if it's not a constant dps race to rush through adds and the boss, allowing more viable tactics than simply maximizing raid dps. An example: 90% big drakes spawn. 70% whelplings spawn. 50% big drakes and whelplings spawn together.

    2. Give the boss a set attack pattern.
    For an example: Start the fight with a belly flop. 5 auto attacks. Call adds to main tank. 5 auto attacks. Purple eye. 5 auto attacks. Blue eye. 10 auto attacks. Repeat.

    3. Make the belly flop flop more manageable now that we don't have a runekeeper stone.
    Option 1: Make the buffs on the boss (from adds) not affect belly flop damage.
    Option 2: Remove calling adds to boss/boss running to adds tank mechanic
    Option 3: Make belly flop have a 15s long induction with a morale shield that prevents interrupting until the shield is gone, similar to karazgar fight from thikil-gundu, to stop the belly flop from happening.
    Option 4: Make the add-close-to-boss buff damage part into a defensive buff instead, replacing the +20% outgoing damage with -20% incoming damage. This would also allow AoE on the boss while killing adds, making champions more viable.
    Option 5: Make the whelplings not immune to CC, so they could be CC'd to stop all the whelplings from buffing the boss when they're called to the boss. Give them adaptability buff if necessary, to prevent spamming CC.
    Option 6: Make the boss calling adds to the tank/boss going after adds tank not happen right before a belly flop.

    4.Make the purple eyes not happen on main tank or anyone who's too far away.

    5. If you can't fix the boss, just delete the boss or make it optional.
    Last edited by SotaMursu; Feb 14 2019 at 09:11 PM.

  2. #2
    Join Date
    Aug 2018
    Posts
    134
    Quote Originally Posted by SotaMursu View Post
    The rest of the raid is one of the better raiding experiences i've had in the game. Just please take your time to work on the first boss, or even just disable the boss or do a full rework on the boss if necessary.

    How I would fix it:

    1. Make the adds only spawn a set amount of times. It's a lot easier to balance a boss if it's not a constant dps race to rush through adds and the boss, allowing more viable tactics than simply maximizing raid dps. An example: 90% big drakes spawn. 70% whelplings spawn. 50% big drakes and whelplings spawn together.
    Well, the adds are actually already spawning a set amount of times because the Boss Fight itself will only be 9 minutes long now that there is an Enrage Timer. On T3, once you hit the Boss below 95% he's able to summon adds. He will then resummon all adds who died after 90 or 120 seconds (not sure about the timer here). The way the Boss is intended to be done is probably by dealing with the adds by killing them and doing as much dps to the boss simultaneously.

    Quote Originally Posted by SotaMursu View Post
    2. Give the boss a set attack pattern.
    For an example: Start the fight with a belly flop. 5 auto attacks. Blue eye. 5 auto attacks. Purple eye. 5 auto attacks. Call adds to main tank. 10 auto attacks. Repeat.
    Yes, the Boss needs a set attack pattern. It's just stupid that every single fight is drastically different than the last one because the Boss randomly chooses his abilities every fight.

    Quote Originally Posted by SotaMursu View Post
    3. Make the belly flop flop more manageable now that we don't have a runekeeper stone.
    Option 1: Make the buffs on the boss not affect belly flop damage
    Option 2: Remove calling adds to boss/boss running to adds tank mechanic
    Option 3: Make belly flop have a 15s long induction with a morale shield that prevents interrupting until the shield is gone, similar to karazgar fight from thikil-gundu, to stop the belly flop from happening.
    Option 4: Make the add-close-to-boss buff damage part into a defensive buff instead, replacing the +20% outgoing damage with -20% incoming damage. This would also allow AoE on the boss while killing adds, making champions more viable.
    Option 5: Make the whelplings not immune to CC, so they could be CC'd to stop all the whelplings from buffing the boss when they're called to the boss. Give them adaptability buff if necessary, to prevent spamming CC.
    I disagree. If your group can not manage to survive the Belly Flop without the Runekeeper Stone, then there's something very wrong with your group composition or your DPS class mitigation/morale. Runekeepers Stone was NEVER needed to survive the Belly Flop. The Belly Flop mechanic itself is a fairly good one but they should consider removing these "Dragon Breath Fields" that randomly spawn during the fight. First, they are completely random and the only way to play around them is to basically ignore them (by standing somewhere else where they will not be affected) which is already stupid by itself. In addition to that, sometimes the Energized Whelplings are casting inside of these fields and you have to run in (and if you're unlucky, a new field will spawn in that exact moment). Also, they don't really add anything to the fight, just frustration. (And I don't mean they're overpowered or you can not avoid them but they just are terribly designed.) Besides that, they have been bugged since release and they sometimes stop spawning.


    Quote Originally Posted by SotaMursu View Post
    4. If you can't fix the boss, just delete the boss or make it optional.
    They just need to adjust the randomness of all these events.

    My biggest concern about the new (and probably by the devs intended) strategy is that the group will most likely need to stand close to the adds but the Energized Whelpling will continue to spawn randomly in the Arena. I hope they will make the Energized Whelpling spawn at the same spot where all other adds are spawning.

  3. #3
    Join Date
    Dec 2009
    Posts
    46
    Quote Originally Posted by Snobs View Post
    Well, the adds are actually already spawning a set amount of times because the Boss Fight itself will only be 9 minutes long now that there is an Enrage Timer. On T3, once you hit the Boss below 95% he's able to summon adds. He will then resummon all adds who died after 90 or 120 seconds (not sure about the timer here). The way the Boss is intended to be done is probably by dealing with the adds by killing them and doing as much dps to the boss simultaneously.
    It is currently possible for no adds to spawn at all, while sometimes adds spawn every about 1min30s, based on luck (and getting boss past 95% during a purple eye). An alternative would be having adds always spawn on set time intervals starting from the morale tresholds they're starting to spawn from.

    Quote Originally Posted by Snobs View Post
    I disagree. If your group can not manage to survive the Belly Flop without the Runekeeper Stone, then there's something very wrong with your group composition or your DPS class mitigation/morale.
    The biggest problem with the belly flop mechanic is that if the boss runs into the adds during an eye or when the boss calls adds to him - being able to stop the belly flop in itself would give more options to deal with the randomness. The belly flop in itself is manageable (we're stacking beorning, champ, LM and burglar debuffs, with rk healer on squishier group) as long as there isn't too many buffs from adds touching the boss due to the other mechanics.
    Last edited by SotaMursu; Feb 15 2019 at 12:15 AM.

 

 

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