I created this infobox to use it in the Slam article. Feel free to use it on any ability --(ALiEN 12:49, 9 April 2007 (EDT))
- Also, reason the history is so big is because Show preview doesn't show changes done to an infobox (might be something I did) --(ALiEN 13:09, 9 April 2007 (EDT))
I've modified the template so it includes abilities that are activated by talents.--ALiEN 20:41, 9 April 2007 (EDT)
"Next melee sec cast"
This phrase appears in the displayed infobox whenever cast_time=Next melee. I am currently investigating how to prevent that, but I don't understand template parameters and how they're processed yet. ° talk ˚ contribs. 00:32, 13 June 2008 (UTC)
This template really shines amongst all those that we have on WoWWiki. I remember seeing it for the first time and thinking, "WOW. All ability pages should be this way." Of course, it was just getting started then. In my application of the template, and the related boilerplate, I've made small revisions to cut down on the amount of data that needed to be duplicated to complete the box (e.g.: buff_image & image used to be independent fields, but buff_image now feeds from image if no other data is supplied).
Which gets me to my main point: cutting down duplicate data. There is still some improvement to be done there, and I'd like to spearhead the effort - but first I'd appreciate a second opinion.
Talented field -- I believe this can be wiped out completely. It's only ever Yes when "Talent Tree" is going to have something. "Talent Tree", as written, only has something if Talented is Yes! If it is stated that "Tree of Life" is Restoration, Tier 9, then people have all the info they need in that regard.
Talent Improvements field -- I have a number of issues with this one, but they have less easy solutions.
- This field has the potential to bloat the infobox immensely (consider almost any Shadow Priest ability). I feel the spirit of an infobox is to provide "at a glance" info, and if you have to scroll it at most resolutions, it is a failure.
- When there are a lot of talents listed, people have a tendency to put "see below" (or more accurately, see left). We have a Talent Improvement section in the boilerplate ... sooooo, why does the info reside in two places? Though not inherently Wrong, any duplication - especially for such a detailed set of data - creates an opportunity for lost data.
- Mind you, as things stand, there's going to be a lot of lost data. We have hundreds of ability pages, and at least tens of talents to consider in relation to them. Nobody really wants to do these kinds of logistics x1000.
Taking that all together, I am forefront advising that Talent Improvements be removed from the infobox and left to the content of the article. I also propose that our template engineers, at their own initiative, think about ways to make more of the talent information automated: Some way or the other, templates should be able to bundle common talent info into these abilities.
E.G.: if school=Shadow, class=Priest, and the spell deals damage, then improvements=(at least) Blackout, Shadow Affinity, Shadow Focus, Shadow Weaving, Darkness, (Shadowform)*, (Vampiric Embrace)*, and (Vampiric Touch)*.
E.G.: if school=Nature, class=Druid, and cast_time~=instant, then improvements=(at least) (Nature's Swiftness)*.
- These spells are in parentheses since they don't actually improve any ability just by taking the talent. You need to debuff the target or buff yourself before their full power is brought to bear.
- That's too much automation for a template. We're trying to make it so people can present information accurately, not so they can play the game on the wiki. -- ( •
) 03:54, 24 June 2008 (UTC)
- Daugh! Pcj, why the dismissive attitude? That's two for two now. I swear you look at something, feel it clashes with your style, and say "no. reverse it." Of course I'm not proposing a recreation of the game. Please re-read the numbered points again. I am saying that, with some good template ideas, accuracy of information improves. You do NOT get accurate information through repetition. You do NOT get accurate information through omission. This infobox proved that through its lifespan. I will thank you, sir, if you do not agree with an idea, to try to offer revisionary criticism, rather than nay-say. ° talk ˚ contribs. 05:53, 24 June 2008 (UTC)
- I concur, a possible idea would be to add "Related Glyphs" under "Other Information"
I have the suggestion to add a field like bcb (=Buff Consolidation Box) that can have the following value:
- Yes or 1: The buff will be stored there if the player uses it (depending on the interface settings). and would have the value yes or 1;
- No, 0 or missing (omitted): The buff will never be stored there, regardless if the player uses it or not. would have the value no or 0, or the field is even omitted;