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.
I do have an issue which is maybe answered in the thread, but my searching didn't give any results, so with the risk of getting flamed I want to ask the following question.
We use the MLDKP 1.5 plugin to import the string but with version 2.1.22 (and earlier with 2.1.21) I do not get a string while trying to export. The 'Unknown EQDKP' setting does generate a string but can not be imported in our system. Either I am missing a very important point or something is wrong. Any help is very welcome and sorry if I'm being a dork here.
[2008/12/08 02:54:03-129-x1]: RaidTracker-2.1.22\Export.lua:209: bad argument #1 to 'pairs' (table expected, got boolean)
RaidTracker-2.1.22\Export.lua:209: in function <Interface\AddOns\RaidTracker\Export.lua:153>
(tail call): ?:
RaidTracker-2.1.22\UI_Dialog.lua:92: in function `Edit_OnShow'
<string>:"*:OnShow":1: in function <[string "*:OnShow"]:1>
<in C code>: in function `Show'
RaidTracker-2.1.22\UI_Dialog.lua:18: in function `Show'
RaidTracker-2.1.22\UI_Button.lua:89: in function `Menu_OnClick'
RaidTracker-2.1.22\UI_Button.lua:6: in function `func'
Interface\FrameXML\UIDropDownMenu.lua:568: in function `UIDropDownMenuButton_OnClick':
<string>:"*:OnClick":1: in function <[string "*:OnClick"]:1>
---
Let me know if you need any more information!
On 12/3 we went to The Obsidian Sanctum and then after to Naxx 25. v2.1.22 is showing the date as 12/4, no Sarthrion kill but the time shows both runs.
Mailed log over the weekend
setting is currently @all on boss kill
- fixed menu to go 4 levels for picking bosses, much nicer
- cleaned up drop-down menus
- added first pass bosses for WotLK
- added missing world bosses first pass
- cleaned up kill event code
- added original encounter exceptions back (RnJ, etc...)
- made fully functional test zone teldrassil if you want to see effect of options
for some reason before going on a raid, teldrassil is the instance, and
Nightsaber Stalkers are the bosses, why should i just get to play :)
- updated/fixed zone changes so that the display updates correctly if not in a
raid log session, also should pick up subzones and other zone changes that have
never ever worked before raid or no raid.
- fixed so that ANY boss that was in any list, includign the new ones in the drop
downs, that wasnt already mapped to an event, get used as triggers.
- boss kills that are triggerable will also trigger a new log session
if not already started and auto create for the group type is on, see bleow
this puts a boss kill on parity with looting, otherwise you miss the event but
get the boss loot record which was historicaly bad, and fun side affect is that
if you down a classic world boss solo with autosolo on, you get to record it
otherwise forget, mostly it makes this consistant.
- enhanced the autocreate for Raids, Parties, BGs, Arenas and Solo.
rules are better, was never realy complete before looking at it.
rules are (assumign you have it turned on for a particular type):
raid,bg: if in a raid/bg and at least one player then create
party,arena: in party/arena and at least 2 players create
solo: not auto create based on group changes
all: if no log is started and 1) loot drops or 2) a boss kill event then create,
and loot must be above log threshhold
this one enables autocreate for solo, it wil start on first loot
this wil nto fire for /rt additem which depends on selected raid, if you were worried
- still to be worked through is how better Auto will affect raid log end
this is a tricky one because differnt people want diff things, ill work something out.
- tooltips are purged if you have over 20 raid logs, see below
- user custom zones that match zones that exist in defaults were removed
many zones have been added, this shoudl actually be nice for people that have had
RT for very long tiem as well and feel stuck with them, the rules for it removing
it you remove a zone from a raid manually were very cumbersome, remove one and you
remove it form the list, this is no longer the case.
- Default for AutoParty is now 2 (AutoCreate), see above
mostly this is because ther are a huge number of people wanting this to work
for 5 mans since is now a feature, if was already set then it wont change it,
only if its never been set.
- Default for AutoEvent is now 2 (On Kill), see below
- Default for TimeFormat is now 0 (12 hour time), see below, this wont affect DKP
- reset options for TimeSync, TimeFormat, TimeZone, LevelMax, SaveTooltips, DebugMode
back to defaults, and AutoEvent if set to 1 (on mouse-over).
in reading the below sections, its important to remember that some have had
some form of RaidTracker for over 2 or 3 years. previous upgrades handled most
of the transitions, but this give some a fresh start and fixes issues.
- TimeSync is gone, not needed anymore, all time is saved game time and
the sync form local time to game time is automatic now, all db time values
are inherently 24 hour saved as seconds since epoch, so DKP is fine.
in a nutshell all db time is 24 hour sever time, display time will be 12 hour
where appropriate. some users were getting robbed not getting to see 12 hour
time when the reason they set ti was historically needed to save db values for
DKP, users who had really old settings.
- TimeFormat: see above
- TimeZone still works but not needed for DB would only be for display, again
this should be nice to remove this for almost everyone, the default is 0 hours.
the original reason it was set was for DKP in the DB which see above no longer
needed.
- LevelMax: this is a DKP export setting, this ensures every starts at 80 now
just in case. it was configured with a previous scheme update if it was 70,
make it 80, but users who had it at 67 for some reason will fail DKP
- SaveToolTips: tooltips are purged if you have over 20 raid logs, these take a
huge amount of space and are useful only for perusal in the DB file, they are
not used by DKP or RaidTracker. they are help for manual DKP fix-ups or just
fun or curiosity. not functional part of RT.
- DebugMode: purged in case some don't understand enough to turn it off, but
have been suffering the output, if it was set some long time
- Since the Event kill mechanism is working again after very long time, and
the only way to queue next loot boss was mouse-over, this ensures that
everyone will get a chance to get proper boss kill targets, the mouse over is
a much more user aware option and not as solid as checking the same things
on kill. is special purpose usually.
One thing i want is feeback on dkp strings and uploads, who is using what system, waht sites and whats workign and not. And thank you fro those who have sent DBs to me, those help waaay more than you know. Soem localization help woudl be nice too for the functional strings.
- fixed db update schema issue
- added wow 2.4 event processing for unit death
events on boss kill should work again
- fixed issue with lookups not processing: player leaves, loot receives
- moved nax bosses to the new nax
Evetns for loot, playerleave shoudl be workign again now with 2.1.21. Thanks to Crazytoo for sending me thier database, can thank him for his help adn having this fix.
FYI I emailed my lua.