BACKPAiiN {"ops":[{"insert":"An option to configure in "},{"attributes":{"bold":true},"insert":"Account Settings > Site Settings "},{"insert":"the default view for a cards "},{"attributes":{"bold":true},"insert":"In Deck"},{"insert":" section to automatically default to the "},{"attributes":{"bold":true},"insert":"Exclude Maybeboard"},{"insert":" option. \n\n"},{"attributes":{"underline":true},"insert":"Use Case"},{"insert":"\n\nWhen deck building I will regularly want to know if a card that is listed as Owned or Other Printing in the Collection Status is available for a deck or not. When brewing a new deck or updating an existing deck I will use the Maybeboard section to move cards I have cut from a deck into, or cards I am considering adding to a deck, or just cards I'd like to keep 'on the radar' for that deck, should I choose to lean into a slightly different archetype or power level etc. \n\nThis means when brewing a deck my routine is to usually click on all the cards I Own or have Other Printings of, take a quick count of how many I own in the "},{"attributes":{"bold":true},"insert":"Collection Records "},{"insert":"tab and compare that with how many decks I am currently using them in in the "},{"attributes":{"bold":true},"insert":"In Deck"},{"insert":" tab, which requires each time I open the card view to update the In Deck tab and select the 'Exclude Maybeboard' option. \n\nThis over time is becoming a slightly more laborious process, as my collection expands and the amount of decks I have matching cards in increases, my last brew for example had 80% of the cards listed as owned/other printing and most of which needed verifying this way.\n\n"},{"attributes":{"underline":true},"insert":"Current Workaround and Request"},{"insert":"\n\nCurrently I am running a script in my browser to append the 'excludeOutOfDeckCards=true' parameter to the /api/cards/inDecks/ API calls which does do the job but it's not actually checking that option on the In Deck view and I do find myself double checking it from time to time. If there was some kind of configurable persistent client-side setting this would be ideal.\n\nThis feature has a couple other duplicate requests listed below:\n\n"},{"attributes":{"bold":true},"insert":"CrimsonD87 - "},{"attributes":{"link":"https://archidekt.com/forum/thread/23878223/1","bold":true},"insert":"Here"},{"insert":"\n"},{"attributes":{"bold":true},"insert":"hampusr - "},{"attributes":{"link":"https://archidekt.com/forum/thread/16187558","bold":true},"insert":"Here"},{"insert":"\n\n\n\n\n"}]}
0
{"ops":[{"insert":"We can add a cache to those flags. They should just persist from the last state you left them in. \n\nTbh I'm a bit confused why i left those other posts on read. I read every post that hits the dev forum, and it's unusual for me to not reply to posts. My only guess is that I thought \"oh just cache that\" then forgot to go back and actually add the feature. \n\nI'll add the caching next time I sit down to work. \n"}]}
1
{"ops":[{"insert":"That would be perfect.\n\nAppreciate the prompt response as ever, thank you. \n"}]}
0