WowAce

1x integer overflow attempting to store 12689730504
[string "=[C]"]: in function `format'
[string "@Rarity/Core/Announcements.lua"]:44: in function `AnnounceAttemptForItem'
[string "@Rarity/Core/GUI.lua"]:132: in function `OutputAttempts'
[string "@Rarity/Core/Collections.lua"]:337: in function `ScanArchFragments'
[string "@Rarity/Core/EventHandlers.lua"]:1151: in function `?'
[string "@Ace3/CallbackHandler-1.0-8/CallbackHandler-1.0.lua"]:109: in function <...Ons/Ace3/CallbackHandler-1.0/CallbackHandler-1.0.lua:109>
[string "=[C]"]: ?
[string "@Ace3/CallbackHandler-1.0-8/CallbackHandler-1.0.lua"]:19: in function <...Ons/Ace3/CallbackHandler-1.0/CallbackHandler-1.0.lua:15>
[string "@Ace3/CallbackHandler-1.0-8/CallbackHandler-1.0.lua"]:54: in function `Fire'
[string "@Ace3/AceEvent-3.0-4/AceEvent-3.0.lua"]:120: in function <Ace3/AceEvent-3.0/AceEvent-3.0.lua:119>

Locals:
(*temporary) = "%s: %d attempts - %.2f%%"
(*temporary) = "Scepter of Azj'Aqir"
(*temporary) = 12689730504
(*temporary) = 100

IIRC this could happen due to some API changes on Blizzard's end. This was some years ago, however. Please try this:

* Create a new (temporary) profile in the options UI
* Switch to this "empty" profile
* Complete another attempt for the scepter via archaeology

If the problem is fixed, the issue is with old data still saved in your addon database. In that case you can simply go to the options, switch back to the original profile, and remove the "obscenely large number" with a more realistic attempts count for the item. If gaining an attempt on the new profile causes a similarly large number to be added then something might be broken on Blizzard's end and I'll need to take a closer look when I have time.