+ Reply to Thread
Page 1 of 3 1 2 3 LastLast
Results 1 to 20 of 42

Thread: Illidan, Shear and Shield Block

  1. #1
    Join Date
    Feb 2008
    Posts
    14

    Illidan, Shear and Shield Block

    Let me start out by saying Hello. This is my first post. I have been reading posts here for quite a while and this is the first time that I have needed to post a question that I couldn't find the answer to here. The example I am going to use for my question is on Illidan. My guild has killed Illidan numerous times and it is usually a 1 shot so this is not a "HALP US WITH ILLIDAN" post.

    My question is about Shield block.

    Last night on Illidan we were at 10% and there was 3 seconds before he went into demon form. He started casting a shear and I shield blocked like the thousands of times before. My stats with shield block active are 30% to dodge, 23% to parry and 104.88% to block. With shield block active I took the shear and he 1 shot me (we dont run to traps, they are always across the room so he was enraged). I guess there are 2 parts to my question. How did the shear hit me when I had 104.88% to block? Can someone calculate the chances of me getting hit with shear with 30% to dodge, 23% parry and 105% to block.

    I thought I read something a while back about the bosses hit rating and you need 106% to block to guarentee that you block the attack. We went through the combat logs and grim reaper reports and my shield block was active when the shear went up on me. More or less I just want to know why it happened and see what the chances of something like that happening are.

  2. #2
    Join Date
    Jul 2007
    Location
    Badajoz, Spain
    Posts
    755
    Illidan's shear can be dodged, parried and blocked, the only thing it can't never happen is a Shear missed. Then you just need your dodge+parry+block to be 102,40% to avoid getting sheared.
    The 25% of block needed for Illidan is a myth and if you read any of those articles in this site you should have known this.

    However and answering your question:
    - You could have not been facing Illidan properly.
    - Latency could have make your shield block buff comes a millisecond after shear hitting you.
    - Some times Illidan bugs its own cast and double cast its shear. Specially after he enrages in phase 5. I have seen a lot of times Illidan casting shear, then enraging, then casting another one.

    If you logs your combatlog maybe we could check if it was a latency issue or another factor involving it.

    In summary, TBC raiding is easy. 9/10 encounters can be summarized with 1 phrase. Stay out of the fucking fire.
    Panda Cub with a Gnome pet!

  3. #3
    Join Date
    Feb 2008
    Posts
    14
    Well, I guess that solves that. I did notice when he was casting shear that it was about 1/2 way through the cast and the cast started over. Shield block was still up when the shear went off but it almost looked like Illidan took spell knock back (which is impossible). I knew that shear couldn't miss so thats why I was thinking about the hit rating or whatever and over 100% to block.

  4. #4
    Join Date
    Feb 2008
    Posts
    14
    We do logs for WWS every night but last nights haven't been posted yet. I will get that for you as soon as we get it up. I didn't log last nights raid for some reason but other people did.

  5. #5
    Join Date
    Oct 2007
    Location
    Bulgaria
    Posts
    8
    Short answer - yes, Shear can go through shield block buff (both charges up) while you are facing Illidan.

    Long answer - our guild has been farming Illidan for over 4 months, I'm the MT and I've tanked him all the times except for 2-3 kills where I swapped with an OT to experience stage 2 adds tanking. I personally take care of the WWS logging and parsing so all our kills are tracked.

    Usually everything is alright and Shear has never been a problem except those 3 times. During these months of farming and as you said "thousands of shears blocked" there were 3 noticeable cases when Shear was able to go through my shield block buff. I do not rely merely on human perception so of course I log and parse all boss fights and in all 3 cases (which happened on different days) my combat log was clear - "you gain Shield Block" - about 300-600 milliseconds later "you are affected by Shear" followed by "Shield Block fades from you" a few seconds later. Note that I've checked all my Illidan parses and my shield block buff is always up 300-600 milliseconds before the shear cast ends so at first glimpse there is no difference between what usually happens (and is supposed to happen) and those 3 times mentioned above.

    Why is that? I can not give a straight answer. My guess is that its either a rare bug or the server side check for my buff gain (shield blcok in this case) is performed after the debuff gain check due to slight lag somewhere on the route.

    All I can say atm is that I have experienced the event of Shear going through my shield block buff while I am standing still facing Illidan - proven by my own perception and by the combat log. Although extremely rare - it does happen.

    (for the record - I play with 40-45 FPS and 60-70 ms latency in raids)
    Last edited by Highfather; 02-28-2008 at 01:40 PM.
    Higfather
    Being better than all the rest doesn't mean that you are good enough!

  6. #6
    Join Date
    Feb 2008
    Posts
    14
    Thats is more on track with the kind of answer I was expecting. I was hoping to find something that I could do to prevent it from ever happening again but I was afraid that was going to be the case. The same thing happened on our very first night a while back but I wrote it off as not having 100% block. I can't stand when unexplainable things like that happen because I feel like I am making an excuse. But I guess its just one of those things. Kinda like when Sanguinar got 4 crushing blows on me each for the exact same amount all in the same millisecond. But I will save that one for another thread sometime.

  7. #7
    Join Date
    Jul 2007
    Location
    Badajoz, Spain
    Posts
    755
    That could have been more of a Parry-gib situation.

    In summary, TBC raiding is easy. 9/10 encounters can be summarized with 1 phrase. Stay out of the fucking fire.
    Panda Cub with a Gnome pet!

  8. #8
    Join Date
    Feb 2008
    Posts
    14
    Quote Originally Posted by Narshe View Post
    That could have been more of a Parry-gib situation.
    Thats what I thought it was at first too, but we went through the logs and I didn't even get a hit off, as soon as he spawned he 1 shot me only later to find out it was 4 crushing blows in the same swing. It was almost like he swung a millisecond before he even became hostile.

  9. #9
    Join Date
    Aug 2007
    Location
    Notlob its a palindrome
    Posts
    736
    Quote Originally Posted by Troxed View Post
    Thats what I thought it was at first too, but we went through the logs and I didn't even get a hit off, as soon as he spawned he 1 shot me only later to find out it was 4 crushing blows in the same swing. It was almost like he swung a millisecond before he even became hostile.
    we talking about illidan?

    he cant crush.......

  10. #10
    Join Date
    Feb 2008
    Posts
    14
    Quote Originally Posted by nicki View Post
    we talking about illidan?

    he cant crush.......
    No, that was Sanguinar on Kael, which is why I said I would save it for another thread. Sorry for the confusion.

  11. #11
    Join Date
    Aug 2007
    Location
    Notlob its a palindrome
    Posts
    736
    xD i must catch up my sleep

  12. #12
    Join Date
    Feb 2008
    Posts
    14
    Quote Originally Posted by nicki View Post
    xD i must catch up my sleep
    same, sleep is good.

  13. #13
    Join Date
    Mar 2008
    Posts
    785
    The shear double cast can happen, but still rarely effects whether or not you actually get sheared. The more likely scenario is latency, the same effect that occurs when an NS heal hits a tank for 10,000 before he dies in a combat log, or a boss hits a paladin for 23,000 critical as Divine Shield goes off, and the paladin never takes a point of damage.

  14. #14
    Join Date
    Jul 2007
    Location
    Badajoz, Spain
    Posts
    755
    I have another experience. My last Hydross kill (attunement run) we decided I could stay for like --- 25% of the boss in the same stage. So Hydross got the nasty debuff stacked I can't remember how many times.

    Well.... I got hit for 23k damage and I didn't die... but in my resistance gear I have 20k HP with all buffs.... so explain it if you can :P

    In summary, TBC raiding is easy. 9/10 encounters can be summarized with 1 phrase. Stay out of the fucking fire.
    Panda Cub with a Gnome pet!

  15. #15
    Join Date
    Dec 2007
    Posts
    1,630
    Quote Originally Posted by Narshe View Post
    I have another experience. My last Hydross kill (attunement run) we decided I could stay for like --- 25% of the boss in the same stage. So Hydross got the nasty debuff stacked I can't remember how many times.

    Well.... I got hit for 23k damage and I didn't die... but in my resistance gear I have 20k HP with all buffs.... so explain it if you can :P
    I've had extremely odd stuff like that happen before too. Way back in the day, on my rogue in MC, I was stealthing around and aggroed a surger, and it started beating the hell out of me, but my vanish cooldown wasn't up yet. Anyway, I finally vanished, and then looked at my combat log, and I took something like 9000 damage when I only had 4000 hp. And I obviously didn't get any heals, and the server wasn't lagging.

    ImageShack - Hosting :: hacksvw2.jpg

    I can't believe I even still have that picture stashed away.

    Anyway, exceptionally weird server behaviour just happens sometimes :|
    Xav
    Formerly Xavastrasz
    Quote Originally Posted by Rak View Post
    control+c control+v amirite?
    Quote Originally Posted by Magnuss View Post
    Hell no, its Xav, he is gonna type that bitch till his fingers fall off.

  16. #16
    Join Date
    Oct 2007
    Posts
    84
    It's all Jaeden's fault imo.

  17. #17
    Join Date
    Feb 2007
    Location
    SD, CA
    Posts
    44
    Quote Originally Posted by Malignus View Post
    It's all Jaeden's fault imo.
    Agreed.

  18. #18
    Join Date
    Feb 2008
    Posts
    7
    This exact same thing happened to us last night on Illidan. I have posted a screen shot of the Recount log after the fact. I might understand if the shear and the shield block were cast withing milliseconds of each other, then possibly there could be syncing problems. However, in this log, you can clearly see that the SB was applied a half a second PRIOR to the shear hitting.

    Log


    Full size screen shot
    http://img527.imageshack.us/img527/8...8234038zi4.jpg

  19. #19
    Join Date
    Mar 2008
    Posts
    9
    I had problems on my first few attempts - but I noticed I had a really, really large number of buffs. Examining combat log showed some of the most recent ones falling off much earlier than they should (notably: Holy Shield falling off after 3 seconds without expending a single charge).

    It may not be the exact reason or this the perfect solution, but I started removing unnecessary buffs (AI, Spirit, BoW, weapon oil) and the problem seemed to go away.

  20. #20
    Join Date
    Dec 2007
    Posts
    1,630
    Quote Originally Posted by Moraval View Post
    This exact same thing happened to us last night on Illidan. I have posted a screen shot of the Recount log after the fact. I might understand if the shear and the shield block were cast withing milliseconds of each other, then possibly there could be syncing problems. However, in this log, you can clearly see that the SB was applied a half a second PRIOR to the shear hitting.

    Log


    Full size screen shot
    http://img527.imageshack.us/img527/8...8234038zi4.jpg
    This is a little bit different. For one thing, the combat log timers aren't exact, and often aren't actually accurate or very truthful. I don't know why this is, but it's consistent, and can be proven rather easily by observing combat log parses. Basically, the combat log seems to estimate when events are actually happening, within a one second window, and assigns a number to it. I don't believe the actual wow client supports active accurate logging on any intervals of a smaller value than 1 second.

    Because of that, your shield block may have been cast only *very* slightly before the Shear, and then due to latency and client/server not being perfectly synced, cause you to get shear since you didn't actually have the shield block stats buffed on the server yet. That's what I would assume happened, anyway. Due to shear's 1.5 second cast, I'm always hitting SB at least a second before it hits, unless I'm short rage and then have to do bloodrage first.

    This isn't to discredit or downplay the oddities with Shear that do actually happen, and other weird Illidan behaviour (since I've experienced it too), but I kind of just wanted to point out that I wouldn't put much faith into timespans displayed by any combat log parser. (This is why whenever I look at a log I go only by the seconds and attempt to logically deduce when stuff happened)

    Quote Originally Posted by Stroja View Post
    I had problems on my first few attempts - but I noticed I had a really, really large number of buffs. Examining combat log showed some of the most recent ones falling off much earlier than they should (notably: Holy Shield falling off after 3 seconds without expending a single charge).

    It may not be the exact reason or this the perfect solution, but I started removing unnecessary buffs (AI, Spirit, BoW, weapon oil) and the problem seemed to go away.

    They raised the buff cap to some obscenely high number some time ago, more than a year now, I think. I haven't heard of any buffs being knocked off due to having too many since then. This is also when I actively raided engame during TBC's early launch when getting every single buff you possibly can was common for some of the more pleasant 1.0 versions of the bosses. This is a screenshot of an old Al'ar kill, all of my own buffs aren't even listed, nor are anyone else's, since my unit frames weren't set to show more than like 16 or something fairly small. (You can't even see my int, or the tank's ironshields, etc). Nothing was ever pushed off anyone in these type of raids, where you could stack obscene numbers of buffs/consumables together.

    ImageShack - Hosting :: buffsdh8.jpg
    Last edited by Xav; 03-20-2008 at 10:44 PM.
    Xav
    Formerly Xavastrasz
    Quote Originally Posted by Rak View Post
    control+c control+v amirite?
    Quote Originally Posted by Magnuss View Post
    Hell no, its Xav, he is gonna type that bitch till his fingers fall off.

+ Reply to Thread

Bookmarks

Posting Permissions

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