krvys 2 months{"ops":[{"insert":"Hello, Longtime member, first time Poster. I was hoping to request a function that takes all cards added into a deck or package, and compile a list of what tags they fall under from the Scryfall Tagger Project in a tab within the deck settings.\n\nFor example, if a deck or package has a lot of cards with the \"cheaper than mv\" scryfall tag, it can tell you the total number of cards that fit into that definition, as well as how many of them may fit into other tags, such as counterspells, or removal. (using as example because i had these cards open in a diff window)\n\nFunctionality like this could also help players identify subthemes in their deck they are unaware of, such as if they were building an elves deck, but were unaware of a counters subtheme they had, for example. It would also be a boon for people designing cubes on the site, as they would be able to easily see subthemes emerging they either want to focus on, or remove from the cube, and increase or decrease cards that fit into those subthemes.\n\n\nThere is the chance this functionality exists, and i have missed it. At the very least, I argue it is not easily viewable.\n\nI am also aware the Scryfall Tagger Project is not perfect, but i am hoping that this is a tool which can be of use to community members, and may encourage other members of the community to take part in it.\n"}]}
0
michael(Alpha User)
2 months{"ops":[{"insert":"While this all sounds like a pretty cool idea, the tagger api is still in a beta state, so I've been avoiding building anything using it until they've finalized it. Once it's finalized, I'll be more open to using that data. I just don't want to spend time building something, only for it to change our from under me if that makes sense. \n\nOnce the tag api is finalized this sounds like a neat idea! Though I'll need to verify that it's possible to build with whatever functionality they land on (and by possible, I mean both possible and feasible). \n\nFun idea though for sure! \n"}]}
1
krvys 2 months{"ops":[{"insert":"Makes sense. It was functionality i thought of specifically because i am designing a commander cube, and it would allow me to see a lot of themes and subthemes from my pool of legendary creatures, which i hoped would help inform some themes i was working on.\n\nBut avoiding building something until it has been finalized on there end makes a lot of sense. I just hope you consider that functionality in the future.\n"}]}
1
michael(Alpha User)
2 months{"ops":[{"insert":"While this all sounds like a pretty cool idea, the tagger api is still in a beta state, so I've been avoiding building anything using it until they've finalized it. Once it's finalized, I'll be more open to using that data. I just don't want to spend time building something, only for it to change our from under me if that makes sense. \n\nOnce the tag api is finalized this sounds like a neat idea! Though I'll need to verify that it's possible to build with whatever functionality they land on (and by possible, I mean both possible and feasible). \n\nFun idea though for sure! \n"}]}
0