{"ops":[{"insert":"Add a deck action to Cascade for X. \n\nRight now, to avoid looking past cards you would have cascaded to, you have to do a combination of peaking/revealing cards and moving them to the bottom of your library one at a time. There's 2 downsides to this:\nThe cards are in the same order on the bottom of your library instead of being a random order; and"},{"attributes":{"list":"ordered"},"insert":"\n"},{"insert":"It's quite cumbersome."},{"attributes":{"list":"ordered"},"insert":"\n"},{"insert":"\nIt would be really great to have a deck action the same as \"Draw X cards\" where you have \"Cascade for X\" where it will go to the first cascade-able card and shuffle the rest at the bottom of your library\n"}]}
0
{"ops":[{"insert":"Generally speaking we avoid implementing game mechanical actions (like cascade) for a few reasons. \n\nThere's a lot of actions that we could theoretically build shortcuts for, but we don't because frankly, there's just too many of them in MTG for us to reasonably start adding options for many of them (the menus in the playtester are already kinda bloated if we're being honest). But beyond that, it kinda just makes the playtester a bit more brittle. The way we've designed it, is that actions in the playtester nearly always have a IRL machanical equivillent. Moving X cards to XYZ, tapping XYZ cards, etc. To implement something like cascade, we'd have to start playing magic for you by checking the state of cards, CMC, card types, etc. Doing so not only cheats the user out of actually playtesting their deck, but as MTG is a complicated game, it will very likely result in odd edge cases that will cause further friction down the line. \n\nFor the cascade interaction, I'd suggest you play it the same way you would at a table IRL. You reveal the cards onto the table (or play area in this case) until you hit one you can cast off of the cascade trigger. From there, you move your card off the \"pile\" of cards in the play area, use multi select to select all those cards, then choose Move to => bottom of library shuffled. \n"}]}
1
{"ops":[{"insert":"That makes sense. Thanks for the quick reply!\n"}]}
0