WowAce

4x integer overflow attempting to store 6690098711
[C]: ?
Rarity\Core.lua:2765: in function `UpdateText'
Rarity\Core.lua:581: in function `DoEnable'
Rarity\Core.lua:526: in function <Rarity\Core.lua:525>
(tail call): ?
[C]: ?
[string "safecall Dispatcher[1]"]:9: in function <[string "safecall Dispatcher[1]"]:5>
(tail call): ?
...ceAdiBags\libs\AceAddon-3.0\AceAddon-3.0-12.lua:558: in function `EnableAddon'
...ceAdiBags\libs\AceAddon-3.0\AceAddon-3.0-12.lua:651: in function <...ceAdiBags\libs\AceAddon-3.0\AceAddon-3.0.lua:636>
[C]: in function `LoadAddOn'
FrameXML\UIParent.lua:445: in function `UIParentLoadAddOn'
FrameXML\UIParent.lua:564: in function `TimeManager_LoadUI'
FrameXML\UIParent.lua:1191: in function <FrameXML\UIParent.lua:1089>

This seems like it could be caused by the archaeology projects data being invalid. Normally, it should be gone after manually resetting it.

I'll have to look into fixing this automatically, but in the meantime you could find the entries for Fossilized Raptor and the Scepter (mount) in your Rarity.lua saved variables file (located in the WTF/<Account>/SavedVariables folder) and set them to 0 or something. Make a backup of your saved variables first, of course.

Okay, I will try that, thank you!

Please try the latest alpha and report back. There should be no more errors, allowing the attempts count to be updated properly later on (or reset manually ingame).

Edit:

It should display an incorrect number but otherwise load without errors, which then allows you to either update the attempts manually (by deleting them to have Rarity query Blizzard's API for the correct count) or wait until Rarity updates it with the next manual attempt (when you continue to finish digsites and complete related archaeology projects).

I don't want to potentially risk messing up someone's database with an automated deletion routine, so I'll stick with this "fix" instead of trying to find the invalid entries and deleting them automatically.