Rarity
NEW:
- Support for Cataclysm Classic (experimental)
- Rarity now has a Discord server!
If you're interested in following the development process or contributing, you should also check out the official GitHub repository. We're always in need of more hands to help us make the addon better!
Rarity tracks how many times you've tried to obtain various rare items like mounts, battle pets, and toys. It will tell you how likely you are to obtain the item, track how long you've been farming for it, and tell you how lucky you've been so far. Although it's mostly used for mounts, battle pets, and toys, it supports pretty much any item, including profession patterns, archaeology projects, and more.
Looking for Rarity Item Packs? Click here.
Out of the box, Rarity includes support for every single mount, battle pet, and toy in the game which require some time to farm. It also includes support for some mount-related items like Skyshard, Primal Egg, and Giant Dinosaur Bone. It'll even notice if you mouseover a Mysterious Camel Figurine, plus lots of other stuff. Rarity factors in the size of a typical group when determining probabilities, and can also tell you if you've killed various bosses this week (or day). Holiday just started, and you didn't notice? Rarity will give you a helpful reminder to run those holiday dungeons or daily quests if you still need an item from them.
If Rarity doesn't track something you want to track, you can add it yourself! Just about everything is user configurable.
Curious what math is going on behind the scenes? The author of Bunny Hunter created the original algorithms. He wrote an article about it here. Your chance to obtain an item doesn't increase as you farm it; Rarity is just telling you how lucky you've been so far. It can be remarkably cathartic to see a progress bar move up as you spend hours upon hours trying for that Disgusting Oozeling.
Main features
- Rarity is primarily an LDB feed with a large tooltip. It can function as either a mini-map icon (you have to turn this on in the options), or as a standard LDB feed (use a display like Fortress, Button Bin, Titan Panel, or Chocolate Bar).
- Provides a progress bar, which you can toggle by clicking the icon or feed label.
- Adds info to NPC and item tooltips, showing you if it drops or contains something that Rarity tracks. Rare mobs with a guaranteed drop show which item they drop and if you've defeated them yet.
- Includes full source info, telling you how to obtain everything Rarity tracks.
Other features
- Share packs of items with other users
- Can automatically add waypoints to TomTom for certain items
- Uses statistics whenever possible to keep track of attempts
- Breaks your farming down by session, day, week, and month
- Looks at your instance locks to see if you've defeated various bosses recently
- Reminds you if you need to farm a holiday dungeon or daily quest, and hides holiday items that aren't available right now
- Supports bonus coin rolls
- Automatically screenshots when you obtain an item
- Keeps track of rare achievements like Frostbitten and Glorious
- You can add your own items to track
- Lets you modify your attempt count without having to edit saved variables
- Automatically imports data from Bunny Hunter if you're switching
Slash Commands
Simply typing /rarity should open the options menu (unless disabled).
For troubleshooting issues:
- /rarity dump displays the most recent debug log entries (even if the debug mode is disabled)
- /rarity validate checks the consistency of your item database, including custom items (experimental)
Comments & bug reports
Help translate Rarity
Click here to help translate Rarity into your language.
Frequently Asked Questions
Click here to read the Frequently Asked Questions. Please read this before requesting support.
I am having issues with Rarity tracking the kills of Nalak and Galleon. When I kill them and bonus coin, half the time the tracker doesn't increase automatically, sometimes it does. It will list them as Defeated for that character but it wont increase the attempts counter half the time. It can get a little frustrating.
I have a feeling this may be due to sometimes being stuck in combat after the boss is defeated, typically with Galleon as combat does not drop until about 20secs after Galleon dies due to the Sauroks running away. Sometimes with Nalak you're stuck in combat with the opposite faction and/or the Shado-Pan Guards. As the attempts counter only seems to add the kills as soon as combat drops, if you're stuck in combat shortly after maybe that confuses it? Typically I hearth straight away, often while still in combat, which may also be screwing with the tracker as the attempts counter does not increase as soon as I reach my garrison. Not sure what the exact cause is but it definitely hasn't been tracking those 2 correctly for a while now.
I've been doing those weekly for a long time now and it's always worked for me. I also get stuck in combat after Galleon, but I've never hearthed while in combat. Regardless, it shouldn't affect it. Here's how it works: any time you leave combat with anything at all, Rarity scans your statistics to see if any of them went up. If so, it counts an attempt for that thing. Now sometimes the statistics don't go up right away because Blizzard is slow to update them. So Rarity scans several times after you leave combat: after 2 seconds, 5 seconds, and 10 seconds. It shouldn't matter what zone you're in when that happens. You can test that this works by logging in on another computer with a fresh or out-of-date install of Rarity: give it a couple minutes, but Rarity will eventually detect attempts on a ton of statistics, no matter where in the world you are.
So having just re-tested those two particular bosses this week, and having farmed them myself for over a year, I'm unable to reproduce any unwanted behavior. Detection is working for me. Having also reviewed the code, I'm not able to see or think of any reason why it would be behaving that way. So that means we'll have to narrow down the cause better, somehow.
In order to better debug this, since I can't reproduce, please go into Rarity options and turn Debug Mode on. Complete another attempt on the boss(es) in question and post everything that Rarity prints in the chat log. This should help figure out what's going on, I hope.
Thanks for the reply.
I've already completed all of my Nalak attempts for this week so I'll have to wait until next week to get a debug report. Normally I find that Nalak is the one that has the most problems with the tracking, it just doesn't record the kill and/or bonus coin half the time. So sometimes it works, sometimes not.
Galleon is usually more consistent, but I've definitely noticed that a few times it didn't track it. I've enabed debug mode and will try to get some info for Galleon if I can.
One thing I will mention is that coin detection requires that you use the coin only AFTER Rarity detects the original attempt. With statistics, since they require you going out of combat and sometimes the statistics take a second or two to update from the server, you may be missing some coins. Make sure to get out of combat and wait for Rarity to register the attempt on Nalak or Galleon before using the coin, otherwise it won't count. In practice for me, I never get stuck in combat after Nalak (not sure how you get stuck with the guards, but I'm on a PvE realm). With Galleon, just wait the seconds it takes for combat to drop and then use the coin.
Ok so I just did Nalak with the debug mode on and it did not record the kill. Here's the text that it displayed for me. I noticed when I killed Galleon last week with debug mode on it displayed some extra lines to indicate the kill counter, which are not present below. Hopefully this is helpful.
[17:46:37] Nalak yells: I am but...the darkness...before the storm...
[17:46:37] You receive item: [Stormtouched Cache].
[17:46:37] Rarity: Building initial statistics table
[17:46:37] Rarity: BAG_UPDATE
[17:46:38] <DBM> World Boss - Nalak down! You have 57 total victories.
[17:46:39] Rarity: Scanning calendar (DELAYED INIT)
[17:46:39] Rarity: Scanning toys (DELAYED INIT)
[17:46:43] Rarity: Currency updated (CURRENCY_DISPLAY_UPDATE)
[17:46:43] Rarity: Used coin: Mogu Rune of Fate
[17:46:43] You receive bonus loot: [Leggings of the Chromatic Hydra].
[17:46:43] Rarity: BAG_UPDATE
[17:47:39] Rarity: Scanning calendar (DELAYED INIT)
[17:47:39] Rarity: Scanning toys (DELAYED INIT)
[17:47:52] [1] Changed Channel: [1. General - Garrison]
After all of that there was nothing else to add. I waited on the Isle of Thunder for 30 secs after combat dropped to see if it was original hasty hearthing that affected it, but it seems like it's something else entirely.
Edit: So I just did another attempt on a different alt, and it worked perfectly fine. Here's the debug info below of what text it gave me. As you can see they're completely different. Sometimes it works for Nalak, sometimes it doesn't.
[18:06:10] Nalak yells: I am but...the darkness...before the storm…
[18:06:10] Rarity: New attempt found for Reins of the Thundering Cobalt Cloud Serpent
[18:06:10] Rarity: Allowing this item to be counted again if a coin is used in the next 90 seconds
[18:06:10] You receive item: [Stormtouched Cache].
[18:06:11] Rarity: BAG_UPDATE
[18:06:11] <DBM> World Boss - Nalak down after 2 minutes and 22.94 seconds! Your last kill took 2 minutes and 32.47 seconds and your fastest kill took 32.84 seconds. You have 67 total victories.
[18:06:16] Rarity: Currency updated (CURRENCY_DISPLAY_UPDATE)
[18:06:16] Rarity: Used coin: Mogu Rune of Fate
[18:06:16] Rarity: COIN USE DETECTED FOR AN ITEM
[18:06:16] Rarity: New attempt found for Reins of the Thundering Cobalt Cloud Serpent
[18:06:16] Rarity: Starting a session
[18:06:16] Rarity: Allowing this item to be counted again if a coin is used in the next 90 seconds
[18:07:12] [1] Changed Channel: [1. General - Garrison]
OK I think I found the problem here, thanks to your help. It looks like Rarity actually scans statistics WAY too early upon login, so there is no data. This isn't usually noticed for two reasons: the situation will correct itself after 3 minutes or after you exit combat the first time. Most players will hit one of those two conditions before making an attempt.
But if you logged in, only entered combat with Nalak and nothing else, and killed him less than three minutes after you logged in, Rarity would fail to detect it. This would occur for any statistics-based detection.
I'll get it fixed. Thanks for your help!
Yeah that's actually what I do with my Nalak kills!
I simply park all of my alts there before Tuesday's reset, then approximately each time he's spawned I'll log in, pull him, and kill him. So I wont enter combat with anything else beforehand and sometimes, depending on the alt, he'll die super quickly under the 3min mark of logging in. This would explain why sometimes the kill tracking works and doesn't work.
Thanks for fixing it!
Hello, sorry for the late reply. I was away and then I've been ill. (Deathwing issue blazing drake not tracking after aquiring handmaiden on N25)I just checked on one of my characters on 25man normal and the statistics do go up when I kill him, however the counter doesn't and it still won't even show as "defeated" unless I reload UI or relog. I will try on 10 man aswell.
Update: I have now tried it on 10-man aswell, the same issue is still there (and the statistic still goes up)
In order to better debug this, since I can't reproduce, please go into Rarity options and turn Debug Mode on. Complete another attempt on the boss(es) in question and post everything that Rarity prints in the chat log. This should help figure out what's going on, I hope.
Hello im trying to track Frostdeep Minnow as custom track but cant get any attempts while fishing in my garrison... it works outside the garrison but not inside any ideas how to fix that?
Make sure "Requires pool" is off, and make sure you've filled in the zone correctly.
Hello!
I formatted the PC , the rarity this reset. the rarity will update all previous information ?
Rarity will automatically pick up attempts associated with any Statistics on the first character you log in with. Other than that, you need a backup of the saved variables in order to restore the information.
Great addon if it would work, getting lua errors and when I try to copy over profile settings it also copy my attempts from that character...
Rarity works just fine. Post the error you're getting. Copying attempts when copying your profile is working as intended. You shouldn't be copying your profile, anyway, though. You should put all your characters on the same profile. Don't copy it. Profiles are a relic from when mounts and pets weren't account wide. They're not necessary now.
I created a profile and I did setup all the settings I need on character A. Logging in to Character B and load the profile from character A. Great all settings are fine but not kill attempts :/ Do I need to setup the settings on all my 25 characters? that would take alot of time even worse if it some how got lost in the future.
Date: 2016-01-07 20:50:07
ID: 1
Error occured in: Global
Count: 1
Message: ..\AddOns\Rarity\Core.lua line 2239:
Usage: GetItemInfo(itemID|"name"|"itemlink")
Debug:
(tail call): ?
[C]: ?
Rarity\Core.lua:2239: UpdateText()
Rarity\Core.lua:711: ?()
...oot\Libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:145:
...oot\Libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:145
[string "safecall Dispatcher[3]"]:4:
[string "safecall Dispatcher[3]"]:4
[C]: ?
[string "safecall Dispatcher[3]"]:13: ?()
...oot\Libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:90: Fire()
...rface\AddOns\Bartender4\libs\AceDB-3.0\AceDB-3.0.lua:465: SetProfile()
...artender4\libs\AceDBOptions-3.0\AceDBOptions-3.0.lua:275:
...artender4\libs\AceDBOptions-3.0\AceDBOptions-3.0.lua:274
(tail call): ?
[C]: ?
[string "safecall Dispatcher[3]"]:9:
[string "safecall Dispatcher[3]"]:5
(tail call): ?
...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:794:
...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:614
(tail call): ?
[C]: ?
[string "safecall Dispatcher[3]"]:9:
[string "safecall Dispatcher[3]"]:5
(tail call): ?
...ace\AddOns\Bartender4\libs\AceGUI-3.0\AceGUI-3.0.lua:314: Fire()
...r4\libs\AceGUI-3.0\widgets\AceGUIWidget-DropDown.lua:442:
...r4\libs\AceGUI-3.0\widgets\AceGUIWidget-DropDown.lua:433
(tail call): ?
[C]: ?
[string "safecall Dispatcher[3]"]:9:
[string "safecall Dispatcher[3]"]:5
(tail call): ?
...ace\AddOns\Bartender4\libs\AceGUI-3.0\AceGUI-3.0.lua:314: Fire()
...s\AceGUI-3.0\widgets\AceGUIWidget-DropDown-Items.lua:351:
...s\AceGUI-3.0\widgets\AceGUIWidget-DropDown-Items.lua:341
Locals:
None
AddOns:
Swatter, v5.21e.5566 (SanctimoniousSwamprat)
WowheadLooter, v60013
AchievementsReminder, v
AtlasLoot, vv8.00.70
Babylonian, v5.1.DEV.332(/embedded)
BagBrother, v
Bagnon, v6.2.4
BagnonConfig, v6.2.4
BagnonScrap, v14
Bartender4, v4.6.12
Configator, v5.1.DEV.382(/embedded)
Coordinates, v1.19
CrossRealmAssist, v0.76 beta
DBMCore, v
DBMDefaultSkin, v
DBMGarrisonInvasions, v
DBMStatusBarTimers, v
DebugLib, v5.1.DEV.337(/embedded)
GatherMate2, v1.35.5
HandyNotes, vv1.4.6
HandyNotesDraenorTreasures, v1.16
HandyNotesTimelessIsleChests, v1.13
HandynotesTimelessTreasures, v1.0.2
Informant, v5.21e.5566 (SanctimoniousSwamprat)
IskarAssist, v
LibExtraTip, v5.12.DEV.390(/embedded)
MasterPlanA, vA
MoveAnything, v15.2.9
Postal, v3.5.4
RaidAchievement, v
RaidAchievementOldModules, v
Rarity, v1.0
RarityOptions, v
SavedInstances, v6.2.7
Scrap, v12.24
ScrapOptions, v12.24
Skada, v1.4-32
SlideBar, v5.21e.5566 (SanctimoniousSwamprat)
Stubby, v5.21e.5566 (SanctimoniousSwamprat)
TipHelper, v5.12.DEV.389(/embedded)
TradeSkillMaster, vv3.1.4
TradeSkillMasterAppHelper, vv3.0
TradeSkillMasterAuctioning, vv3.0.3
TradeSkillMasterShopping, vv3.1.1
TradeSkillMasterWoWuction, vv3.0.1
BlizRuntimeLib_enUS v6.2.3.60200 <none>
(ck=515)
You need to put all your characters on the same profile. Pick one character as the "master" and set all the other characters to that profile. Pets and mounts and toys are now cross-account, so it is incorrect to try to count attempts separately between characters.
From the FAQ (http://www.wowace.com/addons/rarity/forum/40930-frequently-asked-questions/#p1):
Can Rarity track cross-account attempts if I farm on multiple characters?
Yes. Rarity can track attempts across all characters on a single World of Warcraft license. It cannot track attempts across multiple licenses within a single Battle.Net account, because World of Warcraft does not permit this.
If you just installed Rarity for the first time, it will automatically track attempts across a single license. You don't need to do anything. If you find that this is not true, follow the directions below.
If you had already used Rarity before patch 5.0, you need to take action in order to enable cross-license tracking. Open your Interface Options and find Rarity in the list. Click on Rarity, then click the + sign that appears. This reveals a new entry called Profile. Click it. Finally, in the Existing Profiles drop-down, select "Default". Warning: This will reset your options and you will lose all existing attempt counts. Some attempts may be repopulated based on the current character's Statistics, but most things will be reset to 0.
"If you just installed Rarity for the first time, it will automatically track attempts across a single license. You don't need to do anything"
fresh install and removed rarity settings from old install. It still does not work. what to do now?
Follow the directions I posted. It tells you what to do.