Rarity
NEW: 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.
In reply to pokettz:
Well, not all bosses use the same method of detection. Rukhmar would be using combat log events, while Sharkbait is tracked by looting the NPC. Others use kill statistics from Blizzard.
Without a discernible pattern or additional information/a way to reproduce, hard to debug.
In reply to Cakechart: I'm not sure it helps but I do think I was wrong about how the attempts were going up. I do now believe that it was entering and exiting combat that was raising the attempt counts, in every instance. Either way I am now just reloading my UI after every mount attempt to stop the count from increasing incorrectly. Thanks for looking into it.
In reply to pokettz:
I've created this issue to track the status, just in case it can be reproduced:
* https://github.com/WowRarity/Rarity/issues/743
I notice Crispin is missing! I dunno what possessed me to boop that shaman anyway!
https://www.wowhead.com/item=129175/crispin
In reply to Bananafana:
The item has a drop rate of 95% (according to wowhead). There's probably no point in tracking it.
In reply to Cakechart: Are there many others like that? I've been using the tooltip to decide whether to go for a mob or not, so maybe I've been missing things.
In reply to Bananafana:
Probably? For completionist efforts, I'd recommend installing AllTheThings.
Hi, is there any reason Rei Lun, who drops the Pristine Cloud Serpent Scale which can be used to purchase the Rajani Warserpent isn't available to track on this addon?
In reply to Deltrus:
That item is already part of the database, but it's in the "Toys and Items" category: https://github.com/WowRarity/Rarity/blob/a8606072dadf1e1438734f6a2dca401a0d4263fa/DB/Toys/BattleForAzeroth.lua#L648
I ended up doing the same, and so far it appears to be working alright, minus the HUGE pause to the game about 5 minutes after logging in.
Not sure if it's the cause for Quantum Courser not being tracked but the Statistic ID attached to it is the kill from Chrono-Lord Deios in Uldaman, not the one from DoTI.
In reply to osum:
Indeed... nice catch. That would explain why tracking no longer works. Will fix shortly.
In reply to Cakechart: I got the new version and it's still not tracking it. I've been running it at low M+ keys and it's still not updating. I've tried to comment it out and track it Custom but it's still not counting. Weird.
In reply to osum:
Not weird at all. Since there's no kill statistic for the "right" version of the boss, Rarity is once again using the NPC ID to detect loot events. Unfortunately, that only works in regular Mythic dungeons and can't be used to track Mythic+.
It might be possible to detect keystone completions somehow, but since I can't test that ingame someone would have to provide an event log. You can enable it via `/etrace` ingame (only capture the end of the M+ run and ideally the chest being opened, separately) and submit this here or in the Discord if you want me to take a look.
Alternatively, there may be other addons that track M+ completion which would allow me to copy the code, but I haven't looked into that yet (and I still can't test it myself).
---
I've created another issue to track the M+ detection: https://github.com/WowRarity/Rarity/issues/713
In reply to Cakechart:
I can get you the log but I'm not sure it's worth doing. The season ends next week and we can't farm M+ for that loot anymore after that.
In reply to Cakechart: Hi! I'm not the sharpest spoon in the drawer but when I ran /etrace I don't know how to export it out of the window it came out of to here.
In reply to Cakechart: Yeah that fixed it! but the next issue is the repeatable setting, i got one and it reset to 0 and luckily got another one on the next run, then said I got it on my first try
The repeatable setting is checked
No errors, ill have to figure it out which addon is doing it one by one but it still only happens when i edit rarity numbers
Plus, quantum courser tracking is still not working. Have to edit the attempts manually
It seems Rarity causes a noticeable 1-2 second screen freeze around 4 minutes after logging in every time. This despite a pretty high-end system I'm running. I'm assuming it's due to this in Core.lua:
self:ScheduleTimer(function()
self:ScanCalendar("FINAL INIT")
Rarity.Collections:ScanExistingItems("FINAL INIT")
Rarity.GUI:UpdateText()
end, 240)
Any way to spread out some those initializations to avoid that large load all at once causing a hiccup?
Thanks
EDIT: For what it's worth, I commented out the ScanCalendar and ScanExistingItems lines there, and that resolved it. Not sure if that's going to break things, but seems to be working ok so far. :)
In reply to gaviin1242:
I suspect that the culprit is Blizzard's API taking too long to return here. You'd have to track down the Lua API functions that are ultimately called in order to be certain, of course, but I remember encountering this issue in the past. Rarity already spreads out the initialization routines, but if the client needs to load Blizzard addons (like Blizzard_Collections), this might still take a relatively long time with no way of preventing the delay.