I noticed this as well. The same thing happens if you set MaximumFramerate to a lower value than would be produced by the looping duration itself.
(For example, Duration = 0.1 seconds and MaximumFramerate = 5, you will still get 10 calls to the OnLoop function.)
The loops are still happening, even if their parent frames never get updated. This could be either desirable, or undesirable, depending on how the addon wishes to use timers.
This behavior is probably intended to keep multiple looping animations in a group in-sync, independent of the player's or animations' framerates.
Remember that we are talking about encouraging testers to provide feedback that is not necessarily limited to in-game errors. Part of this process involves a means of providing directions or instructions to testers for new features or desirable testing scenarios.
The changelog is a good place to start for this, but I would certainly understand if authors wished to provide instructions more blatantly within the game itself.
If an author is only using an Animation's looping for timer purposes, further CPU efficiency might be gained by setting the maximum framerate of the animation to the inverse of its duration.
Specifically, you will want to look at the insets subtable to determine how far in from each side the frame's background texture is drawn. You can subtract these values from :GetWidth() and :GetHeight() to determine the "inner size" of the frame.
Getting the tester (not average users) to swat at the dialog is precisely the point. Anyone unwilling to take that small action once per build probably shouldn't be testing alpha and beta versions of the addon, in my opinion.
I think people who are willing to test will already be the ones downloading alpha and beta packages.
But as you said, I would not be opposed to a pop-up message with each build that explained the testing priorities. Esepcially if there were a checkbox to the effect of "Don't show this message again for this build."
This is one area where I think per-project forums might be helpful. (Or at least having a few different per-project comment threads.) It seems many users are uncomfortable working with the ticket system for providing feedback.
If you really want some significant testing and feedback, however, I'm afraid you will just need to slow down the entire release cycle. Testers' playtime is limited, and they may not be able to try the build and provide feedback as quickly as you hope. Try limiting yourself to packaging one build per week, whether that build is alpha, beta, or release. (I haven't noticed an excessive number of packaged builds for Recount, so this may be easy for you.)
Another option you might consider is a splash screen or some chat spam in your alpha and beta builds only. Ensure that every time a tester logs in, they are presented front and center with your goals for that particular build, and specific scenarios they should test. Many testers may not read the change log, or may have forgotten what it said by the time they get into the game.
When players install alpha and beta builds, they are becoming your testers, and if they're unable to tolerate this "spam", they are unlikely to have provided meaningful feedback on the changes anyway. Those players should switch to release versions only.
Is it possible you have another addon which might be modifying the titles dropdown? I think Outfitter might change it. (I have no idea if this would affect the font or not.)
I have also noticed what appears to be a 5 day (120 hour) timer on these "weekly" quests. However, weekly maintenance seems to always reset this timer. In addition, some rolling restarts (which we've been having a lot of lately) seem to reset these timers, too. There have also been a few occasions where I've been able to do the "resource gathering" quest more than once in a 5 day period, if a different random resource is available that day.
My advice would be just to get into the habit of doing these quests on the same days each week. Do them on Tuesdays and Sundays, or on Wednesdays and Mondays. Remember that some quests are only available while on offense or defense, so you'll need to do at least two battles. Then if you happen to be in Wintergrasp other days of the week, swing by the resource quest givers to see if another quest happens to be available to you.
Regarding requesting new features, it's important to keep in mind that very few of the new or changed APIs are created solely for the use of third-party addon authors. They're typically created for use by Blizzard's own addons, and they allow us to use them unsupported.
Until the scriptable portion of the Blizzard UI needs to know about any of the various world coordinate systems (there are several), we're unlikely to see those exposed as a part of a usable API. It's been requested dozens of times over the past 5 years, and has never been implemented.
If you don't want to replace the default Blizzard font for everything, you can try modifying the global DAMAGE_TEXT_FONT. It's just a path to a font file.
By default, DAMAGE_TEXT_FONT = "Fonts\\FRIZQT__.TTF".
Unfortunately, it's not possible to change the size, color, or style of the damage text with globals or through any other means in-game. You'll still have to look around and find a smaller font.
No, you cannot change the texture of the selection circle, nor its size, nor its color. (It can't even be overridden by placing an identically named texture in the same location in the filesystem.)
If you'd like to change the nameplate textures, the easiest way to do that would be with one of the existing nameplate addons, such as Aloft.
0
(For example, Duration = 0.1 seconds and MaximumFramerate = 5, you will still get 10 calls to the OnLoop function.)
The loops are still happening, even if their parent frames never get updated. This could be either desirable, or undesirable, depending on how the addon wishes to use timers.
This behavior is probably intended to keep multiple looping animations in a group in-sync, independent of the player's or animations' framerates.
0
The changelog is a good place to start for this, but I would certainly understand if authors wished to provide instructions more blatantly within the game itself.
0
Edit: This may not have any realistic effect when no animation work is actually being done, but it certainly shouldn't hurt anything.
0
{ bgFile = "bgFile", edgeFile = "edgeFile", tile = false, tileSize = 0, edgeSize = 32, insets = { left = 0, right = 0, top = 0, bottom = 0 } }Specifically, you will want to look at the insets subtable to determine how far in from each side the frame's background texture is drawn. You can subtract these values from :GetWidth() and :GetHeight() to determine the "inner size" of the frame.
0
0
if(select(2, UnitClass("player")) ~= "CLASSNAME") then return DisableAddOn("YourAddonName"); end
0
But as you said, I would not be opposed to a pop-up message with each build that explained the testing priorities. Esepcially if there were a checkbox to the effect of "Don't show this message again for this build."
0
If you really want some significant testing and feedback, however, I'm afraid you will just need to slow down the entire release cycle. Testers' playtime is limited, and they may not be able to try the build and provide feedback as quickly as you hope. Try limiting yourself to packaging one build per week, whether that build is alpha, beta, or release. (I haven't noticed an excessive number of packaged builds for Recount, so this may be easy for you.)
Another option you might consider is a splash screen or some chat spam in your alpha and beta builds only. Ensure that every time a tester logs in, they are presented front and center with your goals for that particular build, and specific scenarios they should test. Many testers may not read the change log, or may have forgotten what it said by the time they get into the game.
When players install alpha and beta builds, they are becoming your testers, and if they're unable to tolerate this "spam", they are unlikely to have provided meaningful feedback on the changes anyway. Those players should switch to release versions only.
0
0
0
TradeskillCooldownGroups = { Alchemy = { 100 = { name = "Transmutation" , -- localize this duration = 72000 , -- 20 hours, in seconds spells = { 11479 , -- Transmute: Iron to Gold 11480 , -- Transmute: Mithril to Truesilver 60350 , -- Transmute: Titanium 17559 , -- Transmute: Air to Fire 17560 , -- Transmute: Fire to Earth 17561 , -- Transmute: Earth to Water 17562 , -- Transmute: Water to Air 17563 , -- Transmute: Undeath to Water 17565 , -- Transmute: Life to Earth 17566 , -- Transmute: Earth to Life 28585 , -- Transmute: Primal Earth to Life 28566 , -- Transmute: Primal Air to Fire 28567 , -- Transmute: Primal Earth to Water 28568 , -- Transmute: Primal Fire to Earth 28569 , -- Transmute: Primal Water to Air 28580 , -- Transmute: Primal Shadow to Water 28581 , -- Transmute: Primal Water to Shadow 28582 , -- Transmute: Primal Mana to Fire 28583 , -- Transmute: Primal Fire to Mana 28584 , -- Transmute: Primal Life to Earth 53771 , -- Transmute: Eternal Life to Shadow 53773 , -- Transmute: Eternal Life to Fire 53774 , -- Transmute: Eternal Fire to Water 53775 , -- Transmute: Eternal Fire to Life 53776 , -- Transmute: Eternal Air to Water 53777 , -- Transmute: Eternal Air to Earth 53779 , -- Transmute: Eternal Shadow to Earth 53780 , -- Transmute: Eternal Shadow to Life 53781 , -- Transmute: Eternal Earth to Air 53782 , -- Transmute: Eternal Earth to Shadow 53783 , -- Transmute: Eternal Water to Air 53784 , -- Transmute: Eternal Water to Fire 66658 , -- Transmute: Ametrine 66659 , -- Transmute: Cardinal Ruby 66660 , -- Transmute: King's Amber 66662 , -- Transmute: Dreadstone 66663 , -- Transmute: Majestic Zircon 66664 , -- Transmute: Eye of Zul } , } , } , Mining = { 200 = { name = "Titansteel" , -- localize this duration = 72000 , -- 20 hours, in seconds spells = { 52208 , -- Smelt Titansteel } , } , } , Tailoring = { 310 = { name = "Mooncloth" , -- localize this duration = 331200 , -- 92 hours, in seconds spells = { 56001 , -- Moonshroud } , } , 320 = { name = "Shadowweave" , -- localize this duration = 331200 , -- 92 hours, in seconds spells = { 56002 , -- Ebonweave } , } , 330 = { name = "Spellfire" , -- localize this duration = 331200 , -- 92 hours, in seconds spells = { 56003 , -- Spellweave } , } , } , Inscription = { 410 = { name = "Minor research" , -- localize this duration = 72000 , -- 20 hours, in seconds spells = { 61288 , -- Minor Inscription Research } , } , 420 = { name = "Northrend research" , -- localize this duration = 72000 , -- 20 hours, in seconds spells = { 61177 , -- Northrend Inscription Research } , } , } , Enchanting = { 500 = { name = "Void Sphere" , -- localize this duration = 172800 , -- 48 hours, in seconds spells = { 28028 , -- Void Sphere } , } , } , }Edit: This database is accurate as of patch 3.2.0a. It may be used by any person for any reason, with no credit neccessary.
0
My advice would be just to get into the habit of doing these quests on the same days each week. Do them on Tuesdays and Sundays, or on Wednesdays and Mondays. Remember that some quests are only available while on offense or defense, so you'll need to do at least two battles. Then if you happen to be in Wintergrasp other days of the week, swing by the resource quest givers to see if another quest happens to be available to you.
0
Until the scriptable portion of the Blizzard UI needs to know about any of the various world coordinate systems (there are several), we're unlikely to see those exposed as a part of a usable API. It's been requested dozens of times over the past 5 years, and has never been implemented.
0
By default, DAMAGE_TEXT_FONT = "Fonts\\FRIZQT__.TTF".
Unfortunately, it's not possible to change the size, color, or style of the damage text with globals or through any other means in-game. You'll still have to look around and find a smaller font.
0
If you'd like to change the nameplate textures, the easiest way to do that would be with one of the existing nameplate addons, such as Aloft.