Fellguy 2 days{"ops":[{"insert":"Hello,\n\nI'm not sure if this is the appropriate place for writing this, but there's one... feature... that bothers me a little when creating decks, and maybe other people experience it too.\nWhen I add a card to a deck in building, it usually defaults to the latest version of the card. And because I like keeping my decks with accurate versions, I always have to edit it to a version I own.\nI believe it would improve the user experience if a card being added defaulted to a version owned by the user.\n"}]}
1
michael(Alpha User)
44 hrs{"ops":[{"insert":"So I've looked into this a few times and the reason I haven't implemented it is because there isn't a way to do it that doesn't punish non collection users. \n\nTo enable defaulting to editions owned, the card lookup process would need to look up which editions you own (obviously). This process is not a free one, and slows down literally every single card lookup that the site does (which is more than you might expect).\n\nThis trade-off might be worth it to some, but to the users who don't use the collection manager, that lookup (to check their collection) still needs to happen. Implementing a feature like this would slow down card lookups for those users. But even for the users who would want to use it, it slows down card search so much that using archidekt becomes a far worse experience. \n\nAs a comprimise, what we've done instead is implemented collection version overwriting into the card optimizer. When you run the card optimizer, it can swap all optimized cards to collection versions. This way it doesn't need to effect card lookups at all. \n"}]}
0
