Joomla! 1.5 WoW Progress Tracker 3.0 update

Details
Published on Sunday, 07 November 2010 14:08

Dear World of Warcraft raiders

I was once emailed by one of you who bought the extension sending me the code to insert the Lich King in the heroic modes of Icecrown Citadel. I thanked him, but I was not sure the entire module worked as intended with heroic modes. Unfortunately I saw there were systematic errors when an achievement was done in heroic mode, as the normal one is "inglobated" in the new one.

I thus decided to completely rewrite the extension core, and that drove me crazy! Eventually I came up I couldn't automatize all the process, and thus I made separated files for each progress. This lead me to think to optimize the code too, and now you've got a faster and smaller* extension! I stress-tested locally with one player and the execution time was under the half of a second (but the one-per-day download of the XML files), pretty good, isn't it?

The next step is to create a Joomla! component page where to know more in detail the progress, player per player. It will be included in version 4.x, and the price will rise up a little (up to 3.47€). Of course, who has bought the extension won't have to pay the difference, all the updates are for free!

 

I invite you to download the extension again, and while you can upgrade the module as allways, please uninstall the component before upgrading it (there may be some files outdated and unused anymore).

*smaller: being split in different files, the component will only call for the single progress part, reducing the execution time!

 

Cheers and good raiding!

WoW Progress Tracker and patch 4.0.1

Details
Published on Wednesday, 13 October 2010 15:53

[dropcap cap="D"]ear friends and customers,
while the armory is offline, I'd suggest you to keep the module disabled, as elsewise you may run in some parsing errors. If you didn't turn off it, please disable it untill the armory turns back and delete the characters/guild folders in the root of the site. In this way you'll force the update of the XML files.[/dropcap]

~elegos

Joomla! 1.5 WoW Progress Tracker 2.5.3 update

Details
Published on Tuesday, 07 September 2010 18:29

Hello again!

I'm sorry for the time you've waited, but I was away from home and didn't have the instruments to work on WoW Progress Tracker, even if I've allways replied to all the support emails you've sent to me!

This update fixes the ICC25 Hard Mode tracker (it was just a typo I've found), I'm sorry for all the ones who got it broken! As of the Lich King in Heroic Mode, I still have to think how to implement it, as the meta-achievement doesn't include the Lich King death in heroic mode, and the single achievement appears only when the normal one has been achieved. The problem is that if the achievement is not found, it's considered done due to the 2.5.2 update... I'm starting thinking there is no actual workaround to make the system digest these exceptions (trackers are just variables sent to the main processing method), I'll update you if I find anything to do that!

Other people asked me to add the Ruby Sanctum tracker and I'll reply here too just to make it public: there is no need of a RS tracker, as it's just a stupid switch "done - not done", 0-100%, there is no progress at all.

 

Cheers and good raiding!

Joomla! 1.5 WoW Progress Tracker 2.5.2 update

Details
Published on Friday, 20 August 2010 12:39

Hello again!

This time I've fixed a Blizzard bug (or at least this is how I call it!). I've discovered that when there are two different achievements with the same name, for normal and heroic versions, once the latter one has been completed, the former will be literally deleted. This caused of course some troubles with my tracker, but it's now fully operating again!

Joomla! 1.5 WoW Progress Tracker 2.5 update

Details
Published on Thursday, 12 August 2010 13:19

Dear followers,

I'm sorry for the problem found in my WoW Progress Tracker extension about the heroic modes. I've worked hard to find out the bug and I eventually rewrote part of the code to better debug it in the future. The problem should now be fixed, enjoy :)