Page 1 of 2
1
2
LastLast
  1. #1

    Void Shift killed me!

    Never had this happen before:
    http://imgur.com/5ofvbG4

    Has this happened to anyone else?
    Last edited by Music; 2013-11-16 at 04:02 AM.

  2. #2
    Deleted
    void shift should never bring anyone under 25% hp and you could have taken dmg right at the moment you shifted, kor krons dmg could have had a delay when it dealt the damage
    Last edited by mmoc29c502100c; 2013-11-16 at 03:33 AM.

  3. #3
    Quote Originally Posted by fail View Post
    void shift should never bring anyone under 25% hp and you could have taken dmg right at the moment you shifted, kor krons dmg could have had a delay when it dealt the damage
    I think I know what happened, though, and you're partially right.

    At the time I had 788,880 hp.

    I cast Void Shift, while it was traveling I took 210,640 damage, which was 27% of my health.
    So then I took the 591,660 (75% of my health since I was full health) from Void Shift, for a total of 802,300 and died. Not sure why overkill didn't show, but I'm pretty sure that's what happened.
    Last edited by Music; 2013-11-16 at 04:35 AM.

  4. #4
    Its server lag that killed you, not void shift.
    I'm guessing you sit somewhere 255ms server based on the timestamps.

    The add hit you at 23:17:20:244
    You cast void shift at 23:17:20:311
    Your client recieved the notification that you got hit by the add at 23:17:20:499
    The server received your request to void shift at 23:17:20:566 (It's likely during this request that it does the check to see if you've got enough health, which based on the health your client reported to the server, you would've been fine, So it approved the full hit/heal)
    Then you received the hit from voidshift at 23:17:20:821
    Last edited by Nestar; 2013-11-16 at 11:53 AM.

  5. #5
    No I've had it glitch too. I've even had it kill me and my target simultaneously a couple times which is wsird.

  6. #6
    Deleted
    I've had this happen quite a few times (23~ MS the majority of the time). It kinda puts me off using it. ^^

  7. #7
    Bloodsail Admiral nobodysbaby's Avatar
    15+ Year Old Account
    Join Date
    Feb 2009
    Location
    Sweden
    Posts
    1,055
    Ohhh... now I understand a few mishappenings in the past. And yes, it got me quite insecure using it aswell.

  8. #8
    Quote Originally Posted by Nestar View Post
    Its server lag that killed you, not void shift.
    I'm guessing you sit somewhere 255ms server based on the timestamps.

    The add hit you at 23:17:20:244
    You cast void shift at 23:17:20:311
    Your client recieved the notification that you got hit by the add at 23:17:20:499
    The server received your request to void shift at 23:17:20:566 (It's likely during this request that it does the check to see if you've got enough health, which based on the health your client reported to the server, you would've been fine, So it approved the full hit/heal)
    Then you received the hit from voidshift at 23:17:20:821
    Can you explain how you got the timestamps more in detail? I don't think I fully understand.
    Also, I sit at ~20ms during raid.

  9. #9
    I'm guessing it was a lag spike of some sort.
    As far as timestamps go
    The logs show you casting the void shift at 461, directly following your smite, Yet both the heal from smite and dmg/heal from Void Shift happened at 821. That's a 360ms delay (for the travel both ways). Implying that your MS to the server was at the very least, half of that. Or 180ms (It was like 6AM when I responded to this initially and I've closed all the tabs I was using when I figured it out, So I don't recall exactly where my 255/510ms comment came from, Was likely looking at some of the delay on the earlier abilities)
    Regardless, a 180ms delay on abilities implies something was going very wrong with your connection based on the standard <20ms you mentiond.

    Edit, I see it now.
    One of your earlier atonements in the log at 17.646 had its atonement hit at 18.400. Almost a 754ms gap. Looking at my own logs I see a delay between expected hit/heal on atonement about 250ms past my own standard delay. Likely time taken by the server to calculate the smart heal.
    Honestly not sure how much of this is affected by the whole healing lag from aoe/smart heals that a lot of guilds have been complaining about. I've heard its significantly worse in 25's, so that may affect it too.
    Last edited by Nestar; 2013-11-17 at 01:28 AM.

  10. #10
    I'm very hesitant to think ms works that way in logs.

    Here's a log of me in Shrine just now. http://www.worldoflogs.com/reports/t...3D+%22Music%22
    My ms is at 22 and has been stable at that the entire day.

    Looking through anyone's logs there are lots of events that fire off in the same millisecond almost constantly. There's also a large delay on atonement regardless of the player. Go take a look through some logs and you'll find the same thing happening.

    I think it's hard to tell what exactly happened based on what I've stated/linked above.

  11. #11
    Happening at the same time yes, Usually when you finish a cast with an instant cast. Eg Smite into PWS. Theyll both show as happening at the same time. The server lag comes into play when you look at the time the ability finished and when the effect happened.

    The logs will show,

    Started casting "Heal"
    Expected cast duration
    Casted "Heal" on "Target"
    Casted "Instant Cast Heal"
    Server lag
    "Heal" hit "Target" for "Amount"
    "Instant Cast Heal" hit "Target" for "Amount"

    Both casts and both hits will generally have the same timestamp on your own combat log.

    And yes, I mentioned that the delay on atonement may have to do with healing lag, On my own logs I was seeing shorter delay and I run between 90-150ms depending on which connection I'm on. But it was still approximately double my own server ms plus 250. Keep in mind I also run 10 man, So the healing lag may affect you much more severely.

    Do you happen to have a WoL copy of that void shift death btw? I'm curious how much the timing would change if seen from someone elses point of view.
    Last edited by Nestar; 2013-11-17 at 02:10 AM.

  12. #12
    I was talking about other people's events happening at the exact same time as mine, and the initial combat log link was from our tank's logs. Our logs are private for now, so I can't really link them to you.

    My own logs:
    [22:17:23.299] Music casts Smite on Garrosh Hellscream
    [22:17:23.328] Music casts Void Shift on Einstean
    [22:17:23.713] Music Smite Garrosh Hellscream 72072
    [22:17:23.713] Music Void Shift Einstean +747232 (O: 0, O: 75637)
    [22:17:23.713] Music Void Shift Music 591660
    Also cast a Void Shift in Shrine and the heal and damage hit at the exact same time multiple times.

    Looking at your logs I see a delays of up to 800ms if not more: IJ kill

    For example:
    [21:32:06.713] Nestar casts Smite on Iron Juggernaut
    [21:32:06.961] Nestar Holy Fire Iron Juggernaut 1895
    [21:32:07.031] Nestar Smite Iron Juggernaut 59439
    [21:32:07.457] Nestar Atonement Rikkuz +2071 (O: 0)
    [21:32:07.820] Nestar Holy Fire Iron Juggernaut *4547*
    [21:32:07.842] Nestar Atonement Rikkuz +39487 (O: 0, O: 25476)
    Last edited by Music; 2013-11-17 at 03:10 AM.

  13. #13
    Quote Originally Posted by Music View Post
    I was talking about other people's events happening at the exact same time as mine, and the initial combat log link was from our tank's logs. Our logs are private for now, so I can't really link them to you.

    My own logs:

    Also cast a Void Shift in Shrine and the heal and damage hit at the exact same time multiple times.

    Looking at your logs I see a delays of up to 800ms if not more: IJ kill

    For example:
    Yes, the damage and heal both happen at the same time, But they were delayed from the cast, Which is what I was referring to.

    and ya, the copy of my own logs there, that was an exceptionally laggy day for me. So I wouldve been sitting around 150ms world, Which in theory it should be 260ms longer than your own delay

  14. #14
    Quote Originally Posted by Nestar View Post
    Yes, the damage and heal both happen at the same time, But they were delayed from the cast, Which is what I was referring to.
    Void Shift has travel time, but I'm not sure if you're referring to the actual Void Shift cast or the Smite cast delaying Void Shift? Kinda confusing.

    Quote Originally Posted by Nestar View Post
    Yes, the damage and heal both happen at the same time, But they were delayed from the cast, Which is what I was referring to.

    and ya, the copy of my own logs there, that was an exceptionally laggy day for me. So I wouldve been sitting around 150ms world, Which in theory it should be 260ms longer than your own delay
    I looked back at other logs of yours and they're all around 800ms or somewhere above where they "should" be. Another IJ 10/29
    [20:13:56.331] Nestar Smite Iron Juggernaut *97001*
    [20:13:56.959] Nestar Penance Iron Juggernaut 63936
    [20:13:56.978] Nestar casts Penance
    [20:13:57.137] Nestar Atonement Rikkuz +*28313* (O: 0, O: 23910)
    [20:13:57.523] Nestar Atonement Mognovox +19188 (O: 0, O: 49656)
    Yet another IJ from 10/22
    [20:07:50.073] Nestar casts Smite on Iron Juggernaut
    [20:07:50.255] Nestar casts Penance
    [20:07:50.478] Nestar Smite Iron Juggernaut 47172
    [20:07:51.140] Nestar casts Penance
    [20:07:51.168] Nestar Penance Iron Juggernaut 62141
    [20:07:51.222] Nestar Atonement Xuen +50073 (O: 0)
    [20:07:51.638] Nestar Atonement Rikkuz +65963 (O: 0)
    Unless you happen to get extremely laggy on IJ every week, I don't know what to tell ya.

  15. #15
    Quote Originally Posted by Music View Post
    Void Shift has travel time, but I'm not sure if you're referring to the actual Void Shift cast or the Smite cast delaying Void Shift? Kinda confusing.


    I looked back at other logs of yours and they're all around 800ms or somewhere above where they "should" be. Another IJ 10/29


    Yet another IJ from 10/22


    Unless you happen to get extremely laggy on IJ every week, I don't know what to tell ya.
    I hadn't considered the travel time. It's possible there's a bug where the calculation for damage is done on cast, That would mean if anything hit you between the cast and the visual effect dropping you more than 25% hp, It would be a guaranteed kill. Might be worth looking into.

    As you probably noticed already IJ is about the only fight I regularly heal

    Just to clarify a bit of my math here, maybe deal with some of the confusion.
    I'm assuming any heal/damage that occurs requires both a request to the server (world ms) and back from the server (home ms). Usually these should be about the same. For myself being at 90 best case, 150 worst. I would expect a delay of approx 180-300ms between the lines "casts on target" and "heal/dmg" I am seeing the strange counts on atonement as well. Looking at the same fight as the one you just linked from me but at a flash heal I've got a

    [20:12:30.815]Nestar begins to cast Flash Heal
    [20:12:32.105] Nestar casts Flash Heal on Mognovox
    [20:12:32.375] Nestar Flash Heal Mognovox +*133822* (O: 0)

    A gap of 270ms

  16. #16
    Looking quickly it is likely travel time. VS is technically a missile.

    - - - Updated - - -

    Looking closely, thats exactly what happened.

    461 - Void Shift cast (and health amounts to be transferred calculated)
    499 - You're hit by the Warbringer
    821 - VS Missile hits your Monk/you and you take transfered VS damage at original calculation.
    Death


    Its server side latency (as small as it may be) added to the VS travel time. Bad luck on the swing from the Warbringer during that ~360ms window.
    Last edited by derevka; 2013-11-17 at 04:08 PM.

  17. #17
    Quote Originally Posted by derevka View Post
    Looking quickly it is likely travel time. VS is technically a missile.
    Mmhmm just as I though; I posted that earlier in the thread .
    Quote Originally Posted by Music View Post
    At the time I had 788,880 hp.
    I cast Void Shift, while it was traveling I took 210,640 damage, which was 27% of my health.
    So then I took the 591,660 (75% of my health since I was full health) from Void Shift, for a total of 802,300 and died. Not sure why overkill didn't show, but I'm pretty sure that's what happened.

  18. #18
    Quote Originally Posted by Nestar View Post
    Its server lag that killed you, not void shift.
    It's not server lag. This happened to Talbadar on the B.net World Championship 2012, which is played in lan. It's a bug that exists since the spell was added, 'cause Void Shift is pretty much like Pyroblast, in terms of having a (much shorter) flight time, and the spell not taking effect until the animation lands.
    When you cried I'd wipe away all of your tears
    When you'd scream I'd fight away all of your fears
    And I held your hand through all of these years

  19. #19
    Stood in the Fire h3lladvocate's Avatar
    10+ Year Old Account
    Join Date
    Jun 2009
    Location
    幻想郷
    Posts
    468
    Yup, happened to me a few times.

    SO glad were getting a talent that lets us spam this 100% bug free spell... really hating Priest in WoD so far

  20. #20
    Quote Originally Posted by Nestar View Post
    Its server lag that killed you, not void shift.
    I'm guessing you sit somewhere 255ms server based on the timestamps.

    The add hit you at 23:17:20:244
    You cast void shift at 23:17:20:311
    Your client recieved the notification that you got hit by the add at 23:17:20:499
    The server received your request to void shift at 23:17:20:566 (It's likely during this request that it does the check to see if you've got enough health, which based on the health your client reported to the server, you would've been fine, So it approved the full hit/heal)
    Then you received the hit from voidshift at 23:17:20:821
    get rid of server lag. client/server communication needs to be synced to the effing nano second.

Posting Permissions

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