Bloticus {"ops":[{"insert":"I take a modular building/upgrading approach to my decks. For example, when I buy a precon I like to swap out 10-15 cards, throw in my upgrades, and leave the original cards to be swapped back in. I also build pauper commander (PDH) decks and then create a 10-15 card sideboard of non-pauper cards and/or alternate commanders to play with the decks at regular EDH tables. Essentially, multiple versions of a deck coexist in a single box.\n\nWhat I end up doing is creating two separate deck profiles and maintaining the separate lists or using the snapshot feature.\n\nI think it would be beneficial to be able to keep both deck builds together concurrently and develop a method to be able to toggle between them. If a card gets removed or added from one view/build it could get flagged in the other view/build so that it can be properly allocated to either the sideboard or main deck. When reports are generated on the builds, it should be able to enumerate data for each separately as well as a combined analysis of what the cards in the sideboard offer (e.g., combo potential). It would be great to share either build or both together.\n\n"}]}
0
{"ops":[{"insert":"This is a fun idea, and it's one we've considered in the past. But ultimately the storage complexities it would add, we've deemed it not worth adding.\n\nWe already support deck snapshots, and using either color tags, or out of deck categories can get you 95% ish of the way there for this kind of use case. Pushing further into those kinds of features, while a really cool idea, ultimately is not a great use of time on our end sadly. \n\nTo do what you're trying to do, I'd recommend saving snapshots of the separate completed builds, and move cards into dedicated \"version\" out of deck categories. \n"}]}
0
{"ops":[{"insert":"Is it possible to at least have the combos algorithm identify if there are combos including the sideboard and have that be a toggleable feature to enable or disable?\n"}]}
0