{"ops":[{"insert":"Been setting up for a recent PCDH tournament and have been extensively deck-building. Began dabbling with a mono-black devotion Grey Merchant deck, and for some reason, despite having an uncommon printing, the system will not allow me to include good ol’ Gary as my commander. Wondering if this is a bug or if someone could shed light.\n\nThanks\n"}]}
0
{"ops":[{"insert":"Unfortunately, this relates to the way Scryfall stores pedh data in their card json. Any card that's ever been printed at common has the \"legal\" tag while any creature that's been printed at uncommon and "},{"attributes":{"italic":true},"insert":"not"},{"insert":" common has \"restricted\". We look for that restricted tag to tell us a card is a legal commander, but that misses any creature that's also been printed at common at some point since it's only tagged as \"legal\". \n\nThe alternative for us would be to just look at a card's rarity to determine whether it's a legal pedh commander, but then legality would be dependent on you picking the right printing (i.e. the uncommon Gary from Theros: Beyond Death would be legal, but original Gary would not). That would maybe be a slight improvement, but it'd still be wrong.\n\nWe've voiced this concern to Scryfall, but they don't seem too bothered by it since a syntax search can yield all legal pedh commanders. Unfortunately, we really need that data in the json. If creatures printed at both common and uncommon had both the \"legal\" and \"restricted\" tag, it'd be perfect. \n\nThat said, I'm not expecting any action from them on this (nor do I really blame them since it probably looks like a non-issue from their end). We're looking into the possibility of creating an exception list for cards marked as \"legal\" that are okay to have as a commander (which would include Gary), but it's going to be a bit of a pain to implement and maintain. Since pedh only makes up .3% of our decks made since September, it hasn't made it's way to the top of the priority list just yet.\n\nSo until we do get the chance to implement our bandaid solution, I apologize for the inconvenience! Regardless, I appreciate you reaching out with the reminder that this is something that matters to some users. \n"}]}
1