However, the player may have instead completed two runs (ten matches) with the same deck in a row, and in this case it makes sense to have multiple data points. If said player matched with more than one of the folks tracking their data, we would have at least two data entries instead of one. The player could have completed one run, thus five matches, on the same day or split them across several days. There can be duplicate data points of a deck being piloted by the same player in the same League run, which shouldn't be treated as if it were separate entries of the deck. Nonetheless, we believe the data may help highlight overall trends in the world of Pauper. Despite our sample size, averaging almost 43 matches a day, it is still only part of what happened on Magic Online during this time.
#Pauper metagame full
This neither comes from nor has any affiliation with Wizards of the Coast, and it does not offer a full picture of the metagame. After everything was done, we had 1,195 matches to analyze. This means removing duplicate entries when both players send their results, dealing with naming conventions, et cetera. I received everyone's data and was tasked with the merging, organization, and treatment of it. This data set was crowdsourced via players in the Pauper Leagues of Magic Online from February 1 to February 28, similar to the famous Challenge Projects of Vintage, Legacy, and Pauper. There I list the cards normally seen in each deck and discuss some of the naming conventions, things like why Boros instead of R/W. You can find clarifications on the naming of archetypes in Appendix 1: Deck Dictionary at the end of the article.
0 kommentar(er)
