Angry Keystones
Adds additional information to the Mythic Keystone objective tracker.
Bonus Chest Timer
Adds a secondary timer next to main one to show time left for bonus chests. Shows in gold for time for 2 bonus chest, and in silver for time for 1 bonus chest. It also adds a line on the timer bar to mark when this will occur.
Extended Progress Bar
Shows more exact information on how much Enemies Forces progress is needed. Either displaying it as a more exact percent (24.19%) or as a numerical value (90/372), or both. Will also show on enemy tooltips how much progress they each give, after killing them once to learn how much progress they give.
Death Tracker
Will show an icon in the objective tracker with total number of deaths for the current run. Hover over it for a tooltip to show a breakdown of deaths per player, and the total time lost. It won't count deaths very far away from you that didn't show in the combat log.
Keystone Linking
Replaces Keystones links you see in chat from [Mythic Keystone] to [Keystone: The Arcway - Level 5], will also color it grey if it is depleted.
Auto Gossip
During Mythic Keystone dungeons it will automatically select gossip entries for you. For example for starting Odyn and his trash, and Court of Stars buff objects.
Also has an option to output the clue from Chatty Rumormongers to party chat during the Court of Stars event. Currently only available for English locales.
Options
Configuration options can be accessed with /akeys, or in the addon interface options panel. There is an option for auto gossip, format of progress bar, and whether to show progress value on enemy tooltips.
Frequently Asked Questions
Can you disable hiding the objective tracker during boss battles?
This is caused by another addon, likely DBM, hiding the tracker during boss battles. To disable this, uncheck the "Hide watch (objective) frame during boss fights..." in the "Blizzard Disable & Hide" area of DBM settings.
I received an ADDON_ACTION_BLOCKED error, can you fix it?
First try disabling the "Hide quest and achievement trackers during Mythic Keystones" and "Show objective tracker after Mythic Keystone completion" configuration options.
ADDON_ACTION_BLOCKED very frequently doesn't accurately blame the correct addon. There is a reason that is not displayed as a standard Lua error by default, and you need an additional addon (like BugGrabber) to even see the contents of the message. If you really believe it is AngryKeystone causing the error and causes a defect to occur, please first verify the error appears with only AngryKeystones enabled and that it stops happening when it is disabled.
In reply to HD_MOVIE_SOURCE:
I've had a very similar lua error from Clique for years now and I can't figure out what's causing it.
It's nearly identical, except I can get different ones, all the same error except the number in the 'CompactRaidFrame#:Show()' function.
1x [ADDON_ACTION_BLOCKED] AddOn 'Clique' tried to call the protected function 'CompactRaidFrame26:Show()'.
[string "@!BugGrabber\BugGrabber.lua"]:519: in function <!BugGrabber\BugGrabber.lua:519>
[string "=[C]"]: in function `Show'
[string "@FrameXML\CompactUnitFrame.lua"]:376: in function `CompactUnitFrame_UpdateVisible'
[string "@FrameXML\CompactUnitFrame.lua"]:307: in function `CompactUnitFrame_UpdateAll'
[string "@FrameXML\CompactUnitFrame.lua"]:126: in function <FrameXML\CompactUnitFrame.lua:57>
If anyone knows anything of what this is caused by, please let us know?
In reply to HD_MOVIE_SOURCE:
getting this error as well
1x [ADDON_ACTION_BLOCKED] AddOn 'AngryKeystones' tried to call the protected function 'CompactPartyFrameMember1:Show()'.
[string "@!BugGrabber\BugGrabber.lua"]:519: in function <!BugGrabber\BugGrabber.lua:519>
[string "=[C]"]: in function `Show'
[string "@FrameXML\CompactUnitFrame.lua"]:376: in function `CompactUnitFrame_UpdateVisible'
[string "@FrameXML\CompactUnitFrame.lua"]:307: in function `CompactUnitFrame_UpdateAll'
[string "@FrameXML\CompactUnitFrame.lua"]:155: in function <FrameXML\CompactUnitFrame.lua:57>
In reply to Holy_Z:
so any update on this? it's completely fucking up raid/party frames. Had to turn off addon
What are you (Blizzard UI user) guys doing to prevent the dungeon panel to eating the debuffs? Sometimes the debuffs are over the dungeon panel, but sometimes under it, covering them. You moving the debuffs? Or the dungeon panel?
Message: Interface\AddOns\AngryKeystones\Schedule.lua:60: attempt to concatenate local 'playerRealm' (a nil value)
Time: Sun Oct 25 13:18:44 2020
Is there a github page that I can share some code and fixes?
In reply to siweia:
Unless Ermad replies with something he prefers, I'd suggest using the CurseForge issues system and either pasting some code in there, or linking us to something.
In reply to ywfn666:
I did open an issue on the site.
In reply to siweia:
Yeah saw it. It's not being ignored, but Ermad wants to wait until SL is out to add SL stuff.
In reply to siweia:
I appreciate the contribution and putting them in, just only playing a small amount atm so it takes some time to test.
In reply to Ermads:
Ok, glad to know you are not afk.
You forgot to update game interface in the toc file.
In reply to okaboo:
Haha, yea,, toc bump in notes, but no actual toc bump. Ssssssstuff happens XD
In reply to okaboo:
Fixed
In reply to ywfn666:
that is quite funny it was actually not fixed :)
Kind of makes you think if you know what your doing oh well back to unloading the addon again
In reply to Forge_User_54881641:
No idea what you're talking about.
In reply to ywfn666:
You claimed you'd fixed the toc file but in realty you had not fixed it making the game still think it was for client version 8.3 but it seems like you finally got around to it anyway.
Message: Interface\AddOns\AngryKeystones\Schedule.lua:112: attempt to index field 'RunStatus' (a nil value)
Time: Sat Oct 17 10:17:23 2020
Count: 13
Stack: Interface\AddOns\AngryKeystones\Schedule.lua:112: attempt to index field 'RunStatus' (a nil value)
Locals:
In reply to enoryt:
Change RunStatus to WeeklyChest.RunStatus in lines 110, 112, 113, 114 of Schedule.lua
In reply to enoryt:
Change RunStatus to WeeklyChest.RunStatus in lines 110, 112, 113, 114 of Schedule.lua