World of Logs and Siege of Orgrimmar

[Maihem]

In other news: detection for Galakras, Spoils of Pandaria & Norushen was updated. See viewtopic.php?f=12&t=4276

[Killshot]

As far as I can tell, Purifying a Contaminated Puddle only removes a single point of Corruption from Immerseus. Can anyone confirm whether it's 1 or 1.5 points of corruption being removed?

You will never get sum of 100 if something doesn't remove more than 1.


Our Iron Juggernaut logs are getting split into weird parts:
Try 1 (wipe):
http://www.worldoflogs.com/reports/re0p ... 966&e=1208

Try 2 (kill) split into 3 parts:
1: http://www.worldoflogs.com/reports/re0p ... 302&e=2469
2: http://www.worldoflogs.com/reports/re0p ... 486&e=2643
3: http://www.worldoflogs.com/reports/re0p ... 665&e=2701

We don't attack the boss during Siege Mode at all (siege mode lasts 1 min). That may be the reason why this happens. There's a lot of healing during that phase though. Shouldn't healing and damage from the boss reset timeout?

[Kihra]

As far as I can tell, Purifying a Contaminated Puddle only removes a single point of Corruption from Immerseus. Can anyone confirm whether it's 1 or 1.5 points of corruption being removed?

You will never get sum of 100 if something doesn't remove more than 1.

It's just 1 point of Corruption removed for Purification. The issue is really that you can win with as little as 97 corruption removed, since if he can't spawn a Sha Puddle (he needs 4 corruption remaining to spawn 1 Sha Puddle), he just gives up and hands you loot. Note that you typically see some events with Immerseus as a friendly at the end of the fight as debuffs fall off of him on the hostility switch, so you could add "Did the boss turn friendly?" to your detection along with "Did I see enough Corruption?"

Basically the fight terminates in one of two ways... either you hit 100 corruption during the submerge phase while dealing with puddles, in which case he never re-emerges, or you have < 100 corruption and he comes back up with < 4 corruption and goes friendly rather than submerging again.

[Killshot]

It's just 1 point of Corruption removed for Purification. The issue is really that you can win with as little as 97 corruption removed, since if he can't spawn a Sha Puddle (he needs 4 corruption remaining to spawn 1 Sha Puddle), he just gives up and hands you loot. Note that you typically see some events with Immerseus as a friendly at the end of the fight as debuffs fall off of him on the hostility switch, so you could add "Did the boss turn friendly?" to your detection along with "Did I see enough Corruption?"

Basically the fight terminates in one of two ways... either you hit 100 corruption during the submerge phase while dealing with puddles, in which case he never re-emerges, or you have < 100 corruption and he comes back up with < 4 corruption and goes friendly rather than submerging again.

Explain those kills then:
http://www.worldoflogs.com/reports/mz2j ... 799&e=1270 it sums up to only 94
http://www.worldoflogs.com/reports/oxhy ... ?s=0&e=441 with total of 92

But from what I can see purified is only 1 worth. This is true. Still it's really hard to wipe at the end of the fight. If you have 90+ worth of corruption removed you can assume it's a kill. World be a lot better than current validation that results tons of 2 min or less "kills". It seems that boss "dies" earlier. Just need a proper threshold.

[Kihra]

It's just 1 point of Corruption removed for Purification. The issue is really that you can win with as little as 97 corruption removed, since if he can't spawn a Sha Puddle (he needs 4 corruption remaining to spawn 1 Sha Puddle), he just gives up and hands you loot. Note that you typically see some events with Immerseus as a friendly at the end of the fight as debuffs fall off of him on the hostility switch, so you could add "Did the boss turn friendly?" to your detection along with "Did I see enough Corruption?"

Basically the fight terminates in one of two ways... either you hit 100 corruption during the submerge phase while dealing with puddles, in which case he never re-emerges, or you have < 100 corruption and he comes back up with < 4 corruption and goes friendly rather than submerging again.

Explain those kills then:
http://www.worldoflogs.com/reports/mz2j ... 799&e=1270 it sums up to only 94
http://www.worldoflogs.com/reports/oxhy ... ?s=0&e=441 with total of 92

World of Logs sets combat ranges based off damaging events (and probably enemy deaths as well). Healing does not extend the range of a combat, and Immerseus doesn't die, so if he doesn't re-emerge, the final events of the combat will be the damage done to the last Sha Puddle. Therefore if the final points of corruption come from heals after all the Sha Puddles die, they will not be counted as part of the combat because there is no boss death event following the heals.

In order to fix this, the Purified buff gain should probably be counted as a potential ending combat event and be allowed to extend the range of the combat.

[Killshot]

World of Logs sets combat ranges based off damaging events (and probably enemy deaths as well). Healing does not extend the range of a combat, and Immerseus doesn't die, so if he doesn't re-emerge, the final events of the combat will be the damage done to the last Sha Puddle. Therefore if the final points of corruption come from heals after all the Sha Puddles die, they will not be counted as part of the combat because there is no boss death event following the heals.

In order to fix this, the Purified buff gain should probably be counted as a potential ending combat event and be allowed to extend the range of the combat.

I have a copy of those logs and there's no other damage/heal events past those you see on WoL. Yes, that means those logs ends with 94 and 92 corruption respectively.

Healing does not extend the range of a combat

This is completely wrong and breaks my Iron Juggernaut reports (see above).

[Kihra]

I have a copy of those logs and there's no other damage/heal events past those you see on WoL. Yes, that means those logs ends with 94 and 92 corruption respectively.

They're in another language so I can't really verify. If you're using log browser time ranges, though, remember those only have second precision and can extend outside the actual range of the combat. It's possible I have the terminating condition (< 4 corruption) wrong, though, and that he may give up at a higher level, e.g., 8.

Healing does not extend the range of a combat

This is completely wrong and breaks my Iron Juggernaut reports (see above).

It's a tough problem. You can't really count ticking DoT damage or heals as extending combat, because those things can and do occur after a combat has ended. You also can't easily tell you're looking at the same boss without actually caching the "unique instance" component of the GUID (which WoL probably didn't save to conserve space) and/or looking at the mob health (which you can only do if you add in support for the new HP values added in 5.2).

In the case of Iron Juggernaut, stopping all damage completely for a full minute is kind of silly, so I don't really think it matters whether or not WOL handles that degenerate case correctly.

[Killshot]

It's a tough problem. You can't really count ticking DoT damage or heals as extending combat, because those things can and do occur after a combat has ended. You also can't easily tell you're looking at the same boss without actually caching the "unique instance" component of the GUID (which WoL probably didn't save to conserve space) and/or looking at the mob health (which you can only do if you add in support for the new HP values added in 5.2).

I don't see a single reason why Seismic Activity can't extend combat. Boss has GUID and you can easily verify it's same boss damaging you.

In the case of Iron Juggernaut, stopping all damage completely for a full minute is kind of silly, so I don't really think it matters whether or not WOL handles that degenerate case correctly.

That's very common 10 man strat for Iron Juggernaut HC. Better be safe when you have enough DPS to beat it.

[Kihra]

I don't see a single reason why Seismic Activity can't extend combat. Boss has GUID and you can easily verify it's same boss damaging you.

Yeah, that would work. Requires special case Iron Juggernaut code, but should work. If nobody is taking damage, then you'd have to track him gaining the buff and stay in combat until the buff fades. If he despawns on a wipe, though, it might not fade.

Really it's just ridiculous that Blizzard hasn't provided events for fight boundaries. The fact that so much code has to be written to figure all this out is so dumb, and it's entirely Blizzard's fault.

[Liquidsteel]

Immerseus heroic wipes being logged as kills. I know you're aware of this, just posting my logs to see if it helps. We had 10ish wipes before the kill, but half of our attempts are marked as kills, inflating ranks.

http://www.worldoflogs.com/reports/2z5e8r467wq0i8dg/

Also, are there any plans to separate flex and normal ranks?