Completed:
Back-end
(The back-end data parsing is ready to undergo strenuous testing as I receive lua files.)
Data upload and view is based on roster authentication levels.
Default guild setting until raidtracker is guild/realm/locale aware.
Boss/Item data merging

Item Data
Routine for pulling armory item data lookups
Routine for pulling armory item data tooltips

To Do:
Realm Scope Frontend:
View boss kills
View loot drops

Guild Scope Frontend:
View raids
View boss kills
View loot drops
View attendance

Character Scope Frontend:
View loot
View bosses killed

Admin Scope Frontend:
Flag raids/loot/attendants as 'deleted' so data is not displayed. (Actual data deletion will not stop the raid from being uploaded again.)

Current Available Options

General:
Minimum CT Raidtracker version (current disabled)
Global Enable/Disable of Raidtracker
Admin Access Level
Upload Access Level
View Access Level
Active linking to internal roster or the armory
Configurable armory search string (in case it changes)
Date display format
Default timeframe for database pulls (defaults to 90 days)
Images Format (gif/jpg/png)
Images Location
DB transaction enable (in case the mysql struct changes to support it) (currently disabled)

Item Options
Global store items flag (on or off)
Minimum rarity for item storage
Store players per loot (must also be activated in the addon - intensive)
Combine loot - Display option for whether to show single lines per loot or concat all users into one line per unique item. (may be removed)

Raid Options
Expand Raids (start display expanded or not) (may be removed)
Merge raids - Whether to collate raid data or store unique raids if data matching occurs
Store Unknown - Flag to store raids in unknown zones
Store Pre-BC - Flag to store old world raids
Store BC - Flag to store BC raids
Store WLK - Flag to store WLK raids (for expansion)

Attendance Options
Global store attendance flag (on or off)
Leaves - Store player leaves

Boss Options
Global store bosses flag (on or off)
OldWorld Bosses - Flag to store old world bosses
BC Bosses - Flag to store BC bosses
WLK Bosses - Flag to store WLK bosses (for expansion)

Notes and Errata:
* Per-item attendance uses a lot of memory to achieve. There may be more efficient ways to handle this (like in SQL queries). I will research it as soon as I have a working full version.
* Most message strings have been moved to being locale-based for translation.
* A 3meg data file uses approximately 15-16meg of memory to process without per-item attendance tracking enabled. With, the script uses approximately 36meg.
* Data collation currently utilizes two methods for retrieving a "match" raid. Primarily, if the raid shares the same Blizzard raidID, we have a match. For older data, it attempts to match the zone, guild and server names, and the raid date within +/-4 hours of time. (I can make the 4 hours a configurable option if there is a call for it.)
* The number of wipes are recorded, but not the times they occurred. If someone would like the time strings recorded instead, please let me know.

I'm waiting on a couple fixes for the newest MLDKP raid tracker, but I wanted you to know I'm starting to get some more progress done. I'm trying to get it to a point where I can at least release a base for everyone, even if there is no admin section in the beta.

Here's a screen:

Gaxme wrote:I'm waiting on a couple fixes for the newest MLDKP raid tracker, but I wanted you to know I'm starting to get some more progress done. I'm trying to get it to a point where I can at least release a base for everyone, even if there is no admin section in the beta.

Excellent - many thanks for the update. Raid Tracker is crucial for my guild work and it's the only thing stopping me from deploying Roster 2 :-)

What faults are you waiting on? Do you have the links to the mldkp forums?

swampy wrote:Excellent - many thanks for the update. Raid Tracker is crucial for my guild work and it's the only thing stopping me from deploying Roster 2 :-)

What faults are you waiting on? Do you have the links to the mldkp forums?

I still need to verify that the English version (1.5.4) is properly auto-setting zone names and exporting instance IDs into the LUA. It's broken for myself and another user, though I have yet to wipe my raid data out and try fresh with a clean install.

The thread is here: http://www.mldkp.net/smf/index.php/topic,65.150.html

Thanks for any assistance you can give. =)

The backend code I've got written should be able to collate raids without the raid ID, but it sure makes it a lot more efficient.

Eris was nice enough to include the realm in the new output raid struct, so I should be able to make the tracker multi-guild (even multi-realm) aware as well.

Now I'm just thinking out loud...

G.

I've been using the MLDKP Raid Tracker 1.5.4 with the old version of the roster and it's been catching the zone ok (along with zone id). It seems to have been missing occasional bosses I'd expect it to catch, though.

I'll get hold of a freshly generated LUA from a fresh install and throw it your way if it'll help.

That would be nice, just so I can verify that it's my end that's broken. =)

G.

Update on the broken logging. I completely removed 1.5.4, the lua data files and reinstalled 1.5.4, and it appears to have fixed the instanceID and autozone features.

Just thought I'd put that here in case anyone else was having a similar problem.

Work continues on the addon, I really am trying to get a viable version ready for release.

G.

Hi Gaxme !

I know coding is a long work, but any hope we can see your progress soon ?

I want to put roster v2 in prod, but without RaidTracker it's impossible

Thanks for your work

I am so sorry that I have let this lapse as long as I have. I had a few RL issues crop up in the last few months that took my time completely away from the game and coding.

I am thinking that I will release what is done so far, and ask for community help in fixing the display frontend, which is the majority of what is left.

I'll know more in a few days when I can evaluate how much time I have to work on it.

No problem !! RL must be always first !!!!

And yes the community will help on raidtracker for sure

Good luck for RL isssues !