Stun break with 4 seconds immunity abuse

Discussion in 'General Archive' started by ElveElve, Jun 28, 2015.

Dear forum reader,

if you’d like to actively participate on the forum by joining discussions or starting your own threads or topics, please log into the game first. If you do not have a game account, you will need to register for one. We look forward to your next visit! CLICK HERE
Thread Status:
Not open for further replies.
  1. ElveElve

    ElveElve Someday Author

    Hey,

    It seems like running and longstanding metagaming, grab the '4 sec immunity after stun' talent and break stun whenever possible with nova, jump, teleport etc.

    Why is there immunity after stun breaking? seems like powerful enough to just break stun, it stands no reason why would you be immune to it afterwards.

    Honestly, go into open arena and watch all the kids use stun break + immunity whenever they get stunned. What is the point of stun then, if you can easily break it with skills having less cooldown than your own stunning skill?

    Elve
     
  2. Heaven

    Heaven Junior Expert

    Because otherwise we would see people dying 20 secs into the battle to the first warrior going after them. It puts balance into the game, and, honestly, is completely fine as it is.
     
    AmerickaNindza likes this.
  3. trakilaki

    trakilaki Living Forum Legend

    I can't see any abuse ... anyone can get those skills.
     
    DesertKoala likes this.
  4. Morinphen

    Morinphen Forum Overlooker

    Let's view it from another standpoint, shall we? Say you want to face a boss, but you're too weak to just tank it and see who kills who faster. But, if the boss is stunnable - even more so, repeatedly, then you can beat it without a problem - yes, it would probably take a lot of time and you'd need to be careful at coordinating your stuns in matter of timing, but that's beyond the point - thing is it could be done. I, just as many others, could make short work of any PvP opponents if I could keep them stunned while pummeling them over & over until they finally die. Yes, stun break + immunity is annoying... I'm not denying that, but a solution for one person is a problem for the other in PvP... thus the other has to come up with a solution to his problem, solution which will be a problem to the original guy. Plus, it's a choice: you choose to have 4-sec. immunity after being stunned rather than the other talent for that level, and you also choose to make one of your skills be a de-buff in detriment of another talent.
     
  5. ScientiaPotestasEst

    ScientiaPotestasEst Someday Author

    Hi Elve,

    Since I know you're a DK and you're struggling with opponent's stun breaks and stun immunity, may I suggest trying a class less reliant on stuns to attack?

    Rangers is highly recommended by me, you can make one and have fun in arena without extensive grinding/buying. Otherwise, mage is also a decent choice.

    Your other option is to grind excessively on your DK or make purchases. Heavy P2P DK is the strongest class in the end.
     
  6. _Baragain_

    _Baragain_ Living Forum Legend

    That is why I love the bugs in map2. They are stunable and using just two stuns, I can keep one from attacking indefinitely and kill it at my leisure. It gets more complicated when there are 2-5 bugs at once, but still doable.

    Now, on topic so the mods don't get itchy "delete" fingers;

    Elve,
    Speaking from experience, before I got stun breaks and stun immunity on my DK, PvP was a nightmare. It required very careful timing and strategy to force the other classes to use their escapes and then use a headbutt on them. In the end, it made me a better player, a better DK, and prepared me so that when I got those skills that I would not make the same mistakes that my opponents made against me. Persistence is the key to PvP, and in the end, superior technique can beat all but the heaviest P2W/"No-Life-Outside-DSO's-PvP" players. Good luck, stick with it, and, soon, they will have reason to fear you.
     
    Shiladitya and Morinphen like this.
Thread Status:
Not open for further replies.