With the release of KLD, token creation templating has changed. This has changed a lot of cards' Gatherer texts, but these changes haven't been reflected in MTGJSON. Are all card texts supposed to be updated with each version? When will this change be made?
Well... last printed set was only a suggestion. If this particular file is meant for card properties not from any specific set, then why include info about sets a card was printed in in the first place? I mean is it really bad to have rarity information alongside already provided set info? It's just a suggestion which - in my personal opinion - would make the specific file slightly more usable.
It would make that file more useful, yes, but where do you stop? The printings there are so you know where to find that card. Adding rarities would obviously be useful to people who need rarities, but what about artist, card number, etc? The idea is that AllCards is not a replacement for AllSets, but a purposefully light(er)weight file.
What is Wizards' position on this? Is a card's official rarity overridden by its most recent printing, or is it a property that's intrinsically unique to a printing?
I do not believe Wizards gives any "official" rarity to cards. It's intrinsic to a specific printing, though power-level and cost dictate similar rarities of reprints. If you look on Gatherer, you'll see that there is no "rarity" field, only colored expansion symbols in which they were printed.
What do you think about adding rarities (or at least the most recent) to AllCards-x.json? This really is the last thing missing for the card info to make it complete.
That file is meant specifically for properties of the card not from any specific set. To add rarity you need to decide what you're considering most recent. For example, do you include online only sets like vintage masters? What about media promos? Supplemental printed projects? It's not a decision that can be made without knowing the use case, so I'd recommend not adding it to that file.
I second Nis's comment. The order of the fields shouldn't really matter in well-formed JSON, and you should save yourself a lot of work by using a third-party parser!
mtgjson isn't intended to be an "API" necessarily. You probably should not be loading the json into your app clients straight from the site. Rather, the intention is to provide a comprehensive and consistent set of data so that you can build your own data set, specific to the needs of your app.
That being said, the only reason I can imagine you're getting Hearthstone sets is that there was a problem with your DNS and/or caching. Try clearing your browser cache, then figure out how to clear your DNS cache, and try again?
I emailed him yesterday offering to take over. I think it's a great resource and it'd be a shame to see it go unattended.
Currently I'm just working out how to get it up and running on my machine. It seems like before anyone will be able to take it over, it might need to be cleaned up a little around the edges. I'm currently fighting through node package errors..
I don't see any problem with the current format. Mtgjson is meant to be a serialized data dump, not a Gatherer replacement. I don't think it's its job to be assigning uuids when there are none. Nor do I think there's any problem necessarily with the way multifaced cards are handled. The only current ambiguity in the system are some of the early set's basic lands, which have no multiverse id. Otherwise, all the data is there you just need to put it together.
I see in your source code (shared/C.js) that you have some references like "magicCardsInfoCode", "essentialMagicCode", etc. These also show up in the json checked into the repository (e.g. json/4ED.json) but not the json on the site itself. These would be really useful for apps looking to add links to these various sites; can they be added?
Would it be possible to add to this database which sets have been release online? I know that there is an "onlineOnly" property, but I don't see any way to identify sets that have never been release online vs sets that have been release on both.
That being said, if you get me the columns you would want, I can try to whip something up for you.
It would make that file more useful, yes, but where do you stop? The printings there are so you know where to find that card. Adding rarities would obviously be useful to people who need rarities, but what about artist, card number, etc? The idea is that AllCards is not a replacement for AllSets, but a purposefully light(er)weight file.
I do not believe Wizards gives any "official" rarity to cards. It's intrinsic to a specific printing, though power-level and cost dictate similar rarities of reprints. If you look on Gatherer, you'll see that there is no "rarity" field, only colored expansion symbols in which they were printed.
Hopefully it's just temporary! In the meantime Internet Archive has a copy, which I believe includes the JSON files: https://web.archive.org/web/20151124175319/http://mtgjson.com/
That file is meant specifically for properties of the card not from any specific set. To add rarity you need to decide what you're considering most recent. For example, do you include online only sets like vintage masters? What about media promos? Supplemental printed projects? It's not a decision that can be made without knowing the use case, so I'd recommend not adding it to that file.
mtgjson isn't intended to be an "API" necessarily. You probably should not be loading the json into your app clients straight from the site. Rather, the intention is to provide a comprehensive and consistent set of data so that you can build your own data set, specific to the needs of your app.
That being said, the only reason I can imagine you're getting Hearthstone sets is that there was a problem with your DNS and/or caching. Try clearing your browser cache, then figure out how to clear your DNS cache, and try again?
Currently I'm just working out how to get it up and running on my machine. It seems like before anyone will be able to take it over, it might need to be cleaned up a little around the edges. I'm currently fighting through node package errors..
I see in your source code (shared/C.js) that you have some references like "magicCardsInfoCode", "essentialMagicCode", etc. These also show up in the json checked into the repository (e.g. json/4ED.json) but not the json on the site itself. These would be really useful for apps looking to add links to these various sites; can they be added?
Thanks!