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.
First identification of the export <Version 1.4> make inport without Error.
It is only import test. Dont know what happend after.
After i update your RT around wersion 2.1.xx and 2.2 Have problem with inport into web page. Page say Invalid DKP string.
In options have EQdkp1.1/eqdkp pluggin. Where is problem?!
What I need for everyone is waht system you are importing into and what import plugin, need to knwo the names, and wehat you used to export wiht to get it ther and what format you chose form that to do it. For example tell me things like: "I used CT Raid - Eris Fork, raided and worked during BC, exportign wiht ML 1.5 into blah blah site using ML import 1.x. It stoped workig wotlk and her is what it does... and i tried these things..." or "I used NRT exporting wotlk wiht CT Raid Tracker export format until xxx, eqdkp plus on xxx site with xx importer." Just ell me what and where and i fix...
- met criteria for version 2.2
which is working through rewrites of certain portions of the code not yet
had a decent pass, WotLK data workable, stable features, and various
enhancements too many to count along the way.
- tons of UI cleanup, fixes and polish mostly with the lower detail views and
all of the lists
- worked through most of the list building, sorting and attendee gathering,
should be much faster and more solid
- added player name to dialogs for cost and count
- added ability to set guildie rank thresh-hold for log guildies in options
can choose off, all, or rank dynamically built when opening options,
of the actual ranks in your guild. choosing a rank means will add players
at that rank or higher but not below.
- cleaned up and enhanced item options UI
now shows layers of items, defaults at the bottom, saved items in middle
and new unsaved items at the top, layered alphabetically. a lot work went
in as well to making much use-able. you can also now get to the Item
Option by left clicking on an icon in the lists. This should make some
peoples lives much easier doing excludes
- completed UI rework for item icons and lists
links, special keys, pastes, dress up, loading non-cached, cursor icon,
blending line highlights and pass through hits, etc.. all there now
they are also the right size so not as distorted
- db update for cleaning DB for null joins and leaves.
- fixed bad void crystal ID for default item options
- fix for XML instance data
- Ok I'm going to stop, lots more, Enjoy :)
I've been using CTRT for, well, years and I've been looking for an updated version for some time.
Are there any notable exclusions that CTRT had that this mod does not?
Anything spectacular that this mod does that CTRT does not?
Specifically, for a user that's ridiculously comfortable with CTRT, what's the transition to using this mod going to be like?
CTRT is still working for me (for the most part), but I know it isn't being updated and so would like to pre-emptively find a replacement. From the looks of the descriptions this might be a winner, but there's no screenshots!
Celess, you seem to be actively responding here, I hope I hear from you =)
Also welcome to any user comments!
Thanks
Example:
Agarious (race: Unknown, class: Unknown, level: Unknown, rank: None) was updated to (race: Unknown, class: Unknown, level: Unknown, rank: None)
Aiurr (race: Unknown, class: Unknown, level: Unknown, rank: None) was updated to (race: Unknown, class: Unknown, level: Unknown, rank: None)
Using CT_RaidTracker Plugin for EQdkp 1.16.13 and RaidTracker 2.1.32, any suggestions? The option "Player Detail" is checked in the options.
While I have your attention though I would like to make a feature request that I think many people would love - for logging guildies on boss kills, etc, could you create an option where we could exclude certain ranks?
For example, my guild has a rank called "Casual Town" for retired raiders that obviously don't get DKP or attendance.
Here is what I think atm for dkp importers (if i were king for a day):
1) make a universal eqdkp major rev 1.1
a) all it does is change format to 123344567 timestamp instead of 12/3/99 12:23:34 date strings. Its one of the only base differnces for eqdkp and all the other verions and all working all dkp imports are converting the time strings to timestamps on the server side as they import anyway. Id be more than happy to take the eqdkp 1.0 exactly as is and declare, as any good heritic would, that this is the official eqdkp modern world baseline just so that the pooor importer script writers have a place to say see... here is one, can i make import for it? can tell them its MUCH faster cause it is and less cpu time, far less. The DB in this RT went to timestamps long time ago, people with over 500 raids in their db proly noticed near instant views and detail frame updates vs like 1-10 minute long ones when they switched to this one. I dont mind being the bad guy, cause the is not DKP board of directors and whatever to do this otherwise. Also as baseline guarentee at least from this RT that all times are server time. Because in this RT DB they are, which means takes away problem that anyone in guild or on the server coud do import and would match times. That is in this RT as well.
2) all curretnly maintained import scripts (eq and ml derivatives):
a) use the < instance > tag I added, Main driver atm being using the diffuculty detection for 10 vs 25 man raids for wow. Fields of <instance> are: name, id, reset, difficulty, which can be on any xml field, like log start, events, items. This gives you lots to play with and things in the instance tag are guarenteed to be non-localized and coherent (they are together matching values guraenteed to have meaning together as a whole, to coherently represent the same thing). This tag is on events and log starts in this RT for any new raids guarenteed. They put what they can, missign values are allowed, but whats ther is guarenteed to be coherent and follow the rules.
-< difficulty >: if the tag is there use it. Basing on the name was never enough, and takes work away form your side. It tells you 10 or 25 man heroic or not in wow, and no reason you couldn't apply this to any game besides wow. Difficuty > 1 on a raid instance is 25 man in wow.
- < name >/< id >: The reason for this is that so many programs put localized strings in the xml or the < instanceid > could mean anyting. This is guarenteed to be non-localized form of the instance name. For this RT, the DB captures non-localazed DB elements always for everyting, so you get that by default, but gives otehrs who export otehrwsie a chance to say "hey, here is where i stuffed the thing you need realy". It also guarentees in this case a unique raid id so that you can put together one raid no matter how is split up in the logs and hwo many pieces you get, and is why events are doped with this tag as well.
b) attendee snapshots, like the instance tag, are attendee snapshots and can be placed on anyting. They can include anyone on server potentialy, and guildies. Time in raid (for those who use that for dkp) is already in the data in adding up the joins and leaves for a particular player, but only for those in the raid. I'm in no way ever here to say that you do dkp one way or other, but im just tryng to make some common way for you to get the data to do whatever. Jsut sayign seprate the two pools of data cleanly, ntoa chack cause it makign a mess. I fyou want the raid to treat guildies of a certain rank as though they were a part of the raid to get their time online to be avilable for a slot as a fill then that works, i coudl add that too. And the snap shot on boss kill as a guildie is separate thing. Whoudl anyoen have a prob having thise two distict classes. Presence on an event based and tiem based as two separate thigns, and hwo they roll into theexport is its own issue?