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.
Is this better in the latest released version?
Hey @Ermads, I put up a new ticket on your wow ace project site with lua error for the latest version. Please take a look thank you.
is there a test mode for adjust addon?
There isn't, because there really isn't anything to adjust. All the options are the enable/disable features.
Message: Interface\AddOns\AngryKeystones\ObjectiveTracker.lua:29: attempt to index local 'seconds' (a number value)
Time: 11/23/16 16:34:04
Count: 1
Stack: Interface\AddOns\AngryKeystones\ObjectiveTracker.lua:29: in function <Interface\AddOns\AngryKeystones\ObjectiveTracker.lua:19>
Interface\AddOns\AngryKeystones\ObjectiveTracker.lua:209: in function `?'
Interface\AddOns\AngryKeystones\Core.lua:10: in function <Interface\AddOns\AngryKeystones\Core.lua:6>
Locals: timeAmount = 3825931
seconds = 45
ms = 931
hours = 1
minutes = 3
(*temporary) = <function> defined =[C]:-1
(*temporary) = "%d:%.2d:%.2d.%.3d"
(*temporary) = 1
(*temporary) = 3
(*temporary) = nil
(*temporary) = "attempt to index local 'seconds' (a number value)"
Thanks for the report, I will get it fixed for next release.
275x AngryKeystones\ProgressTracker.lua:150: attempt to index local 'linetext' (a nil value)
AngryKeystones\ProgressTracker.lua:150: in function <AngryKeystones\ProgressTracker.lua:105>
[C]: ?
Locals:
I released a new version that should fix this.
Having issues clicking default raid frames and joining instanced PvP like the comment before me. Just shows it crashing and wanting to disable or ignore it.
Please ensure that it is actually this addon blocking it, those messages are notorious for blaming the incorrect addon. Does this happen with only Angry Keystones enabled, and is then fixed by disabling it?
It isn't every single time, just often, problem is resolved by disabling Angry Keystones
this addon is now blocking me from queuing for random pvp matches.
http://imgur.com/a/dDol7
Having the same issue, happens when clicking default raid frames too.
Please ensure that it is actually this addon blocking it, those messages are notorious for blaming the incorrect addon. Does this happen with only Angry Keystones enabled, and is then fixed by disabling it?
when i proceed to disable angry keystones, i am then able to queue for random pvp matches. If i re-enable it i again get this message and am unable to queue.
Love the addon and I also love your Angry World Quests! I have a couple of feedbacks your fantastic addon.
Firstly, is it possible for the timer to remain being displayed during boss fights? Usually it hide the timer during the fight by default. I know it's default for Blizzard UI so I don't know if you can make it to happen.
Secondly, I believe the timer should stay displayed ever after the completion of a dungeon until players zone out or log out. The timer disappears immediately right after final boss is killed.
Again, I love both of your addons and I'm looking forward to continue using both of them!
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.
That is something I would like to add, but with how the addon is setup of just making additions to the default objective tracker is causing some problems for it. I haven't found a good way yet to keep the default it objective tracker shown after the dungeon is complete.
Oh, that would explains everything. Good to know, thanks! Maybe you should contact DBM author and kindly ask him to turn it off by default in future version for this addon.
As for the second question. That make sense, hope you find a workaround for it! Cheers.
when starting a mythic+ , this error (using v0.6.6) shows up to me in my DE client
when i do a (clean) roleback to 0.6.5 , all is perfect
Message: ..\AddOns\AngryKeystones\Core.lua line 10:
attempt to call field '?' (a nil value)
Debug:
AngryKeystones\Core.lua:10:
AngryKeystones\Core.lua:6
Locals:
frame = AngryKeystonesListener {
0 = <userdata>
}
event = "CHALLENGE_MODE_START"
(for generator) = <function> defined =[C]:-1
(for state) = <table> {
(null) = 0
(null) = 0
}
(for control) = <table> {
CHALLENGE_MODE_COMPLETED = <function> defined @Interface\AddOns\AngryKeystones\Splits.lua:94
SplitOutput = <function> defined @Interface\AddOns\AngryKeystones\Splits.lua:63
CHALLENGE_MODE_RESET = <function> defined @Interface\AddOns\AngryKeystones\Splits.lua:86
Startup = <function> defined @Interface\AddOns\AngryKeystones\Splits.lua:152
SCENARIO_CRITERIA_UPDATE = <function> defined @Interface\AddOns\AngryKeystones\Splits.lua:123
}
callback = <table> {
CHALLENGE_MODE_COMPLETED = <function> defined @Interface\AddOns\AngryKeystones\Splits.lua:94
SplitOutput = <function> defined @Interface\AddOns\AngryKeystones\Splits.lua:63
CHALLENGE_MODE_RESET = <function> defined @Interface\AddOns\AngryKeystones\Splits.lua:86
Startup = <function> defined @Interface\AddOns\AngryKeystones\Splits.lua:152
SCENARIO_CRITERIA_UPDATE = <function> defined @Interface\AddOns\AngryKeystones\Splits.lua:123
}
func = 0
(*temporary) = nil
(*temporary) = <table> {
CHALLENGE_MODE_COMPLETED = <function> defined @Interface\AddOns\AngryKeystones\Splits.lua:94
SplitOutput = <function> defined @Interface\AddOns\AngryKeystones\Splits.lua:63
CHALLENGE_MODE_RESET = <function> defined @Interface\AddOns\AngryKeystones\Splits.lua:86
Startup = <function> defined @Interface\AddOns\AngryKeystones\Splits.lua:152
SCENARIO_CRITERIA_UPDATE = <function> defined @Interface\AddOns\AngryKeystones\Splits.lua:123
}
(*temporary) = 1456
(*temporary) = "attempt to call field '?' (a nil value)"
EventListeners = <table> {
WORLD_STATE_TIMER_STOP = <table> {
}
GOSSIP_SHOW = <table> {
}
CHALLENGE_MODE_COMPLETED = <table> {
}
CHALLENGE_MODE_START = <table> {
}
CHALLENGE_MODE_RESET = <table> {
}
PLAYER_ENTERING_WORLD = <table> {
}
SCENARIO_CRITERIA_UPDATE = <table> {
}
WORLD_STATE_TIMER_START = <table> {
}
}
This has been fixed in the latest release, v0.6.7.