Back to home

Thursday, April 2, 2009

Maim my ass off... (Blogsourcing)

With not much melee around there is a good chance you will be maiming in Ulduar.

Last night I was in PTR in Ulduar, testing General Vezax. There was no thrash this time, but compared to last time we only had 1 rogue. The people that could interrupt were that rogue, 1 DK, me and an other druid in catform. I never was in a raid as feral, so I don't even know if Maim could interrupt spellcasts on bosses before 3.0.

Anyway it sucks! For kick a rogue only needs 25 energy. For maim we need to have Combopoints and it costs us 35 energy. A major DPS nerf. When it is your time to interrupt you want to be able to do that immediately. And you have to be ready!. That meant that it sometimes took 20 seconds of waiting time. 20 seconds of keeping GCD ready, 20 seconds of seeing your energy being full, 20 seconds in which you see Rip, SR, Mangle and Rake all drop off from your target... So fair to say my DPS was not optimal. That plus there was a dps nerf about 700 dps for cats on that boss. Well I think it would be about 700 dps even if I didn't interupt.
Also TellMeWhen still isn't fixed and instead of only showing my debuffs it shows debuffs casted by others too, though mine has priority, meaning it will show my rip with 2 seconds left before the other druid's rip with 16 seconds left. But after my Rip is gone it will show the other druid's Rip.

My dps could have been higher but the bossfight itself is totally unreliable too. We were playing from Europe and the server is in the US. That meant we had a .325 latency. Meaning I see the spellcast when it is already going and the boss knows I maimed him somewhat later too. So I had to keep GCD ready.

But it is my thought the boss is bugged. Because of a special shirt GM's provided us for this fight we were all hitcapped and my maim did always hit. The split second I saw the spell being cast I maimed but often the boss kept on casting his spell anyway. He also has the tendency to, after having a cast go through, cast 2 more after that, without others being ready for that. So that was a definite wipe every time.

Now the blogsourcing part of the post; I have a question for you on why maim doesn't always work.
Also I checked combat log and I wonder how that works too. My combat log showed me casting maim and doing x damage. 2 lines below that I saw the General Vezax his spell hit me. The thing I want to know on how that works is: Is the combat log local or server side? For instance, chat is server side. When you type a message and there is a lag you will not see the message. The message has to be processed by the server first and then will be given back to you (and whomever it may concern) and only then the message can be read. Does the combat log work the same? If you maim does the server have to process it and then you will see the maim in your combat log or will the combat log show it the second you cast it, not considering whether the server has received the maim?

PS in this case it could have been that the cast was ready before I maimed and that during those 2 lines I mentioned earlier the spell was traveling from him towards me. Still the change for that is really small, because since I was in melee range the spell (aoe) would have to hit me immediately.


  1. The combat log is whatever you experience - but it is a good representation of what the server thinks you did and how it treated you. What that tells me is that you got the maim off, but due to latency it wasn't 'cast' until after his cast goes.

    Maim doesn't have a travel time, but latency certainly does.

  2. I never had lagspikes during the whole fight. I even saw my maim on cooldown. That meant the server had sent me back the message that maim was used (right). The server knew it, but the boss did not.

    So either:
    1 the server was sluggish interpreting the maim into an action (while sending me back that is was recieved);
    2 The boss was bugged;
    3 The boss had a buff that made him immune to interrupts.

    Though it being PTR and stuff I rather think it was the second thing.