Template talk:Legacy variant table header

Query legacy mods

For example taken Ornate Spiked ShieldOrnate Spiked ShieldChance to Block: 24%
Evasion: (120-135)
Energy Shield: (26-29)
Movement Speed: -3%Requires Level 33, 44 Dex, 44 Int+5% chance to Suppress Spell Damage

Is it possible to implement requests to mods? For example:

{{legacy variant table header}}
{{legacy variant table row|3.0.0|{{c|mod|{{#cargo_query:
 |tables=mods
 |fields=mods.stat_text
 |where=mods.id="AttackerTakesDamageShieldImplicit4"
 |no html
}}}}}}
|}

But to specify only the mod id. For example:

{{legacy variant table header}}
{{legacy variant table row|3.0.0|{{c|mod|AttackerTakesDamageShieldImplicit4}}}}
|}

Or interaction with the subject itself, as it is implemented in "Skill Gems" with tables "Skill progression"?

upd:

I realized that you can do it with the template {{Ml}}:

{{legacy variant table header}}
{{legacy variant table row|3.0.0|{{c|mod|{{Ml|AttackerTakesDamageShieldImplicit4|display=stat_text}}}}}}
|}

--Ruba159753 (talk) 21:44, 18 October 2018 (UTC)

Sure, you can do a query for mods but you will always get the most current version of the mods. It is probably not the behaviour you want when the purpose of the template is to show historical data. For example Forbidden TasteForbidden Taste
Quartz FlaskLasts 6.00 Seconds
Consumes 30 of 60 Charges on use
Phasing
+10% chance to Suppress Spell DamageRequires Level 27Recover (75-100)% of Life on use
25% of Maximum Life taken as Chaos Damage per secondYour reach exceeds your grasp.Right click to drink. Can only hold charges while in belt. Refills as you kill monsters. has Recover (75-100)% of Life on useLocalFlaskInstantRecoverPercentOfLifeUniqueFlask6
Intrinsic
Recover (75-100)% of Life on use but there are also static 75% floating around since it was first introduced.--Illviljan (talk) 02:19, 19 October 2018 (UTC)

I see. Didn't think.

--Ruba159753 (talk) 07:33, 19 October 2018 (UTC)

Legacy diff definitions

I wanted to ask what's the general opinion about the "diff" between legacy variant mods. Currently you have to update the diff for all variants if a unique gets an update. Wouldn't it more sense to display the diff from one version to the next one rather than the latest one?

How it's done at the moment (mod = removed or changed, not = added | compared to current version):

• Current Version
  • Mod B2
  • Mod C1
• Legacy Version 3.0
  • Mod A2
  • Mod B2
  • Mod C1
• Legacy Version 2.0
  • Mod A1
  • Mod B1
  • Mod C1 (As a side note {{c|not|Mod C1}} is not working on its own -> Bug)

How I suggest it to behave (bold = new, italic = changed, strike = removed | compared to previous version):

• Current Version
  • Mod A2
  • Mod B2
  • Mod C1
• Legacy Version 3.0
  • Mod A2
  • Mod B2
  • Mod C1
• Legacy Version 2.0
  • Mod A1
  • Mod B1

The second case has the advantage that only the latest "legacy" version has to be adapted and the changed can be tracked over the patches. Opinions? Molldust (talk) 22:25, 2 January 2019 (UTC)