Template talk:Item Tooltip

From Lotro-Wiki.com
Jump to navigation Jump to search
See Create new item to create a new item.
See Boilerplate:Item for a clean template and other options.

New archives created

See above for links to archives.

Wm Magill - Valamar - OTG/OTC - talk 14:03, 11 August 2013 (EDT)

Archives have been updated.

Oakheart (talk) 09:44, 16 July 2020 (UTC)

Suggestion: Barter Rewards / Barter Tokens

The "barter" line of this tooltip has been used both for "things that you barter with" and "things that you barter for". The OCD in me nags to change that. --Eirik Ratcatcher (talk) 20:07, 1 January 2018 (UTC)

That line is meant to be used for the “things that you barter with”; the template boilerplate says “used for items that can be bartered for faction standing or items” and it puts items in a category labelled as “These are items that can be bartered to an NPC in order to receive other items.” Using it otherwise is an error, though it’s easy to see why someone would fill it in for something you barter for, if they haven’t read the template description.
To fix it, we just need to delete that parameter when we see it used incorrectly. You could go through the Category:Barter Items if you’d like to be systematic about it. - Elinnea (talk) 14:02, 7 January 2018 (UTC)

Scaled parameter

I'd like to add a "scaled = " parameter to the template which if specified with a value will auto-categorize the item into Category:Scaled Items. Currently we don't have any comprehensive and standardized category for scaled items. Thoughts? --Gaerlin (talk) 23:30, 23 August 2018 (UTC)

How do we handle level-scaled items, for instance the tooltip, I see different approaches Invader's Lively Club vs Invader's Sharp Dagger. Do we always add a scaled table? Or only if multiple item lvls are confirmed? I would suggest highest level in the tooltip without the - ? addition, and a scaled table if multiple levels are confirmed. Tiberivs (talk) 18:53, 21 May 2021 (UTC)
Sorry I missed the explanations on the Boilerplate:Item , no further questions Tiberivs (talk) 09:15, 22 May 2021 (UTC)

Suggested update: Disenchantment

I noticed that this template doesn't yet handle the new "Disenchants into" bit. I wrote a proposal for updating the template (here) and would like a few kind, brave souls to look it over and someone with privileges to implement it when ready. The code is on the page source and split in two sections, one to handle the display and one to handle the category. They're nestled between big DISENCHANT comments. You can't miss 'em. I have a couple concerns though.

  1. The in-game tooltip has a bit of spacing before the disenchant icon shows up. I used 5px but perhaps it needs more to match the game? It also has a bit of vertical spacing between the first line and the item. Ten pixels seems okay, but what do others think?
  2. I'm not quite sure on the ordering for this parameter. It currently displays at the bottom of tooltips, below sell prices, so I stuck it at the end. However, stack and lotrostore parameters don't actually exist on in-game tooltips. Could somebody please tell me where to stick it?
  3. Plural name handling? Does this need to be a thing? If we go this route, we could repurpose the disenchant-amt parameter to handle this. This might be easier. Hmm.... Unless we want to categorize by item and amount. e.g. [[Category:{{{disenchant|}}} Items|{{{disenchant-amt|}}}]] Thoughts?
  4. There was a blank line sticking outside of an #if: statement just before the handling of 'stack'. It seemed out of place and doesn't match the in-game appearance, so I tucked it back into stack. If it shouldn't be like this, switch it back please.

Dadwhereismom (talk) 21:28, 12 January 2019 (UTC)

Decoration Slots

The decoration slots need updated to allow more than 2 deco slots. Also the deco slots are currently backwards if you put an item on deco-slot and deco-slot2 the deco-slot2 will show before the deco-slot on the tooltip.

Oakheart (talk) 09:28, 16 July 2020 (UTC)

Unique Use parameter

The unique_use parameter doesn't accurately represent the in-game text. The in-game colour is #26B27F, but it's currently #006400 here. In-game, the text is also displayed above the "Bind to Account on Acquire" text, not below. --Fanchen (talk) 03:20, 11 March 2021 (UTC)

Glory Rank

The line below needs updating—[[Glory]] currently links to Glory, a Champion trait. I'm not certain, since I don't do PVMP, but has it changed to Renown?

}}{{#if: {{{gloryrank|}}}
   | <li class="red">Requires: [[Glory]] Rank {{{gloryrank}}}</li>
  

Isi7140 (talk) 21:08, 15 November 2021 (UTC)

Junk and Task hardcoded flavor

Since there are some items that has custom flavors like Item:Frost-rimed Skin I propose we remove the hardcoded flavors from the template and just place everything in the flavor parameter. I have a bot script ready to do the change, together with some other minor fixes on these items, if people agree. --Drono (talk) 09:52, 20 February 2022 (UTC)

Fine with me! --RoyalKnight5 (talk) 09:58, 20 February 2022 (UTC)


Edit: Also for Trophy - it is currently replacing some valid flavors with the hardcoded value. --Drono (talk) 10:12, 20 February 2022 (UTC)
Removed. Running bot to update the item pages. --Drono (talk) 08:35, 23 February 2022 (UTC)

Monster Play effect

I don't have permission to change this template. Could we change the text for Monster Play effect so that it is red in color? --Pinkfae (talk) 21:58, 15 April 2022 (UTC)

Hmm, i looked a it and i'm not really sure how we decide what is shown red on tooltips, like minimum level also shows red if your level is too low. Monster Play shows red only outside monster play. So we should probably show all of these white or all of these red. --Drono (talk) 08:18, 19 April 2022 (UTC)
I'm in favour of keeping the text for these parameters white, for more readability etc. —RoyalKnight5 (talk) 09:25, 20 April 2022 (UTC)

Using CalcStat

How do we stand with using the CalcStat module for stats? I'm upgrading the delving gear to lvl 478, and applied CalcStat to calculate stats for  Pristine Keen Delver's Mask, which works great. If SSG changes something about recalculating the stats, the module will take care of that. Also if items are upgraded to a higher level (which is currently the case for delving gear), you only need to change the level parameter...thoughts? -- Tiberivs (talk) 21:39, 25 April 2023 (UTC)

Personally, I don't see so much of a problem in it if you know how to use it. At most CalcStat might not be updated some time and then stats remain as they were like static stats now.

Btw, for item level I like the use of a variable for it. Like below.

Pristine Keen Delver's Mask
  • Bind On Acquire
  • Item Level: 478+  
    (level-scaled)
  • Medium Armour
  •  
  • 2,855 Armour
  • +588 Agility
    +868 Vitality
    +2836 Phyiscal Mastery Rating
    +741 Finesse Rating
  •  
  • Basic Essence
  • Basic Essence
  •  
  • Normal
  • Durability 50/50
  • Minimum Level 140


or sometimes the item level used is higher than the displayed level, so maybe show it in that case (not for this item).

Pristine Keen Delver's Mask
  • Bind On Acquire
  • Item Level: 478(480)+  
    (level-scaled)
  • Medium Armour
  •  
  • 2,916 Armour
  • +601 Agility
    +886 Vitality
    +2896 Phyiscal Mastery Rating
    +757 Finesse Rating
  •  
  • Basic Essence
  • Basic Essence
  •  
  • Normal
  • Durability 50/50
  • Minimum Level 140


I think that I can still produce some spreadsheet with stat points, sell/scaling codes etc for each item. --Gisel Avaleazar (talk) 08:54, 29 April 2023 (UTC)

Aren't these items not already automatically updated by a bot? --Gisel Avaleazar (talk) 09:52, 29 April 2023 (UTC)


Primary and Vitality essence slots added in U38

With the new primary and vitality essence slots added in U38, this template needs to be modified to support these new types by displaying them in their appropriate colors rather than simply showing a number of basic slots. Perhaps adding new parameters such as ess_primary = y, ess_vitality = y, ess_basic = [1 .. 4]. If {{{essences}}} not blank, keep the current display format. Otherwise, display the primary (purple), vitality (green) and basic slots (orange). Sagarmatha (talk) 21:12, 14 November 2023 (UTC)

  • Even more complicated because there is also {{{essences-cloak}}}, {{{essences-neck}}} and {{{essences-pvmp}}}. Sagarmatha (talk) 01:18, 15 November 2023 (UTC)
  • So since
parameter essence slot
essences-cloak
essences-neck
essences-pvmp
then I think we can simply add {{{essence-primary}}} and {{{essence-vitality}}} to display blue and green essence slots and we can just re-use {{{essences}}} to display the number of basic essence slots (orange). Since there can only be one primary and vitality slot each, no need for coding it to support more than one. Need to add more testcases for those existing specific essences variables to ensure the changes don't break those and should be there anyways for completeness. Sagarmatha (talk) 02:40, 15 November 2023 (UTC)
  • Changes made in sandbox with updated testcases. Need to upload primary and vitality slot images and update the sandbox. Sagarmatha (talk) 03:19, 15 November 2023 (UTC)
afaik cloak and neck can also be just one, but i guess it was added as multiple in case there were changes later. I think that the template doesnt need to support more than one from start, but would probably better to use essences-primary = 1 instead of essences-primary = y. Than if in future there will be gear with more slots we wont have to edit all of the earlier gear and just change the template. Also i would vote for uniformly named parameters. --Drono (talk) 08:14, 15 November 2023 (UTC)