{"ops":[{"insert":"(This is a Feature Suggestion --- I'd have said that in the title if I knew I was posting to the Dev Forum, but alas I cannot edit my title!)\n\n"},{"attributes":{"bold":true},"insert":"Current Behavior:"},{"insert":" When submitting a new deck from, e.g, an Arena export, the deckbuilder defaults to a random (?) edition if no set code is specified --- and, even when a set code is specified, it still tends to pick alternative art or foil versions instead of the 'default' printing of the card (Strixhaven: Mystical Archive and the Japanese alternate frames are particular offenders). This results in a deck full of cards tagged with that blue stripe --- i.e. \"you own this card, but not this edition\" --- requiring a great deal of manual intervention to set each card individually to an edition that appears in your Collection.\n\nSuggested Behavior: Whenever Archidekt isn't given enough information to know for sure the set and printing of an imported card, it should first check if the user owns a copy of that card in their Collection. If they do, the importer should automatically default to that version of the card. (If they own multiple versions of the card, then I'd suggest that it default to the 'basic'/'default' version of the card, rather than selecting randomly or leaning towards alternate art/promotional versions.) \n\n\n"}]}
Edited 6/23/2022, 7:10:16 AM
2
{"ops":[{"insert":"Yeah, this is a good suggestion that's received some attention in the past. I've actually got a thread going for it over in our Feature Voting subforum. I'd suggest leaving your support for it over there-- features that generate the most interest receive priority from us when we're planning out site development. This one isn't at the top of the list per se, but it's getting up there. \n\n"},{"attributes":{"link":"https://archidekt.com/forum/thread/2320735/1"},"insert":"https://archidekt.com/forum/thread/2320735/1"},{"insert":"\n\nThank you for the suggestion and I apologize for the confusion about where this was posting to! Only potential features vetted as possible by the team end up getting posted to Feature Voting, so a submission there from a user gets posted here in Development. That definitely could be made clearer. \n"}]}
0