-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MTGJSON as source & automated building #232
Comments
Sounds like it could be very useful. However, how would this work with token images that aren't on Scryfall? would they need special logic to pull the images from other sources? |
Don't mostly all new tokens have art? And for the old or custom ones we have the data ready in the current file. |
So, we would have a manually curated file of tokens that don't have scryfall/gatherer art alongside the automatically generated file from MTGJSON and then stitch those two together for the tokens file for Cockatrice? |
also, yes, most new tokens have art, although for whatever reason Jumpstart '22 tokens didn't have art at all |
Dropping a thought here:
MTGJSON has token cards, and with the last release (5.2.1) there are also information on related cards.
The data should be from Scryfall as well. We could build the database automatically rather than trying to keep up manually, similar to our spoiler files.
For the future, once Oracle is not used anymore and there are ready-to-use, MTGJSON sourced card databases for Cockatrice, tokens can maybe be part of it as well.
The text was updated successfully, but these errors were encountered: