Sam Zimmerman

We have the "boosters/sheets" for other sets, why couldn't we use the same formatting for the list? That would also allow us to include relative rarities and weights of specific...

List sheets are available in each set json, starting with ONE. Other sets are incoming. ONE.JSON: `data/booster/set/sheets/theList`

This should be resolved for all current sets, with each set booster listing its own valid cards. Let me know if there are any other changes needed to the methodology....

I don't think there's a dependency problem. Let me look into it.

I started looking into it and then stopped having free time. The low hanging fruit is CardKingdom. The same source we use to get the names and links also exposes...

Packs have so many variations now that I've mostly been compiling each "pack variation" separately and choosing from that. Is there a particular reason that you need set boosters to...

Yeah so it sounds like you're actually looking for the EV number of cards, right? So a set booster on average has 11.25 cards, so in a box of 30...

I'm already working on building out the product size map here: https://github.com/mtgjson/mtgjson/pull/1061 Once that gets incorporated, feel free to let me know if there's a way I can improve it...

@mallardduck Does the solution here provide what you need? https://github.com/mtgjson/mtgjson/pull/1061#issuecomment-1529935404 @kodabb brought up that overloading `product_size` to mean too many things is not ideal.

Good catch. I think they're all supposed to use the tag `deck_box` for "boxes of preconstructed decks" but you're correct that they aren't getting flagged correctly. If you want to...