Page 1 of 4

Latest Changes

PostPosted: Sun Dec 19, 2010 6:36 pm
by Miles
  • The new talent trees are added, so all the specs should be detected correctly now. If you have a kill where the spec is set to unknown, poke me.
  • Fixed the Twilight Ascendant Council kill condition.

It will take some time until all the reports are reindexed, the rankings and stats will be inaccurate until then.

Recent Changes

PostPosted: Tue Dec 28, 2010 6:33 pm
by Miles
Hi, welcome to the Cataclysm version of this thread :)


* As you have noticed, the new raid bosses have been added already, but the heroic mode detection is still work in progress. The fight validator is also not active yet.
* The new talent detection code is live, poke me if you have a report with unknown specs.
* The shield healing code uses the amount remaining field in the SPELL_AURA_* events now, so the tracking should match any other source exactly for any 4.0+ logs. I haven't manually verified it against other analyzers yet, but it matches the manual count exactly.
* To see which build/feature level the parser is using, check the footer for the version number. v13329 is the 4.0+ parser, v10192 is the previous one with the crit-ticks addition.


That seems to be it for now - the rest is still in the todo queue.

Re: Latest Changes

PostPosted: Sun Jan 02, 2011 3:16 pm
by Maihem
Validation limits have been calculated and applied for the Cataclysm raid instances as far as data is available.

If your fights are marked invalid, check the Ranking Info page to see why.

Post in the forums or PM me or Miles if you think your fight is flagged incorrectly.

Re: Latest Changes

PostPosted: Mon Jan 03, 2011 5:53 pm
by Maihem
Detection for heroic Halfus Wyrmbreaker as well as Twilight Ascendant Council has been implemented. Reports containing these encounters are in the process of being re-exported.

Damage/healing done/taken, actor details and ranking pages showed incorrect numbers as partial absorbs and shielding were processed incorrectly. This has been fixed and the numbers should now be consistent with those on the analyze pages. Rankings will be updated later today.

Re: Latest Changes

PostPosted: Wed Jan 05, 2011 7:21 pm
by Maihem
We've just pushed an update that fixes the following issues:

  • (Live Cata reports only) Incorrect shield value (way too low) calculation (no remainingPoints value for shield SPELL_AURA_* events).
    Rankings will be recalculated somewhere during the next few days.

  • (Cata reports only) Reports containing the UNIT_DISSIPATES event cause an HTTP 500 Internal Server Error.
    New as well as existing reports now work correctly.

Re: Latest Changes

PostPosted: Mon Jan 10, 2011 6:33 pm
by Maihem
The Report List page now hides deleted and purged reports by default. A (show deleted) link was added to toggle this behavior.

Re: Latest Changes

PostPosted: Mon Jan 17, 2011 9:02 pm
by Maihem
Heroic detection has been implemented for the following encounters:

  • Blackwing Descent
    • Magmaw
    • Omnotron Defense System
    • Maloriak
    • Atramedes
    • Chimaeron
    • Nefarian
  • The Bastion of Twilight
    • Halfus Wyrmbreaker (was already implemented)
    • Valiona & Theralion

A big *thank you* to ArcaneMagus as well as seriallos for providing spell data as well as links to heroic reports!

Re: Latest Changes

PostPosted: Tue Jan 18, 2011 3:57 pm
by Maihem
Boss mechanics have been adjusted to properly link Onyxia with the Nefarian encounter. The Nefarian encounter should now start when Onyxia is sighted.

Re: Latest Changes

PostPosted: Sat Jan 29, 2011 6:58 pm
by Maihem
Added heroic detection for Tot4W: Conclave of Wind. Recrawling 35k reports as we speak, all should be updated tomorrow by noon. Any report manually visited will be updated instantly.

Re: Latest Changes

PostPosted: Wed Feb 09, 2011 12:09 pm
by Miles
Not really a WoL change, but a setup change. mod_wsgi has worked quite well for ages, but for some reason, it "just" dies in the middle of the night causing all kinds of trouble - most notable a 50% response failure rate with 2 frontends.

I've changed the load balancer config to workaround this for now, it should mark failed servers as gone and ignore them until an admin can revive it again. A 99.835/836% uptime (last 7/31 days) is just not good enough.