Raid Tracker
Keeps account of attendance, loot and DKP for raids, parties, battlegrounds, arenas and now solo for questing.
Works with SexyMaps, Minimap Button Frame, Titan Panel, FuBar, and others for easy access menus, and a minimap icon if no other manager or bar is installed. Provides export strings for DKP for most popular DKP posting formats. Supports loot filtering via loot options window /rt io, or on the minimap menu.
Chat commands: /rt - main window /rt o - options /rt io - item options /rt help - help /rt hide - hide or show the application icon
Curse site release updates are working normally again. Raid Tracker, Hellbender DKP, Tell Track, AddOn Studio. Use links to get files same as before. Enjoy.
The following error(s) were found :
- item 'Mantle of the Lost Conqueror' wasnt found for this instance.
- item 'Mantle of the Lost Vanquisher' wasnt found for this instance.
- item 'Vest of Vitality' wasnt found for this instance.
- item 'Greaves of Turbulence' wasnt found for this instance.
so im not sure, seems liek them.
When I import DKP using XML outputted by your addon, the import tool retrieves item names and looters properly, but I have to go back in and add each individual DKP value manually ... This is a royal pain.
Thanks and keep up the good work with this great addon overall.
Though, even I changed it like this and had first part of import done (had raid members and drops split), couldnt finish because Insert Raid(s) just returns me to main page (Paste the Log Below). Same happened with older versions (v2.1.23 - 24)
- added Realm to log, and <realm> to eml for all three formats, per CT 1.5.7 feature, exactly hwo it was there. THis Adds the realm name to the log and to the export string. Unless its specifically rejectign XML that is doesnt understnd, which is nto a part of the spec, it shoudl ignore them. Then this shouldnt be a prob.
- changed type 1 and 2 to point at the correct xml script gererator. 0 is eqplugin/mlkp 1.1, 1 is eqdkp unknown, 2 is mldkp 1.5. it was a bug that was in ther for long time that was my fault. what they all generate is very similar, mldkp 1.5 is the most differnt, and parts are very differnt. so... when you picked 0 it went to the gen1 always, when you picked 1 it went to gen2 mldkp 1.5 script, when you picked 2 it went to the gen1 script. the effect was that pickign 2 generated soemting that wasnt really either, since ther are clauses in gen1 script for changing output for 0 and 1 are hard wired in. picking 1 sent it to the mldkp 1.5 gen2 script so pickign 1 was like selectign mldkp 1.5.
If all of these problems are from choosing 0 then that shoudl have been the same. There were a few bug i found tonight, which is what 2.1.28 is about, which have been there whole time and are minor. Thos are:
- 0 wasnt putitng the <version>1.4 tag in like it should have
- 0 was getign <time> for event <bosskill> twice, once as though it was 0 and once as though it was 1, basically <time>11/22/33 44:55:66</time> and <time>1233455678</time> possible that coudl have screwed up a bad parser, and my fault if it tok the second value and trued to parse ti blindly as a string date, if it had no sanity checks. this is fixed to that it does <time>11/22/33 44:55:66</time> for 0 again it has been broken this way a long long time, not new.
This leads to the issue of why take so long to parse a date on the web side. These are all supposed to be EQDKP right? liek 1.4 version ish? from what you can tell, is it supposed to take a string formated date? or a time stamp? If ti takes a formatted date, those are written correctly.
< BossKills >
< key1 >
< name > Bob < / name >
< time > 12/06/08 05:57:31 < / time >
< time > 1228564651 < / time >
0 now does this
< BossKills >
< key1 >
< name > Bob < / name >
< time > 12/06/08 05:57:31 < / time >
Now that
function ConvertTimestringToTimestamp($timestring)
{
$parts = preg_split('/[\/ :]/', $timestring);
return mktime($parts[3], $parts[4], $parts[5], $parts[0], $parts[1], $parts[2]);
}
seems to be choking it at points... I will update everything to most recent version and try doing import tonight to see how it behaves, and post results.
No you dont need fubar. Yes i really diont think about it for the /rt, but proly thought at tiem no one woudl have both sionce this does everytign the otehr does, is jsut updated alot.
Fatal error: Maximum execution time of 30 seconds exceeded in :(
Anyone knows what to do?
Ok I was using CT raid tracker through 3.0 came out then when wrath came out it took a complete crap on me so I'm trying raid tracker the raid is showing up its just not allowing me me export I haad someone else down load it and he said it was working fine do I have to have FUBAR running for this to work properly?