You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that many platforms use their own convention for promotional cards or card sets.
When translating decks, the promotional sets have to be translated as well, as the target application may not understand the set abbreviations of the source application.
For example, TappedOut uses "000" for special promotional printings: http://tappedout.net/mtg-set/promo-set/, whilst Scryfall has a set for each individual promotional printing.
To solve this, some kind of translation layer is required.
Some promotional sets can be translated between TappedOut and Scryfall 1:1, as both sites have the same set, which only differs in the set abbreviation.
But the TappedOut "000" set needs some special handling.
A giant lookup table will solve this, but will be brittle as it has to be maintained manually.
If possible, a dynamic solution should be created for this case.
The text was updated successfully, but these errors were encountered:
luziferius
changed the title
Provide a translation layer for incompatible set abbreviations.
Provide a translation layer for incompatible set abbreviations. (Mostly affects promotional cards)
Dec 22, 2019
It seems that many platforms use their own convention for promotional cards or card sets.
When translating decks, the promotional sets have to be translated as well, as the target application may not understand the set abbreviations of the source application.
For example, TappedOut uses "000" for special promotional printings: http://tappedout.net/mtg-set/promo-set/, whilst Scryfall has a set for each individual promotional printing.
TappedOut set list: http://tappedout.net/magic-cards/
Scryfall set list: https://scryfall.com/sets
To solve this, some kind of translation layer is required.
Some promotional sets can be translated between TappedOut and Scryfall 1:1, as both sites have the same set, which only differs in the set abbreviation.
But the TappedOut "000" set needs some special handling.
A giant lookup table will solve this, but will be brittle as it has to be maintained manually.
If possible, a dynamic solution should be created for this case.
The text was updated successfully, but these errors were encountered: