antalsz {"ops":[{"insert":"I'd like to import decks by providing a list of Scryfall IDs and quantities, or something similar, as this is (isomorphic to) what I get out of the TCGplayer card scanner app, and this would let me create decklist containing the exact versions of cards I own very simply. I can do this easily with the"},{"attributes":{"link":"https://archidekt.com/collections/import"},"insert":" collection importer"},{"insert":", but not the per-deck \"text import\" screen, as far as I can tell. Is there another way to do this?\n"}]}
0
{"ops":[{"insert":"Unfortunately it is not currently possible to do that. \n\nI'm not strictly opposed to adding something like this. My main concern would be whether or not it's really worth the time to do that at all. Most people when importing a deck are doing so via copy paste, and usually when users are doing that they're using card name, set code, etc, which is currently supported by our deck importer. That and making the importer more complex could cause a bit of confusion for users who aren't really sure what they're looking at. \n\nI wasn't aware that the TCG app even provided an export that included scryfall IDs, that's news to me. The app itself doesn't provide a way to export collections beyond a clipboard copy and paste (which isn't large enough for most collections), so I stopped digging into it. \n\nWe can add this to feature voting and see where it lands. It's a good idea overall, I just don't know if the most important thing we should be working on. \n\n"},{"attributes":{"link":"https://archidekt.com/forum/thread/5945506/1"},"insert":"Feature voting thread link"},{"insert":"\n"}]}
Edited 11/21/2023, 9:36:56 PM
1
{"ops":[{"insert":"Supporting set code might be good enough for my purposes, actually – it doesn't let you distinguish between different arts, but my collection is basically all from Saviors of Kamigawa or earlier so that's not really a problem for me :-)\n\nIn terms of TCGplayer export: the app lets you scan to different lists, so I've been going through individual old decks and saving them to different lists. It can then export via email, which provides a CSV; the CSV contains TCGplayer IDs, not anything more standard, but "},{"attributes":{"link":"https://scryfall.com/docs/api/cards/tcgplayer"},"insert":"the Scryfall API supports lookup by those IDs"},{"insert":" so I can write a script to convert those locally, and I figured I wouldn't ask you to add a whole new kind of ID to your backend :-) But that CSV contains card name and set code, so generating a nice importable deck list should be straightforward for me to write a script for instead. (I think the names might be slightly different for things like double-faced cards, but again, Scryfall can solve that.)\n\nAnd as a fellow software engineer, I completely get feature prioritization and user clarity. Thanks for the prompt response!\n"}]}
0