WowAce

I'll need more information. Is the addon loaded? Does typing /rarity open the options menu? It sounds like that part works but some (or all?) items aren't loaded from the server, which isn't something Rarity can directly influence; perhaps clearing your cache (delete/rename the folder in your WOW directory) might help in this case.

Are there any Lua/script errors? See https://www.wowace.com/projects/rarity/pages/faq/how-to-enable-and-disable-script-errors-lua-errors

Is there anything that seems relevant in the debug log? (enable via /rarity debug)

Hello,

I'm having a similar issue to the OP. I'm in the zone Hinterlands, in the ooze cave at 57,42. When killing the ooze mobs (Jade Ooze and Green Sludge) I can see the 0/85 Attempts tooltip, however, when I kill and loot an ooze the attempt tracker does not update. I've run debug mode and will post a link to a picture with the results.

https://imgur.com/qMXdktPhttps://imgur.com/qMXdktP

Hopefully this helps, thank you.

Apologies for the double link, I can't seem to edit one of them out.

That doesn't look like the same issue to me. For those slimes, attempts are counted when opening the bag that may contain the pet, not when killing an enemy that drops the bag.

Ah I see, thank you for the information.

Is there anyway you can make rarity track kills for rare item drops again?

I don't understand the question. Do you face the same problem? With this issue, I'm not even sure what the exact problem is because the OP didn't elaborate.

Feel free to try what I wrote above, or give me more information to work with :)

I cleared my cache and that seemed to work for a while ... but now I get the following error (which I've also sent to the ACE library & Adibags)

17x FrameXML\UIParent.lua:496: script ran too long
[string "@FrameXML\UIParent.lua"]:496: in function `UIParentLoadAddOn'
[string "@Rarity\Core\Collections-Collections.lua"]:63: in function `ScanToys'
[string "@Rarity\Core\Collections-Collections.lua"]:307: in function `ScanExistingItems'
[string "@Rarity\Core.lua"]:198: in function `DoEnable'
[string "@Rarity\Core.lua"]:167: in function <Rarity\Core.lua:166>
[string "=[C]"]: ?
[string "@AdiBags\libs\AceAddon-3.0\AceAddon-3.0-13.lua"]:70: in function <...ceAdiBags\libs\AceAddon-3.0\AceAddon-3.0.lua:65>
[string "@AdiBags\libs\AceAddon-3.0\AceAddon-3.0-13.lua"]:527: in function `EnableAddon'
[string "@AdiBags\libs\AceAddon-3.0\AceAddon-3.0-13.lua"]:630: in function <...ceAdiBags\libs\AceAddon-3.0\AceAddon-3.0.lua:615>

But the Unable to retrieve item information from the server is also back on all mounts (etc.)

Does the timeout happen if you disable all addons except Rarity? If not, chances are it isn't actually caused by Rarity itself.

I would assume your client can't handle too many addons, but this doesn't appear to be something I can help with since it takes place in functions that are inherently part of the WOW client's Lua environment (LoadAddon etc.) or the default frames (UIParent) and not Rarity's code itself.

If there's caching issues, that's also completely outside of an addon's scope and more likely to be caused by client/computer weirdness if there aren't any specific errors pointing towards Rarity.