Talk: Tooltip

Description

Creates a WoW styled tooltip for items and characters.

When using {{effect2}} for sockbonus please specify sockbonus with a null value (eg.sockbonus=), and use sblink= instead.

When using {{effect2}} for effect please specify effect as the effect type (eg.effect=Use:), and use elink= instead.

qitem, qbegin, locked and socket require any value to display, qitem=1 or qitem=yes for example.

unique and unique-eq require being set to no value or an amount greater than 1 when applicable. Eg. unique= = Unique and unique=5 = Unique (5).

locked will automatically add "<Right Click to Open>" for effect.

rep and rfaction work together. Example: rep=Friendly, rfaction=Argent Dawn

For multiple items for a single parameter (attrib, sockets, effect) simply use <br /> after each value for that parameter.

For bind use the following:

• BoP - Binds when picked up
• BoE - Binds when equipped
• BoU - Binds when used

create and createq should be used together eg. create=Runed Copper Pants and createq=Uncommon.

Please use {{socket}} for sockets and {{cost}} for vendor and sell.

Syntax

{{Tooltip|<float=> |<width=> |<icon=> |<stack=> |<name=> |<quality=> |<bind=> |<duration=> |<qitem=> |<unique=> |<unique-eq=> |<qbegin=> |<type=> |<slot=> |<speed=> |<dmg=> |<dmgtype=> |<bonus=> |<bonustype=> |<dps=> |<armor=> |<instancebind=> |<block=> |<attrib=> |<req=> |<sockets=> |<sockbonus=> |<sblink=> |<durability=> |<locked=> |<bag=> |<races=> |<classes=> |<rep=> |<rfaction=> |<skill=> |<level=> |<effect=> |<create=> |<createq=> |<mats=> |<charges=> |<comment=> |<desc=> |<cooldown=> |<cast=> |<vendor=> |<sell=> |<ilvl=>}}

Named parameters can be in any order and any or all can be left out.

Example

{{Tooltip

|float=right

|width=18em

|icon=INV_Axe_34

|name=Zulian Stone Axe

|quality=Rare

|bind=BoP

|type=Axe

|slot=Two-Hand

|speed=2.80

|dmg=131 - 197

|dps=58.6

|attrib=+22 Intellect

|durability=100

|level=60

|effect=

Equip: +44 Attack Power.<br />

Equip: Improves your chance to get a critical strike by 1%.

|comment=Bears the mark of Jin

|sell={{cost|8|78|68}}

|ilvl=68

}}

Result

Template:Img

• Zulian Stone Axe
• Binds when picked up
• Axe
• Two-Hand
• Speed 2.80
• 131 - 197 Damage
• (58.6 damage per second)
• +22 Intellect
• Durability 100
• Requires Level 60
• Equip: +44 Attack Power.
  Equip: Improves your chance to get a critical strike by 1%.
• "Bears the mark of Jin."
• Sell 8 78 68
• Item Level 68

Rules for changing this template

We desperately need to clearly describe the rules we are going to use for changing this template. Please put them here. --Fandyllic (talk · contr) 6:47 PM PDT

For this specific template, the change should be suggested first on the talk page and agreed upon by several admins. Discussion on the IRC channel is likely, but the result of any discussion there should be posted here first. User:Kirkburn/Sig2 22:04, 21 March 2007 (EDT)

A good start, but I think we need to be more specific:

• What are several admins?
• Will notice of an upcoming change appear here before the change or after? After would be bad, but unless someone is actively watching this page, I guess its not a big deal.
• Where will notice of the change be posted here? I recommend at the top, preferrably in a section called "Approved Changes".

--Fandyllic (talk · contr) 11:29 AM PDT 22 Mar 2007

Discussion

Template:Archives1

Item Sets Integration

Looking for feedback and input on this. The current way we implement Item Sets is a touch sloppy, but it worked with the previous Wiki software. I think it's time to readdress this at this time, however, and I think embedding it into the Tooltip (only to be displayed on the item page, not when included) is the way to go to draw the parallel to the in-game tooltip.

I've come up with a few test articles for review:

• User:Tusva/Dev/SetTemplate - New Template that generates Item Set Text
• User:Tusva/Dev/Set - Example Item Set (embedded in Set Page, see User:Tusva/Dev/SetArticle)
• User:Tusva/Dev/Tooltip - Updated version of Template:Tooltip to include embedding item set
• User:Tusva/Dev/Item - Example Item Using Updated Tooltip Template
• User:Tusva/Dev/SetArticle - Example of an embedded Armor Set on a reformatted armor set page.

Ideally this would also initiate a re-evaluation of how we format Armor Set pages, both to include this set information with <onlyincludes> and to better present the information.

I think that this solution is important as, at the least, it'd reduce the TONS of Set Templates we have swimming around (Category:Set_Table_Templates) each of which has a separate article about that set. Best to keep the info all in one place that distributing it around, don'tcha think?

Anywho, I think this is worth looking into and coming up with a standard that isn't so bulky. -- TUSVA ~ T | C 19:57, 12 June 2007 (UTC)

Looks good to me --GRYPHON^tc 20:06, 12 June 2007 (UTC)

Any additional feedback? I'd like to start finalizing how we're going to implement these. -- TUSVA ~ T | C 19:57, 26 June 2007 (UTC)

I'd rarther avoid a listing of set items in every item tooltip - instead include set name linking to the set page, and the number of items in the set (something like Set: Battlegear of Wrath (1/8)). You also seem to have a slight formatting issue with {{spelllink}} and non-spelllink set bonuses. -- Starlightblunder 00:28, 27 June 2007 (UTC)

I think it's important information to list the other pieces in the set as well as the set bonuses, just like they appear in-game, which is the entire point. It's rather worth the effort. -- TUSVA ~ T | C 02:46, 27 June 2007 (UTC)

Color for extra armor

Perhaps I'm missing something, but I can't see how to mark increased armor value as green in some items' tooltips. Take a look at  [Tree-Mender's Belt] for example -- for this ilvl it should have 196 armor, but some of the itemization points were spent for increased armor value, hence the green color here. Should we mark it in similar way to Wowhead or leave it as it is now? -- Vysogota T / C

A few changes in /Dev

I've modified {{Tooltip/Dev}} to fix three issues:

• Unique and Unique-Equipped parameters currently do not handle 1 gracefully. (unique=1 results in "Unique (1)", dev version would give "Unique")
• sockets= argument is ignored unless socket= is also set. I believe someone made a typo, since socket= is not used for anything other than to check whether we need to include sockets=.
• There's no instancebind= parameter in current revision. Some items, like [Staff of Disintegration] are bound to a specific instance - something that our tooltips don't reflect at the moment.

Merge my changes? -- Starlightblunder 14:57, 18 June 2007 (UTC)

I would suggest making the instanceBind variable a link, as there is most likely going to be an article with the same name as the zone. And if we're talking about an update to the template, I'd like my previous suggestion (two sections above) of embedding the set_name field so we can move forward on adding those to tooltips. -- TUSVA ~ T | C 15:51, 18 June 2007 (UTC)

I've added another tweak to the unique and unique-eq parameter handling to /Dev (this removes the empty brackets we have currently appearing where no unique/unique-eq value has been specifies), as well as short set and setpc parameters for sets. Check it out the demo at Template talk:Tooltip/Dev and if you're okay with the new set stuff, we should merge it again soon. -- Starlightblunder 23:52, 21 June 2007 (UTC)

I have updated the Unique fixes, should see if there is anyone has feedback about the item set. --GRYPHON^tc 00:05, 22 June 2007 (UTC)

Source

'Source' should be added. I realize this has been mentioned before in the archives, but I would like to see it happen eventually. --Cisox 18:57, 26 June 2007 (UTC)

It was actually removed when we initiated parser functions. Tbh, that information should already be on the page, and in much fuller detail. --User:Sky2042/Sig 20:39, 26 June 2007 (UTC)

For most cases, Sky, I'd throw in with you. Devil's advocate: pages with tooltips have been used as effectively translcudable, using 'noinclude' and 'onlyinclude' tags. These cases, the rest of the source page is not included ... including that fuller detail. OTOH, context should cover most of these cases almost as well. --Eirik Ratcatcher 00:00, 27 June 2007 (UTC)