Template talk:Legacy variant table header

Query legacy mods
For example taken

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

But to specify only the mod id. For example:
 * }

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 :


 * }

--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 has  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 B2
 * Mod C1
 * Legacy Version 2.0
 * (As a side note  is not working on its own -> Bug)
 * (As a side note  is not working on its own -> Bug)
 * (As a side note  is not working on its own -> Bug)
 * (As a side note  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)