Method of "preferring" blocks and sets per-page, per-deck, and per-card.

[NilsEnevoldsen]

Would be nice to have have a way of saying "this is a Time Spiral page, prefer e:TSP if available". Or, "this is a cawblade deck, prefer e:m11, b:zen, b:som if available". Or even, if especially ambitious, "this was a standard deck on May 6, 2001, prefer standard-legal sets if available".

Card tags would override.

Related to #8.

[NilsEnevoldsen]

This gets us part of the way there: https://www.mediawiki.org/wiki/Extension:Variables

Tricky part is how to fall back.

[Aspallar]

Bit of a necro but here's a less ambitious suggestion...

I have my doubts about the above being feasible through the Scryfall API, especially given that IIRC the API has no way of querying for a list of sets that contain a given card. Can't see a feasible solution to the above without a local db containing card data.

However what we could do is allow the cards in a deck to contain setcode/cardnumber preferences, just like the card tag does already, ofc theres no attributes to specify them, but we could extend the card parsing to support a format similar to the format used in the MTG:Arena game for import/export.

<amount> <card name> [(<set code>) [<card number>]]

e.g The following would all be valid
2 Opt
2 Opt (XLN)
2 Opt (DOM)
2 Opt (DOM) 60

I'm willing to code this if you think it's worth it.

Regards
Asp

[NilsEnevoldsen]

I'm skeptical that's worth it, not because it's not a good feature, but because I think it will be underused.

The original intent behind this issue was an easy way to improve a whole wiki page: a single tag would suffice for the whole page. I wasn't even primarily thinking about decks, but about card tags where users were (sensibly) too lazy to specify set/number.

I don't think there's a downside to your proposal other than the work needed to implement it. Should discuss syntax if you're interested, but Arena syntax seems like the right start. Maybe it should support all the syntax that Scryfall deckbuilder supports.