Mizus RaidTracker v0.16-Beta released

Mizus RaidTracker Version 0.16 beta is now available for download. Check the MRT page for the download link.

0.16 Changelog:

New:

  • Added option for changing the slash command. (Please relog after changing)
  • Added option for changing the currency of the text based export formats.

Changes:

  • The RaidLog browser will now save the last selected raid event and boss event (unless new raid/boss events are tracked).
  • The RaidLog browser will now show raid loot, if a raid event but no boss event is selected (the title of the table will change accordingly).
  • Changed localization files for supporting the CurseForge localization system.

Bug Fixes:

  • Fixed boss detection of the horde gunship battle (ICC – untested)

7 thoughts on “Mizus RaidTracker v0.16-Beta released”

  1. I like your raid tracker. I’m pretty close to switching to it full time for tracking raids. I do 10-man raids and don’t use a DKP system.

    It would be nice if the addon could work 100% in the background — probably by enabling/disabling the right features. I’m wondering if it would be possible to auto assign point values to looted items so that window doesn’t popup on each loot.

    Also, is it possible to not ask for role call on each boss kill. This is another one of those things that could just be an automatic options.

    My last suggestion is for support to allow marking the looted item as either “disenchanted” or “bank”. I’m pretty sure it can be done now by hand entering those values, but it would be nice if the addon did it. It would help avoid typos.

    I have a todo for myself to check out the different export features. I’m hoping to export the loot/attendance list to a forum post and use that for inventorying my guild mates participation.

  2. Great addon. Been looking for something to replace HeadCount and I think I’ve found it. Couple of feature requests for you:

    – Reiterating what Kevin said, having an option to mark a piece of loot as Disenchanted or Banked would be great.

    – Having a ‘Note’ field for loot would also be great. In our custom web-based loot tracker, we currently use the Note field on Headcount to specify offspec items and a few other things.

    – Option to use EPGP item costs. The formula they use can be found at epgpweb.com.

  3. Uh, I should check my comment section more often.

    Thank you for your feedback. It’s always appreciated. So, I will try to answer each point.

    It should be already possible for MRT to work in the background. Just uncheck the “Ask for item cost” checkbox in the option menu (tracking options). MRT will still track the items, but will set item cost to 0. Maybe I should add an option to print a little chat message if an item was tracked. If the person who get the loot is too far away and there is no loot message in your local client, the tracker can’t track the loot.

    Regarding the point about auto assigning loot cost – can you describe on which basis you might want to see it implemented? Should it be on a per slot base (e.g. neck, wrist cost 20, weapon 30, wand 10) or an item level base or really a per item base (where you have to preassign a value to each item)?

    Regarding the role call (I guess you mean the attendance check after a boss kill) – I will put that on my ToDo-list. Will probably implemented as an extra option in the next version.

    Regarding the point about marking looted items – the loot window popup already (should) has two buttons for setting the item recipient to “Bank” or “disenchanted” – so i’m not quite sure what you mean. Would you like to see a set of extra buttons in the raidlog browser? Or some kind of an editable item list for setting items automatically as “Bank” or “disenchanted”? Or something completly different?

    Regarding a ‘Note’ field – implementing an extra field in the loot popup window should be rather easy, but I think I start to run out of place in the raidlog browser. I have a solution in mind but this will require a bit of coding and testing before i am sure that it can work. So, I can’t promise anything if and when this will be implemented.

    I took a look at the EPGP system. There are few cases which can’t be decided automatically (Is a weapon used as MH or OH? / Is a weapon used for tanking?), the rest seems quite easy. I will add it to my ToDo-list, but it may take a while before I’ve created a usable UI for handling these cases.

  4. EPGP – The way EPGP handles the situations where it could be one of two values is to write it as “XXX or YYY” in the input field and then let the user decide which value to keep.

    Also, on exporting — I noticed some weird things with the and times. On our Heroic LK kill the other day, calculating total attendance via Joins and Leaves came to 20 seconds for every raider. It should have been a little over an hour for most and definitely not the same for everyone. The day after on Heroic Halion it gave a total attendance of 0 seconds (Join and Leave at exactly the same time).

    I don’t know what your goal is in terms of tracking attendance on the export, but my assumption would be that every time a raider joined the raid there would be a in the export, and every time a raider left the raid there would be a . Additionally, if “Track Offline Players” was not enabled, a Join and Leave whenever they logged off or on as needed.

    If my assumptions are wrong, please let me know. To me, the main point of running a tracker of this nature is to get by-the-minute information on attendance. If the granularity is reduced to just boss attendance, the appeal of the mod is greatly diminished for me.

  5. One more bug — it looks like Shadowfrost Shards are being tracked twice. When it’s looted, it’s getting tracked but triggers the “out-of-range” manual loot add which ends up adding it a second time to the tracker.

    Also, not sure what happened to my above post. Looks like Join and Leave were filtered out from my post anytime they were in lower case. Very strange.

  6. Uh – um, now you confuses me. There is no “out-of-range” manual loot add as of yet. On the other side, I’ve found a bug, which may enable previously disabled options. But I’m still not sure, how this could effect the Shadowfrost Shards. Can you double check if it’s not a second raid tracker, which tracks something.

    Because of the options bug, I’ll push out a new version earlier than planned. If this “double tracking of items” bug still exist, then please send me a copy of your “MizusRaidTracker.lua”, which can be found in your WoW directory under “WTF\Account\YOUR_ACCOUNT_NAME_HERE\SavedVariables\”. E-Mail address is shadnix@arcor.de

Leave a Reply

Your email address will not be published. Required fields are marked *

 

This site uses Akismet to reduce spam. Learn how your comment data is processed.