Talk: Tooltip

Revision as of 23:59, 6 November 2009

List of Archived Talk discussions

Template talk:Tooltip/Archive01: Up to and including June 2007.
Template talk:Tooltip/Archive02: Up to and including May 2008.

Arena rating

What's the option for: "Requires personal and team arena rating of XXXX"?

Abuse |req= for now, I think. -- foxlit (talk) 20:53, 11 June 2008 (UTC)

Made it |rating=. Just give it a number value and it'll print the rest. g0urra[T҂C] 22:01, 12 July 2008 (UTC)

Double-quotes in name messing with float/font

I saw this problem with ["Gigantique" Bag]. Apparently using " instead of "-mark works. -- Fandyllic (talk · contr) 9:48 AM PST 23 Jun 2008

Cooldown format

There should be a standard format for the Cooldown= entry, perhaps a template like cost. I've seen Cooldown= nn min and Cooldown= nn minutes. I think both work because they are transposed as text, there is no interpretation, but standardizing would be better. Madkaugh (talk) 21:20, 8 September 2008 (UTC)

Non PNG File Extensions

Seems in past discussions this was brought up, but still appears to be unresolved. For example, if you take an icon from wowhead, you'll have to convert it from JPG to PNG, yet the file uploader will take many non-PNG formats. It seems like such a popular template should be congruent with the upload feature. Howbizr (talk) 02:51, 21 September 2008 (UTC)

We intentionally use .png for all of our in-game icons because it makes the rest of our templates/page-creation bots that use wow icons a lot easier to deal with.

The file uploader takes all kinds of images because we use more than just WoW icons... --k_d³ 05:38, 21 September 2008 (UTC)

Achievement Tooltip Ideas

File:INV Ammo Arrow 02.png

Shafted!
Shoot 10 players with the [Silver Shafted Arrow].
Criteria:
- - 10x Silver Shafted Arrow.

Fool For Love
Complete the Love is in the Air achievements listed below.
Criteria:
Rewards:
- Title Reward: <The Love Fool>

I had some ideas. Just wanted to share, if you want to adopt into the stylesheet / template. Here's an example of a regular achievement, as well as an achievement made up of other achievements. -Howbizr (talk) 20:04, 21 October 2008 (UTC)

This should be made into a new template if created at all. This template is strictly for items. --Pcj (T•C) 20:08, 21 October 2008 (UTC)

Best current practice for usage

I notice that there's some inconsistency between common usage, the example at the top of this page, and the boilerplate. On this page, we have:

{{{{{tpl|tooltip}}}
|mode={{{mode|}}}
|arg={{{arg|}}}

Help:Item articles/Preload has:

<onlyinclude>{{tooltip
|mode={{{mode|}}}
|arg={{{arg|}}}
...
}}</onlyinclude>

The boilerplate definitely needs some tweaking so that it works more reasonably with subst (currently the onlyinclude wrapper and standard setup for mode and arg are lost in the subst). The item pages have a mixture of styles, a few of them are even missing onlyinclude/noinclude, causing breakage when used with, e.g. {{item}}. Some use noinclude around the rest of the page, some wrap the tooltip with onlyinclude. I reckon onlyinclude is the better style, as it's less prone to someone less experienced incorrectly putting something outside the noinclude block. But what about {{tooltip vs. {{{{{tpl|tooltip}}}. I can see the utility of the latter, allowing an alternate template to be used when transcluding the page. Is that meant to be the standard, and should we be changing the existing articles to that standard?

I've got all the necessary framework and regexps available with MurphBot, from standardising and fixing the {{achievementbox}} usage, and it is very easy to adapt that to that to this template (although I do realise the scale of usage is significantly larger). Would it be desirable to have a bot standardise the usage to best practice (ensuring there's an onlyinclude wrapper, removing old noinclude wrappers, and ensuring that the required minimum parameters are present in standard form)? If so, does the following represent our desired standard usage?

<onlyinclude>{{{{{tpl|tooltip}}}
|mode={{{mode|}}}
|arg={{{arg|}}}
...
}}</onlyinclude>

--Murph (talk · contr) 11:46, 24 December 2008 (UTC)

What I've understood so far is that {{{{{tpl|tooltip}}} is for Foxbot to easily change the tooltips. The <noinclude></noinclude> has mostly been used in tooltips from older items. I don't believe that newer items has been using noinclude. <onlyinclude></onlyinclude> is what should be used.

On using bots to eliminate noinclude in favor of onlyinclude: I think that's very hard to do since there's articles that aren't items but use noinclude anyway. I'd let someone who knows more about bot editing to comment on that, thoug. g0urra[T҂C] 12:07, 24 December 2008 (UTC)

Thanks. As far as restricting the elimination of noinclude to item pages, that's easy enough, as long as it is sufficient to restrict it to pages which actually include usage of {{tooltip}} (and not pages which transclude pages which have the template). The python regexps which should achieve that are:

'(?msi)(?<={{{{{tpl\|tooltip}}})(.*?)</?noinclude>' -> '\1'

'(?msi)</?noinclude>(?=.*{{{{{tpl\|tooltip}}})' -> ''

Are there any examples of pages which are not items, but do have {{tooltip}} in them?

And not wanting to produce a controversial tangent here (if it's to be discussed, somewhere else would be more appropriate), but this is something that would be made more certain (ensuring that you're only processing items) if the items were in their own namespace or pseudo-namespace.

--Murph (talk · contr) 12:31, 24 December 2008 (UTC)

Just to clear things up: {{{{{tpl|tooltip}}} was inserted by Foxbot, but the actual use is as Murph described: allow a different template to receive all of the tooltip arguments on transclusion. The syntax is desired behavior, and I've now updated the preload page to reflect this. -- foxlit (talk) 10:34, 27 February 2009 (UTC)

Feral attack power

Inspired by something on the Village Pump I noticed way too late, and ultimately Wowhead's new way of displaying Feral attack power [1], I used my basic wiki skills to come up with a suggestion [example] how to implement that on our tooltip template here (for Staves/Polearms/2H-Maces over 54.8 DPS only)

I'd just be bold, but I'm unsure about just copying Wowhead's 'design'. (As a European, I expect just about anything from the US legal system ) Plus, others might not like it/have better ideas.

The previous FAP weapons need to be updated anyway, new DPS, Strength to AP, I'd do that as soon as I hear a 'yes' here. Hopefully Google helps me find all of them. ~ Nathanyel (talk) 14:16, 22 February 2009 (UTC)

Gourra made a point on the Village Pump that WoWWiki tooltips should look like ingame tooltips, and not like Wowhead ones. So another option would be to simply have FAP displayed as ingame, though the green might confuse non-druids. Then again, who can't read "in Cat, Bear, Dire Bear, and Moonkin forms only"? Anyway, I'd hope for at least a "go for it" before I get going

~ Nathanyel (talk) 17:57, 2 March 2009 (UTC)

If the goal is to "make wowwiki tooltips look like in-game tooltips", then you're going to need to know the race and class of the viewer, and what weapons he can wield. Those things are taken into account when the in-game engine renders the tooltip ("Mace" will be in red or white, depending on whether the character can wield a mace). But you don't make any attempt to do that in wowwiki, because the viewer is not in-game, and those decisions don't apply. Thus applying that rule to the Feral Attack Power rating isn't sensible either. I like how wowhead uses an orange color to make it stand out; it's clear that it's something that is not done in-game. I see no problem copying their style, as long as you don't copy their code. The old "Look & Feel" argument was settled long ago in courts, when Apple lost their lawsuit against Microsoft. There is nothing illegal about copying "use orange text to indicate that feral attack power is different and only applies to druids". Please do copy wowhead. Markkawika (talk) 20:35, 2 March 2009 (UTC)

Now that's good feedback, never thought of the "mace in red" thing - I guess what WoWWiki (or Wowhead) should/is trying to display is the item from an omniscient point of view, level 80 character of all classes, with all weapon and trade skills maxed out. Anyway, will get to it after lunch. ~ Nathanyel (talk) 10:11, 3 March 2009 (UTC)

Oh wait, I can't edit {{tooltip}} myself...

Would someone with the proper rights do that please? Here's the diff with what needs to be added. Gonna go ahead and update the former feral weapons already. ~ Nathanyel (talk) 12:50, 3 March 2009 (UTC)

This edit has an error, and causes "Expression error: Unexpected > operator" to appear in every page that uses this tooltip. Would some kind soul with the proper authority fix this please? --Hops Splurt (talk) 15:34, 3 March 2009 (UTC)

Which article are you talking about? I don't see any errors so far with the tooltip. --g0urra[T҂C] 15:41, 3 March 2009 (UTC)

Should be fixed now. --Pcj (T•C) 16:06, 3 March 2009 (UTC)

And done, at least with those weapons Google came up with. Searching for others soon. Would you believe how many distractions can come up during the course of an afternoon? Noticed some ±1 AP disparities on some green Outland random-stat staves plus [Brunnhildar Harpoon], but 1 AP is virtually nothing in Outland content and upwards. ~ Nathanyel (talk) 18:58, 3 March 2009 (UTC)

There are also one-handed and main hand weapons that has feral attack power - while they are obviously not suitable for Druids, shouldn't they show the feral attack power too? This is what I thought about changing in the specific part of the template. The changes starts and ends with '''.

{{#ifexpr:{{{dps|0}}}>54.8|{{#switch:{{{slot|}}}|Two-Hand|{{#'''switch''':{{{type|}}}|Staff|Mace|Polearm=<li>({{#expr:floor(({{{dps|}}}-54.8)*14)}} [[Feral attack power|feral attack power]])|}}'''|One-Hand|Main Hand={{#switch:{{{type|}}}|Dagger|Mace|Fist Weapon=<li>({{#expr:floor(({{{dps|}}}-54.8)*14)}} [[Feral attack power|feral attack power]])|}}'''|}}}}

--g0urra[T҂C] 15:31, 10 March 2009 (UTC)

If you're thinking about the Vanilla 1H maces like End of Dreams, they don't have Feral AP anymore, as this is computed solely by weapon DPS now. For newer 1H weapons with >54.8 DPS, the Feral AP gained from them doesn't matter, as no Feral uses 1Hs anymore – and the FAP display should be (mostly) for weapons that a Feral of appropriate level would use – I'd even supress FAP for staves with spellpower (Atiesh would need a special fix, though) ~ Nathanyel (talk) 18:30, 10 March 2009 (UTC)

Well of course

[The End of Dreams] doesn't have FAP, it has lower than 54.8 DPS. While 1H weapons aren't suitable for feral druids, we should show the FAP for those anyway for consistency.

I've just noticed that the FAP value on items is 1 higher than the value on Wowhead, should this be corrected? I'm not reallyy fluent in the math coding, so it would be appreciated if someone else fixed this. --g0urra[T҂C] 10:57, 16 March 2009 (UTC)

Yeah I noticed the ±1 discrepancies, too, as mentioned above, could be that the actual formula is even more complicated than floor((dps-54.8)*14), but hey, it's just 1 AP max *shrug* If someone finds a better formula, just change the one we use.

I don't know about showing FAP on 1Hs, I'd vote against it, but if more people want it, why not. ~ Nathanyel (talk) 13:06, 16 March 2009 (UTC)

The thing though is that it should be {{#expr:((dps-54.8)*14) round 0}}, which rounds it up or down (506.4 -> 506, 506.6 -> 507 etc) and with no decimals. I'll let some other admin change it though and create the HUEG job queue. --g0urra[T҂C] 15:01, 26 March 2009 (UTC)

No level requirement

I've run across items with no level requirement having level=1 in the WoWWiki tooltip. This is indirectly correct, but is really not the same thing as no level requirement - the tooltip display is different. Am I correct that if the item does not have an explicit level 1 requirement in the in-game tooltip, these should be removed, per note above, "make wowwiki tooltips look like in-game tooltips"? For this particular bit of data, The Armory should be a reliable source. Madkaugh (talk) 01:17, 3 March 2009 (UTC)

Yes, that's correct. --Pcj (T•C) 02:21, 3 March 2009 (UTC)

False positives for Pages which may need their tooltips updated

This template has a mechanism for detecting out of date tooltips, mostly from the change from +healing and +damage to spellpower. The out of date items get put into Category:Pages which may need their tooltip template updated. With transclusion, this category currently contains over 3,200 articles. Of the first 50 I checked, less than half were erroneous, the others were included because they included the word "healing" (mostly from alchemy trinkets). Would it be possible to increase the sensitivity of the detection to minimize the false positives?

Items that had +healing and +damage said: "Increases healing done by up to X and damage done by up to X for all magical spells and effects." Items that increased healing and damage by the same amount had: "Increases damage and healing done by magical spells and effects by up to X."

Perhaps expanding "healing" to "healing done" or a check for "for all magical spells and effects." (not sure if that is still used) would eliminate many of the false positives. This might make a project to go through the templates and update them somewhat less daunting. -- Wige (Talk - Contribs) 18:51, 12 March 2009 (UTC)

It also gets placed on pages that use {{item}} or {{itembox}} that contains the item that needs updating. So if Item A is linked using those templates on 5 different pages, 6 articles will appear in that category.

^{{TDon't hiss at me.•CIf you do things right, people won't be sure you've done anything at all.)} 00:27, 13 March 2009 (UTC)

There is a section in the template that applies only when the template is being called from the item's own page. Would it be possible to either add the check to that section, or wrap the check in a similar restriction so other pages don't get included? -- Wige (Talk - Contribs) 13:59, 13 March 2009 (UTC)

Fixed that a few hours ago; transcludes will slowly disappear from that category as the job queue catches up. -- foxlit (talk) 15:26, 13 March 2009 (UTC)

Also, the check appears to check a variety of things: "effect" contains "spell crit", "spell hit", "spell haste", "dismiss" (for mounts?), "healing" (for the change to spell power), or "ignore". If some or all of these were put into sub-categories it might make it easier to break down the workload and knock them out one by one. -- Wige (Talk - Contribs) 13:59, 13 March 2009 (UTC)

My plan is just to have a bot go over the remaining pages in the category once the dust settles and update the tooltip, then remove the current "need an update" matches from the template -- foxlit (talk) 15:26, 13 March 2009 (UTC)

Finished; there's a list of items you need to examine manually at Template talk:Tooltip/Pages that might need an update. -- foxlit (talk) 22:48, 16 March 2009 (UTC)

Template:Tooltip/doc

Would like to see this template use the <name>/doc format for the documentation to be displayed on the template page. The documentation for this is extensive, and I find it a bit awkward to have to go to the top of the talk page to find it. Would not cause more than one-time disruption of the template page. --Eirik Ratcatcher (talk) 20:58, 10 April 2009 (UTC)

Done. Enjoy your 34k jobqueue. --k_d³ 02:29, 11 April 2009 (UTC)

Others are willing to upset the entire category schema to implement a new one. I'm willing to alter templates that are used everywhere. Everyone has to have a hobby. :) --Eirik Ratcatcher (talk) 19:06, 16 April 2009 (UTC)

Token refund

I noticed that now you can be refunded your [Dalaran Jewelcrafter's Tokens] if you haven't learned the pattern yet. I propose adding {{tooltip|<tokenrefund>}}. -Howbizr (talk) 19:18, 25 April 2009 (UTC)

Template:Tooltip/Dev

Nah. It's not always there in-game. It should just be a note in the article. --Pcj (T•C) 19:31, 25 April 2009 (UTC)

That was one of the changes made in 3.1. Any alternate-currency-purchased items (outside of things that reward achievements or are stackable -- like orbs) can be refunded within a two-hour window. I agree with pcj that such a statement needs to be in the relevant article itself...

Patch 3.1.0#User Interface: "Players can now return items purchased with an alternate currency back to the original vendor within 2 hours of the purchase time for the original cost of the item. Stackable items (such as Frozen Orbs and gems) and charged items that can be purchased with an alternate currency are not eligible." --k_d³ 01:54, 26 April 2009 (UTC)

Bug: Mail (armor items)

I admire that someone put the effort into making the value of "slot" and "type" into links, but I think that the audience would be better served if they were to link to static pages (i.e. Equipment Slot and either Armor or Weapon). Currently, Plate is a redirect to Plate Armor, Mail discusses mailboxes. I imagine that leather and cloth redirect to the armor types. Specifically, my current complaint is about the Mail link.

I could also live quite easily if those two items were NOT links... --Eirik Ratcatcher (talk) 20:17, 28 May 2009 (UTC)

I fixed the "type" problem for armor types at {{tooltip/Dev}}. Maybe you can test it a bit and then I'll move it to {{tooltip}}. I did a few tests at Template_talk:Tooltip/Dev#Type_make_correct_armor_type_link_tests and it seems to work fine. --

Fandyllic (talk · contr) 2:17 PM PST 28 May 2009

Did you also find/correct any problems with "type=(some weapon type)"? I don't know of any, but since you've got the template up on blocks anyway... :) --Eirik Ratcatcher (talk) 21:47, 28 May 2009 (UTC)

Okay, one potential issue. type="Held in Off-Hand" requires a high degree of precision, to link to somewhere useful, IMO. Just sayin'... --Eirik Ratcatcher (talk) 22:11, 28 May 2009 (UTC)

|type= has been fixed for every case I can think of. Are there any slot issues? --k_d³ 00:10, 26 June 2009 (UTC)

Jewelcrafting

Unique equip needs to support more than a number. For [Thick Dragon's Eye], it's "Unique Equipped: Jeweler's Gems (3)." Howbizr^(t·c) 3:00 PM, 6 Jul 2009 (EDT)

item level

Was there a reason the display for item level was changed? Zurr (talk) 00:44, 25 July 2009 (UTC)

Patch 3.2. --Pcj (T•C) 00:46, 25 July 2009 (UTC)

Support for transmute spells

Transmute: Ametrine
Requires Alchemy (450)
Tools:
[Philosopher's Stone]
Requires:
[Monarch Topaz], [Eternal Shadow]
Creates:
[Ametrine]
Transmute the element of shadow and a Monarch Topaz into an Ametrine.
Cooldown: 20 hr
5 sec cast

They don't fit the current template very well - stuff is missing, or doesn't look right. There are several transmute pages that already need written, plus now we're getting more discoverable transmutes.

Here's my suggestion. If this looks good, I'll work on the template in a sandbox. Otherwise, can you give feedback about what you'd like transmute tooltips to look like instead? Howbizr^(t·c) 8:13 PM, 31 Jul 2009 (EDT)

The issue here is that you're trying to use an item tooltip template for what isn't actually an item, and finding that it doesn't quite fit. This is the intended design -- {{tooltip}}, despite its name, isn't meant to be a catch-all template for all tooltips WoW can display, but rather only supports items (perhaps we should... *horror*... change its name to reflect this purpose).

What you should do is to create another template in the style of {{embroid}} or {{enchant}} – or, better yet, see if those three can generalize to some sort of trade skill tooltip template. -- foxlit (talk) 01:25, 1 August 2009 (UTC)

I'm down for that. You're right - the name keeps tripping me up. Do you have any other spells I might try to support (going with the generic idea)? Or any name ideas? ({{prof}}?)

Howbizr^(t·c) 5:40 PM, 31 Jul 2009 (EDT)

I'm leaning towards calling it {{Proftip}}. Here's my sandbox and some examples.

Howbizr^(t·c) 3:13 AM, 1 Aug 2009 (EDT)

Looks okay to me; your next step is probably to move it into the proper namespace and request some more comments -- assuming nothing comes up, we can then mark enchant/embroid as deprecated (or replace them with versions that call your template). -- foxlit (talk) 11:01, 2 August 2009 (UTC)

Support for unique equip types

Test of |unique-type

Template:Tooltip/Dev

Regression

Template:Tooltip/Dev

Anyone see any problems with this change? See {{Tooltip/Dev}}. Howbizr^(t·c) 9:43 PM, 14 Aug 2009 (EDT)

01:59, 15 August 2009 (UTC)

Maybe it was a bad example, but I was trying to show (regression) that the old behavior isn't broken, just because I added a new feature. I couldn't think of any items that have a unique quantity of more than 1, except gems.

Howbizr^(t·c) 12:07 AM, 15 Aug 2009 (EDT)

Moved to the main space.

Howbizr^(t·c) 9:49 PM, 16 Aug 2009 (EDT)

Using Template Tooltip to categorize

Moved from User_talk:Howbizr#Using_Template_Tooltip_to_categorize Howbizr^(t·c) 9:52 PM, 16 Aug 2009 (EDT)

I was wondering if making {{Tooltip}} auto categorize what can be categorized thru it would be a good idea? Over at Template:Tooltip/Dev I have made a copy of {{Tooltip}} and added some {{#if:{{parameter}} then categorize statements, of the parameters that I know to be used as categories. Take a look, play with and see if it looks doable or not?

I did seperate the Classes= into class1, class2, class3, class4 class5 parameters, so that it will categorize the items into each class that can use the item and made the |classes= go into a non-existant Category:Deprecated classes= paramater to find the pages that used Classes= and can be changed over to class1, class2, class3, etc. -- (M o r p h | ^C | _T) MorphgnomeMorphdraenei 01:41, 17 August 2009 (UTC)

I'll look at it. Basically, as long as you tread carefully, it might not be a bad idea.

Howbizr^(t·c) 9:55 PM, 16 Aug 2009 (EDT)

Don't split classes into more parameters, you can use {{#explode}} to good effect here. Also the category names you have are wrong, they are items, not sets. --Pcj (T•C) 02:10, 17 August 2009 (UTC)

I used the same categories that was used for pre-existing items look at Category:Hunter sets it lists the individual pieces for Tier 1, Tier 2,...,and the Tier 9 I added - and there is no such category as Category:Hunter items -- (M o r p h | ^C | _T)

20:46, 17 August 2009 (UTC)

I do not know about / never heard of {{#explode}} so I can not use / will not use it. -- (M o r p h | ^C | _T)

21:46, 17 August 2009 (UTC)

Where are you guys looking? I don't see anything in the history for {{Tooltip/Dev}}.

Howbizr^(t·c) 10:58 PM, 16 Aug 2009 (EDT)

See {{Tooltip/dev}}. --Pcj (T•C) 03:06, 17 August 2009 (UTC)

The problem with auto-categorization is that the Slot gets messed up: we have categories such as Category:World of Warcraft epic guns and Category:World of Warcraft epic trinkets. Then there's also quality that clashes with other categories, such as Category:Epic gems and Category:World of Warcraft rare quest starting items.

Then there's the issue about the classes= parameter doesn't mean that it's a <class> set item; for example look at [Codex of Defense].

In total I'm against this change. --g0urra[T҂C] 07:26, 17 August 2009 (UTC)

I fixed the classes so that it will not put items into classes unless they have a Type and a slot ( meaning they have to be worn - with the class restriction ) before it would put the <class> sets category. -- (M o r p h | ^C | _T)

20:46, 17 August 2009 (UTC)

As a side note, I moved Morph's stuff to {{Tooltip/Dev}}.

Howbizr^(t·c) 5:56 AM, 17 Aug 2009 (EDT)

I believe the categories have just gotten too complex to allow parameters in a template dictate the category it belongs in.

(^Sssss/_Slithered) 19:04, 17 August 2009 (UTC)

I must agree with Gourra and Coobra. Having a template add categories limits what you can do with the template. Some templates (eg Questbox) do autocategorization; we later on had to retrofit with a parameter to allow blocking that behavior. I would be more in favor of a template that specifically added categories. But by the time you get through with that, you've done 90% of the work you would have done anyway, what with customizing (for instance epic guns and not epic main hand swords). --Eirik Ratcatcher (talk) 20:03, 17 August 2009 (UTC)

I semi agree with these statements - It is beyond my Template knowledge to make it do every category properly -- but by the same token - I refuse to try to remember every category an item can possibly goes into (There are just TOO many - I was just wanting to get the main ones). I will just add a few basic (easy to remember) and you all can go behind me and add all the proper (exacting) categories. -- (M o r p h | ^C | _T)

20:46, 17 August 2009 (UTC)

The DEV template now will only categorize the most common Categories:

If |sockets= is set, it will place the item into the Category:World of Warcraft socketed items
It will auto categorize the item by the items quality: Category:World of Warcraft poor items, Category:World of Warcraft common items, Category:World of Warcraft uncommon items, Category:World of Warcraft rare items, Category:World of Warcraft epic items, Category:World of Warcraft legendary items, Category:World of Warcraft artifact items and Category:World of Warcraft heirloom items
If |qitem= is set, it will auto categorize based on the items quality: Category:World of Warcraft epic quest items, Category:World of Warcraft rare quest items, Category:World of Warcraft uncommon quest items and Category:World of Warcraft common quest items or Category:quest items if it does not fit those specific categories. -- (M o r p h | ^C | _T) MorphgnomeMorphdraenei 18:19, 18 August 2009 (UTC)

As a side note I also added the the |races=Alliance parameter to make it show all 5 alliance races and |races=Horde parameter to make it show all 5 horde races as a shortcut instead of typing out Draenei, Dwarf, Gnome, Human, Night elf and it does NOT interfere with pre-existing items that have |races= already set - so could you add that (it would come in handy for future mounts and such that are Horde/Alliance only items), and its associated documentation to that section. -- (M o r p h | ^C | _T) MorphgnomeMorphdraenei 20:53, 17 August 2009 (UTC)

How's the tip handling (eg) "Dwarf, Gnome" (from old mechanostrider) these days? --Eirik Ratcatcher (talk) 21:35, 17 August 2009 (UTC)

All I did was add to see if you put Horde or Alliance (if so then it put all 5 races for you) if you put anything else it shows what you put - so all previous settings will not be affected -- ( go to Template:Tooltip/Dev and see what I mean) change races= to Dwarf Dwarves Alliance Horde Forsaken undead etc. -- (M o r p h | ^C | _T)

21:41, 17 August 2009 (UTC)

I'm still not really sure if it's worth it to auto-categorize every item that used the template.

If the /Dev categorize everything by the item quality, how will it check for the previous categories? (Epic guns, Epic trinkets, Common quest items etc) An item tagged as rare and quest item will get both "... rare items" and "... rare quest items" categories, of which the first one is redundant.
{{Removedfromgame}} requires all the applicable categories to be removed, how would that be handled?
While you like to make it apply for the major categories, I wouldn't implement it until all categories would be handled by this.
I understand that this would be alot of work for you, but I can't help to wonder if it's worth it - I sure wouldn't pick up a project this big. --g0urra[T҂C] 21:05, 18 August 2009 (UTC)

I can add switch as to the epic gun , trinket items and not place them into the epic items. As to the redundant Rare item and rare quest item - I can put 1 more if - on the rare item (checking if it is quest) (yes then do nothing / no then categorize by quality) so it would be rare item or rare quest item ( not both )
As to the removed from game - I can look at the achievementbox or others and see how the |doc= to remove categories - I am guessing another If statement to make it not show category if doc= is set.
I can not do .
With your requirements then your right it cant be done (not by me) and then we are back to what I said above - I will only put the minimal of all categoies (for I refuse to try to remember your Categorical mess I have looked at in the Item categories as they are **ps you have DUPLICATION there already **) and you all can go behind and fill in whatever specific categories you think they should be in (I was just trying to make all existing items have teh bare minimal of similar categories - I have seen some items with 6-10 categories (some I never knew existed) then I seen other items with just 3 of the 6-10 and another item have a different 3 categories of those 6-10 (and the 2 items were the same type just a different tiers) so many inconsistancies but you are Admins and know you best.

-- (M o r p h | ^C | _T)

23:12, 18 August 2009 (UTC)

Never mind project scrapped -- (M o r p h | ^C | _T)

23:13, 18 August 2009 (UTC)

Picking it back up

So I'm taking a look at it now, taking a different approach from morph.

To get some categories like "<quality> quest rewards" and the gem categories to work we're going to need to add some new parameters.

qreward: just a quest reward flag. No display
key: just a 'this is a key' flag. No display
gem: needs to be one of "Red", "Yellow", "Blue", "Green", "Orange", "Purple", "Prismatic", "Meta". Tooltips can be generated using |gem= instead of the flavor line.

I'll come back and edit this when I work through the rest of the categories. --k_d³ 01:08, 19 August 2009 (UTC)

Okay. I've reached a stopping point for the night. Poke holes in what's been implemented so far. I'm not touching classes/races yet. --k_d³ 02:52, 19 August 2009 (UTC)

With what Blizzard is doing to all (if not 90%) of the gear, this is probably the best time to make the tooltips autocategorize the items. This way the corrections can be made at the same time we clean them up. This will also allow for the renaming of the item categories if we so wish. Sssssssssssssssssssssssss For Pony! (^Sssss/_Slithered) 19:46, 26 August 2009 (UTC)

Expecialy the [[:Cateogory:World of Warcraft <blah blah blah>]] can be placed in the [[:Category:WoW <blah blah blah>]]. -- (M o r p h | ^C | _T)

19:59, 26 August 2009 (UTC)

I'll take the opportunity to point out, adding parameters to tooltip only adds marginally to reliability on categorization, in that it shifts the responsibility on the part of the editor from "add/edit categories" to "add/edit parameters". Sure, it makes it greatly easier to do simple category renaming (by changing the category used by this template). But that is not really a common occurrence, is it? More often, categories are new, or subdivided or combined, which would require editing the individual pages anyway.

"Previous pages provide specific tooltip examples" < -- > "previous pages provide specific category examples" Same with boilerplating.

shrug* --Eirik Ratcatcher (talk) 20:39, 26 August 2009 (UTC)

People using the templates fill in more of the Parameters ( problably because it is easier to see all of the paramters used on 1 page ) then add categories ( problably because all of the POSSIBLE categories are not known for the article ) so if you cateogries as much as possible baised on the parameters then the items will be more fully and consistantly categorized - untill recently I put all Cloth items in Category:World of Warcraft cloth items because I did not know there was Category:World of Warcraft cloth head items, Category:World of Warcraft cloth legs items, Category:World of Warcraft cloth hands items, etc... thus a discrepency in how items were categorized not to mention the Plate, Leather, and various Weapons type items that do not fit any pattern in how they are categoriezed ( that I can see yet ). This is the best closest way to being consistant across the board (you can always add MANUAL categories if you feel the auto categories do not add enough categories) but at least the BASIC categories will be hit for all items with template auto-categorizing! -- (M o r p h | ^C | _T)

21:18, 26 August 2009 (UTC)

Sure you can add categories. How do you *remove* categories? --Eirik Ratcatcher (talk) 23:38, 26 August 2009 (UTC)

The idea is to add the known Correct categories 1^st - so ther should not be a need to reemove them unless it is a {{Removedfromgame|<patch #>}} item that requires all categories to be removed. Thiscan be implemented just like the achievements do now (you add 1 more parameter that encompasses ALL categorizations. If |doc= is set then no categories are added, or any other main parameter name for this function. This ability is added last, after the auto-categorization is known to be working and just before it is made live on the main template. -- (M o r p h | ^C | _T)

00:05, 27 August 2009 (UTC)

If there's an issue where the template adds a category it shouldn't.... the template won't mess with the category at all. Since we're going to have to update pretty much every item in the game come 4.0, now's as good of a time as any to get the edge cases fixed so they won't be a problem in the future. /Dev hasn't been messed with in a few weeks... what other cats do we need? --k_d³ 19:05, 31 August 2009 (UTC)

Added a location request parameter option... although this could just be handled independently if it would just be easier. This also might lead into not just <instance> items categories, but also <zone> items categories (like The Barrens items) for non-world drops of course.... which just put a thought in my head, Category:<quality> world drops

(^Sssss/_Slithered) 22:57, 31 August 2009 (UTC)

As mentioned above, would not this be the time to make the categories Category:WoW <blah blah blah> instead of Category:World of Warcraft <blah blah blah>? Then we could go and remove all of the World of Warcraft categories with a bot or such (in preparation for the 4.0 changes - so we will not have the 30,000+ currently on file and any future items between now and 4.0?) -- (M o r p h | ^C | _T)

00:13, 1 September 2009 (UTC)

Added a set request option. -- (M o r p h | ^C | _T)

00:39, 1 September 2009 (UTC)

These aren't sets, they're items. --Pcj (T•C) 02:23, 1 September 2009 (UTC)

Then call them Tier # items (instead of Tier # sets) - you are disagreeing over semantics (words) but they idea of them being group together still remains the same - Since they are already Grouped that way now. -- (M o r p h | ^C | _T)

08:56, 1 September 2009 (UTC)

No, I have a problem with the size of the category more than the name, we should have the sets be categories and within those have the set items. It would make it much more navigable. Hopefully I explained it well enough. --Pcj (T•C) 12:28, 1 September 2009 (UTC)

That does not make sense to worry about the size of Arena 1, Dungeon set 3, or Tier 9 (because tier 9 will only be as big as Tier 9 only, it will not have tier 10 or tier 1 items in it). Every ITEM type category we have will need to be reworked, if you are worried about their SIZE. -- (M o r p h | ^C | _T)

17:07, September 1, 2009 (UTC)

We would have to break down every Simple Category, Armor/Weapons category, Gems catagory, Quest category and Profession category currently listed as active by k_d³, because not ONE of them is getting any smaller, each one grows with each and every new Tier set and Arena season. -- (M o r p h | ^C | _T)

17:18, September 1, 2009 (UTC)

The more specific the category, the greater the need to be able to identify individual items in it. We do indeed have general categories with thousands of pages per category. And they are not amenable to 'browsing'. Yes, we're concerned with size of categories. The larger they are, the less useful they become, the more likely breaking the category down into subcategories would be a useful change. Thus, "poor weapons" instead of just "weapons", for instance. Or "Green gems" over "gems". --Eirik Ratcatcher (talk) 17:26, September 1, 2009 (UTC)

My recomendations were specific and easily identifiable and easily grouped, with the exception of the Class items. Tier 1 items would only have tier 1 items, the same same with Tiers 2, 3, 4, 5, 6, 7, 8 and now Tier 9, as well as with the Arena items (they can NOT grow larger unless blizzard adds to them later and still they can not get too much larger because blizzard adds new Tiers / Arena seasons every patch or two, so the size complaint has no merit in this case, other than the Class items. -- (M o r p h | ^C | _T)

17:42, September 1, 2009 (UTC)

Categories already added to /Dev

Simple categories
- Category:Bags
- Category:World of Warcraft book items
- Category:World of Warcraft conjured items
- Category:World of Warcraft key items
- Category:Lockboxes
- Category:World of Warcraft socketed items
- Category:<Faction> rewards (of Category:World of Warcraft faction rewards)
Armor/Weapons
- Category:World of Warcraft <cloth-plate> <slot> items
- Category:World of Warcraft <quality> (bows|crossbows|fist weapons|guns|neck items|polearms|staves|trinkets) Note: Neck items not supported fully.
- Category:World of Warcraft <cloth-plate> items
- Category:World of Warcraft <quality> items
- Category:World of Warcraft <slot> items
Gems
- Category:<Quality> gems (of Category:World of Warcraft gems)
- Category:<Color> gems (of Category:Socketable gems)
- Category:<BoP/BoE> gems
Quest
- Category:<Quality> quest items
- Category:<Quality> quest starting items
- Category:<Quality> quest rewards
Profession
- Category:World of Warcraft <profession> <recipe> items

Categories still to be added to /Dev

Location
- Category:<Zone> items
- Category:<Quality> world drops
- Category:World of Warcraft <quality> finger items (of Category:World of Warcraft finger items)
- Category:World of Warcraft <quality> neck items (of Category:World of Warcraft neck items)

Categories that will be ignored by /Dev

?

Parameter |doc=

I added the parameter |doc=<something>.

This will keep the template from adding any categories other than the hidden (Category:Item pages). This will keep the template in line with any policies governing the template {{Removedfromgame}}. -- (M o r p h | ^C | _T)

04:43, September 6, 2009 (UTC)

Events

Should probably add an event parameter as well. I'm still trying to figure out exactly where its placed in the in-game tooltips...

Seems to be somewhere after the slot type and before ilvl. Currently we've been using either |instancebind (which comes before things like BoP) and |skill (which comes after ilvl). Sssssssssssssssssssssssss For Pony! (^Sssss/_Slithered) 23:57, November 6, 2009 (UTC)

Revision as of 23:57, 6 November 2009 (view source) Coobra (talk \| contribs) (→‎Events: new section) ← Older edit		Revision as of 23:59, 6 November 2009 (view source) Coobra (talk \| contribs) (→‎Events) Newer edit →
Line 459:		Line 459:
	Should probably add an event parameter as well. I'm still trying to figure out exactly where its placed in the in-game tooltips...		Should probably add an event parameter as well. I'm still trying to figure out exactly where its placed in the in-game tooltips...

−	Seems to be somewhere after the slot type and before ilvl. {{User:Coobra/Sig4}} 23:57, November 6, 2009 (UTC)	+	Seems to be somewhere after the slot type and before ilvl. Currently we've been using either \|instancebind (which comes before things like BoP) and \|skill (which comes after ilvl). {{User:Coobra/Sig4}} 23:57, November 6, 2009 (UTC)

Wowpedia

Talk: Tooltip

Revision as of 23:59, 6 November 2009

Contents

List of Archived Talk discussions

Arena rating

Double-quotes in name messing with float/font

Cooldown format

Non PNG File Extensions

Achievement Tooltip Ideas

Best current practice for usage

Feral attack power

No level requirement

False positives for Pages which may need their tooltips updated

Template:Tooltip/doc

Token refund

Bug: Mail (armor items)

Jewelcrafting

item level

Support for transmute spells

Support for unique equip types

Using Template Tooltip to categorize

Picking it back up

Categories already added to /Dev

Categories still to be added to /Dev

Categories that will be ignored by /Dev

Parameter |doc=

Events