Skip to content
This repository has been archived by the owner on Dec 21, 2018. It is now read-only.

Normalise set booster contents #521

Closed
mirror35 opened this issue Dec 20, 2017 · 5 comments
Closed

Normalise set booster contents #521

mirror35 opened this issue Dec 20, 2017 · 5 comments
Labels

Comments

@mirror35
Copy link

Set booster contents is not normalised. Booster rarity values do not match card rarities.

Suggest the following format:

booster:[
{type:"rarity", value:"Rare"},
{type:"name", value:"Steamflogger Boss"},
[
...options
]
]

I don't mind implementing this if it's something people want / there are no objections.

@fenhl
Copy link
Contributor

fenhl commented Dec 20, 2017

See also previous discussion starting at mtgjson/mtgjson#364 (comment).

@fenhl fenhl added the feature label Dec 20, 2017
@mirror35
Copy link
Author

mirror35 commented Dec 20, 2017

Thanks - I've knocked together a utility which normalises the data into the format given. The format is extensible so could cope with sheet rarity if this data is available in future.

From what I can see, booster information is hardcoded in the ./shared/set_configs/ directory - but I'm still learning the source layout so I'd appreciate confirmation that this is the case.

Also - is this information used in the code anywhere? Or is it just pulled into the final files when they're created?

Few examples:

TSP:

    "booster": [
        {
            "type": "rarity",
            "name": "Rare"
        },
        {
            "type": "rarity",
            "name": "Uncommon"
        },
        {
            "type": "rarity",
            "name": "Uncommon"
        },
        {
            "type": "rarity",
            "name": "Uncommon"
        },

...

        {
            "type": "rarity",
            "name": "Common"
        },
        {
            "type": "rarity",
            "name": "Special",
            "set": "TSB"
        }
    ]

UST:

        {
            "type": "rarity",
            "name": "Common"
        },
        [
            {
                "type": "rarity",
                "name": "Basic Land"
            },
            {
                "type": "name",
                "name": "Steamflogger Boss"
            }
        ],
        {
            "type": "rarity",
            "name": "Token"
        }

@aritsune
Copy link

is this still planned? it would be incredibly useful for what I'm working on

@fenhl
Copy link
Contributor

fenhl commented Apr 11, 2018

It doesn't seem to be a priority for any of the core maintainers, but a pull request would be appreciated.

@ZeldaZach
Copy link
Member

At this time, V4 has removed the "booster" field. It will return in the future when we can figure out how to normalize it. This ticket can be found at mtgjson/mtgjson#46

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants