Template talk:Upgrade component infobox

Description

Isn't this always Double-click to apply to an item with an unused upgrade slot. or at least the default? - Yandere 17:37, 17 September 2012 (UTC)

Eeeyup. Are you saying we should make that a default part of the template? —Dr Ishmael 19:16, 17 September 2012 (UTC)

Yeah, because it saves a lot of typing. - Yandere 19:45, 17 September 2012 (UTC)

Infusion Subtypes

Perhaps this template should be modified to somehow represent the distinction between offensive, defensive, and "omni" infusions? I'm not quite sure how best to do that... --Felbryn 23:20, 26 November 2012 (UTC)

Recent changes

The recent changes of this template have lead to the situation that the pages for the runes DON'T show the statistics of the runes anymore, even if the statistics are still present in the "variables" parameter. Can anybody bring this back, so the wiki pages show these valuable information again? Balwin (talk) 12:04, 20 June 2013 (UTC)

Done. The template documentation needs to be updated.--Relyk ~ talk < 12:27, 20 June 2013 (UTC)

Thank you. Balwin (talk) 16:23, 20 June 2013 (UTC)

Sigils

Are not auto-categorised. --Rhynchelma (talk) 15:20, 22 May 2014 (UTC)

Nor are runes. --Rhynchelma (talk) 15:21, 22 May 2014 (UTC)

the clue was that only historical items were being categorized. It was a blunder earlier when historical properties were changed. -Chieftain Alex 15:28, 22 May 2014 (UTC)

I guess that implies you're fixing it. --Rhynchelma (talk) 15:29, 22 May 2014 (UTC)

PvP versions

Would it be helpful to add a parameter/property to this infobox to show which ones are usable in PvP? I think all of them use the same mechanics, so I'm not sure if it's appropriate to create new pages for all of them. PvP Build is listing the new/unlocked items, but not the default selection. —Mora 17:18, 10 July 2015 (UTC)

We can match the game type flag from the API.--Relyk ~ talk < 01:02, 11 July 2015 (UTC)

Improves

Would it be possible to adjust this template to use the improves parameters used by {{trait infobox}} alongside creating a 'related equipment' template to allow further automation on effect pages? Sunlion (talk) 02:32, 8 January 2021 (UTC)

What is the supposed outcome, given that majority of sigils just give a damage boost, most runes just give stats and one or two effects, and other upgrades give stats only? DJemba (talk) 08:01, 8 January 2021 (UTC)

As can be seen on pages like Bleeding, Chilled, Might, Regeneration and Swiftness, there is still quite a few upgrade components that apply effects. The proposed change would help keep a consistent format among the related equipment sections on effect pages, as currently there is many varieties on the formatting displayed on the pages. There does seem to be wide variety in the conditions required for effects to trigger, which would likely need to be considered if this proposal is accepted. Sunlion (talk) 08:47, 8 January 2021 (UTC)

(Reset indent) This has been suggested by Sunlion again today on another talk page. I think it's actually quite interesting to formalize the behaviour of runes and sigils such that they could be used in queries, so brainstorming a bit...

Some years ago I made an attempt with four properties:

• Has primary rune bonus
• Has primary rune bonus total
• Has secondary rune bonus
• Has secondary rune bonus total

which however is quite clunky. Furthermore, nobody updated the PvP changes (where it was mainly used) after February 25, 2020 in a reasonable amount of time, so I removed the main usage back there. But I think the general idea of this could be reused.

What about setting a record:

• Grants = <granted attributes/granted effect/granted effect duration>;<total granted number>;<granted type> - This allows to store an arbitary amount instead of just two. Note that the type could be used to differentiate between a granted effect and granted effect duration; not sure how to store the amount of stacks yet. Or would make a skill fact like subobject more sense?
• Improves = <improved effect/improved property>;<related rune bonus number> - set rune bonus to get a "description" to display, e.g. bonus 6, default to 1 for sigils, there just use the description itself.

Any thoughts? We would need some catchy property names, the rest would be quite straight forward, as unlike in the trait infobox, the whole cross link queries of which skills/traits are improved aren't required. --Tolkyria (talk) 23:15, 16 October 2021 (UTC)

Rune total

Inspired by an unintentional suggestion (the anonymous user thought we already had the feature) on Talk:Precision#Feedback 2024/02/14, today I have added a calculation for the primary/secondary bonus totals to this template for runes.

This uses Template:Upgrade component infobox/rune totals and sets four SMW properties. It stores the numbers without % signs to allow numerical sorting.

Is this something we want to keep or use? example query

If we then want to create tables of items where the primary or secondary total rune bonus is equal to a certain attribute, then I need to do something further. At the moment the stored string (either Property:Has rune bonus total primary label or secondary equivalent) is too long >72 characters to do a wildcard search (e.g. for [[Has rune bonus total primary label::~*Precision*]]) - per smw:Help:Search_operators#Wildcards ("string length"). There are some options to resolve this:

• Option A: Further modify all rune pages, specifying the bonuses in plain text in the infobox template, and using a formatting template to convert the rune bonus raw text (e.g. "+100 Condition Damage" into "+100  Condition Damage)") - I've prepared Template:Rune bonus in case we want this option.
  • As well as the bot run, this option involves the risk that some non-standard rune formatting is added somewhere in the future and we'll end up having to update the additional template.

• Option B: Only store the first 72 characters of the attribute in the text property (this would take something like <span class="inline-icon effect">[[File:Healing Power.png|20pxpx|link=Healing Power|]]</span> [[Healing Power|Healing Power]] and make it into <span class="inline-icon effect">[[File:Healing Power.png|20pxpx|link= - this makes the actual property for display fairly useless since its truncated halfway through, so I'd actually implement this as yet another new property (e.g. Property:Has rune bonus total primary label searchable).
  • Bit messy with additional properties but easier.

• Option C: Removing the span class="inline-icon effect" tag might be sufficient to get the string short enough to facilitate searching.

-Chieftain Alex 15:13, 17 February 2024 (UTC)

Added and implemented Option C. -Chieftain Alex 15:49, 17 February 2024 (UTC)

Also created Template:Rune list by attribute. -Chieftain Alex 16:18, 17 February 2024 (UTC)