AshHemming 55 days{"ops":[{"insert":"We have a way to track our collections, yes?\n\nWe have a way to filter searched cards by ones owned, yes?\n\nBut there is currently no way to bulk import our whole entire collection because the import function on the deck builder doesn't read the CSV format that the collection page exports.\n\nInstead of worrying about that, just have a button to bulk import our collections directly into the deck builder. Ez pz, just have it scrape the collection of our choice and import it into the deck, with a selector for main deck, sideboard and maybeboard. It would make crafting practice decks with owned cards sooooo much easier, please Archidekt, please make this happen so I don't have to manually edit a CSV with hundreds of cards into a text format that the importer can read every single time.\n"}]}
Edited 5/25/2025, 11:25:59 PM
0
michael(Alpha User)
50 days{"ops":[{"insert":"Sorry I totally forgot to reply to this.\n\nCan I ask why you need this? Generally speaking collections are many many times larger than decks. The deck page isn't really built to handle more than 200-300 cards, so allowing for importing from your collection that can be tens of thousands of cards large, sounds like a generally bad idea.\n"}]}
0
AshHemming 49 days{"ops":[{"insert":"I suppose I hadn't considered people who have as you say tens of thousands of cards, but I'd like to use Archidekt to make decks out of the cards I physically own so I can test them and tweak them without having to go through my physical collection to do so.\n\nI get that that's already a filter in the sorting but I find that search function very slow and buggy when going through anything more than like 50 cards, and I tend to be biased towards cards that appear first in the list, so I thought it would circumvent having to deal with the search function so I wouldn't have to deal with the slow, buggy search function and could give the cards at the bottom of the list a fair shake as well.\n\nHowever if the deck builder page isn't built for a large amount of cards, then there's a different conversation that needs to be had on website optimization and overall memory handling because if the deck builder page can't handle that then the search function which struggles when scrolling down more than 50 cards certainly can't. Perhaps instead of an endless scroll, make card search page based instead.\n"}]}
0
