there seems to be an inconsistency with coldsnap boosters and snow basics: basics have the rarity 'basic land'; basics show up in boosters; the booster field does not list 'land'.
Quick question... In the wake of MTGImage going down, will the imageName field still be populated with a unique value?
I'm interested in this, too, as I found a way to use this field (not to mention UID's are based on this field).
Yes. The imageName field will remain just as is for all current and future sets. I will be populating it with a unique image name for future sets just as I have in the past, so yes, it can still be used as part of UIDS. So in short, the closing of mtgimage.com will not be affecting the 'imageName' field in any way.
I add new sets to MTGJSON once Wizards adds them to Gatherer. They have not yet done that yet for Dragons of Tarkir. They usually add new sets anywhere from a few days to a week or more before the official release date of a set. I usually have it on mtgjson within 24 hours of it hitting gatherer.
there seems to be an inconsistency with coldsnap boosters and snow basics: basics have the rarity 'basic land'; basics show up in boosters; the booster field does not list 'land'.
So from my research, it appears that snow covered lands can sometimes replace a common in a booster of Coldsnap.
However I could not determine whether this is limited to 1 snow covered land max, or if you could potentially get more than 1.
Does anyone have any info on whether or not Coldsnap boosters can have more than 1 snow covered land?
MTGJSON doesn't currently support foreign language only cards. Thus MTGJSON only includes a set if an English version exists on Gatherer or MagicCards.info as this is where I get the data from. The set you mentioned does exist on magiccards.info but only in Japanese (http://magiccards.info/mps/jp.html) and mtgjson doesn't have support to parse this yet.
I saw that you have a github is there anything I could do maybe to help?
Hi Sembiance!
When adapting to the new character for choose abilities, I found a missing dot '.' in the ability text of Blizzard Specter`s first choose ability.
Somehow there are suddenly two dots in the Blizzard specter ability
Fixed.
Blizzard corrected their gatherer page (which is pretty rare for them to do, usually errors are there for good) which caused my internal mtgjson correction to double-fix the problem, producing an extra period.
I saw that you have a github is there anything I could do maybe to help?
I appreciate the offer, but even with a fully working pull request, I'm not sure I'd accept it right away. I'm not sure I want to start supporting non-english sets. Mainly because it's not just their initial inclusion, it's support going forward in the future which could mean a lot more work or a lot more things that could go wrong. So for right now I'm not looking to add the data.
Sembiance, thank you so much for your work on MTG Image and MTG JSON.
I own some non-English cards (especially in French) and would love to help by giving you the printed text on them. If one day you have the time to add foreign language data for other fields than names (I see this in your to-do list ;^)), please contact me!
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?
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!
I was stripping that data before publishing the web JSON files.
I have just updated the site to include the 'magicCardsInfoCode' code for all sets (except for the small handful that magiccards.info doesn't have). I've updated the docs too.
I'm still not publishing out the 'essentialMagicCode' as I only have that for 2 sets and don't feel like going and looking up the rest as nobody has ever asked for that info before. I also didn't include 'magicRaritiesCodes' as I only use it internally for some of the promo sets, which is a small number of the overall number of sets.
Just wanted to mention, the creatures in UGL seem to have the wrong "types" field:
currently they are "Summon"; I believe you intend them to be "Creature".
For things like this do you prefer to be informed here, or forked and mergerequested on Github?
Thanks, I'll look into this.
As for future bug reports/issues, probably best is to just file an issue on Github. No need to fork or send a pull request, I'll just handle the issue manually.
You can also e-mail me too, my e-mail address is on the page.
\
Just wanted to mention, the creatures in UGL seem to have the wrong "types" field:
currently they are "Summon"; I believe you intend them to be "Creature".
For things like this do you prefer to be informed here, or forked and mergerequested on Github?
So, Gatherer currently lists them as 'Summon', even for the 'Oracle' fields. I usually fall to the side of gatherer being the official, correct source, unless I find some sort of rule or article or proof otherwise. UGL is a pretty weird set, so maybe they don't follow the same rules as other cards?
Not really sure.
I can certainly change it all on MTGJSON's side to be the current modern way of doing things, but not sure if I should. Anyone have any thoughts on this?
So, ahead of Origins coming out, what do people recommend for linking Dual Faced Card halves together? I understand that it's problematic due to Gatherer considering them separate cards, which has a knock-on effect on what's in MTGJSON...
Private Mod Note
():
Rollback Post to RevisionRollBack
Minouris's Library - Collection manager and deck builder. It's nifty - Check it out!
If you had some form of UID, you could just add {"backside" : backside# }, but right now a key saying { "isBackside" : TRUE } and { "frontSide" : { whole data of the card's front } } seems usable. This way both front and backside are easily searchable and nothing would break for people using current setup. What do you think?
Something very similar - the ideal one would be cross-referencing IDs, but that would require IDs to be something universally present in the data. My only qualm with doing it that way would be that it would require much extra work on Sembiance's part - he'd have to post-process the data he gets from Gatherer, since I don't believe gatherer implicitly states what is the backsuide of what.
Actually, looking at the data, I think there may be something we can use already there:
If you look at the entry for Daybreak Ranger, you can see that it has a "layout" of "double-faced", and an additional entry in the "names" array naming the other face. When parsing the data, we can link the two cards together by cross checking the names array
Private Mod Note
():
Rollback Post to RevisionRollBack
Minouris's Library - Collection manager and deck builder. It's nifty - Check it out!
Yes and no. Yes, if all we're interested in the card for is deck building, because we only have to worry about one version of the card, which is almost always going to be from a set that is in Gatherer, and has a multiverseID. If, on the other hand, your app is concerned with collection tracking and Wizards decide to release a promo version of the card (promos being absent from Gatherer, and not having a multiverseId) then things get a bit more difficult.
Private Mod Note
():
Rollback Post to RevisionRollBack
Minouris's Library - Collection manager and deck builder. It's nifty - Check it out!
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.
Private Mod Note
():
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Quick question... In the wake of MTGImage going down, will the imageName field still be populated with a unique value?
Minouris's Library - Collection manager and deck builder. It's nifty - Check it out!
Yes. The imageName field will remain just as is for all current and future sets. I will be populating it with a unique image name for future sets just as I have in the past, so yes, it can still be used as part of UIDS. So in short, the closing of mtgimage.com will not be affecting the 'imageName' field in any way.
I add new sets to MTGJSON once Wizards adds them to Gatherer. They have not yet done that yet for Dragons of Tarkir. They usually add new sets anywhere from a few days to a week or more before the official release date of a set. I usually have it on mtgjson within 24 hours of it hitting gatherer.
So from my research, it appears that snow covered lands can sometimes replace a common in a booster of Coldsnap.
However I could not determine whether this is limited to 1 snow covered land max, or if you could potentially get more than 1.
Does anyone have any info on whether or not Coldsnap boosters can have more than 1 snow covered land?
I saw that you have a github is there anything I could do maybe to help?
I loathe creatures! Praise Prison and Land Destruction!
My Peasant Cube (looking for feedback)
Fixed.
Blizzard corrected their gatherer page (which is pretty rare for them to do, usually errors are there for good) which caused my internal mtgjson correction to double-fix the problem, producing an extra period.
I appreciate the offer, but even with a fully working pull request, I'm not sure I'd accept it right away. I'm not sure I want to start supporting non-english sets. Mainly because it's not just their initial inclusion, it's support going forward in the future which could mean a lot more work or a lot more things that could go wrong. So for right now I'm not looking to add the data.
I own some non-English cards (especially in French) and would love to help by giving you the printed text on them. If one day you have the time to add foreign language data for other fields than names (I see this in your to-do list ;^)), please contact me!
Barbarian Bully (JUD:C)
Breaking Point (JUD:R)
Fear (7ED:C)
Flash Counter (8ED:C)
Flying Carpet (7ED:R)
Gerrard's Command (PLS:C)
Goblin Lookout (LGN:C)
Goblin War Strike (SCG:C)
Inspirit (ONS:U)
Killer Instinct (GPT:R)
Lava Axe (7ED:C)
Lava Axe (8ED:C)
Might of Oaks (7ED:R)
Might of Oaks (8ED:R)
Persecute (7ED:R)
Reckless One (ONS:U)
Reprisal (7ED:U)
Sabretooth Tiger (7ED:C)
Scavenger Folk (7ED:U)
Sea Monster (7ED:C)
Spitfire Handler (ONS:U)
Treasure Trove (7ED:U)
Vodalian Mage (FEM:C)
Army of Allah (ARN:C)
Armor Thrull (FEM:C)
Balduvian War-Makers (ALL:C)
Bird Maiden (ARN:C)
Bird Maiden (ARN:C)
Carrier Pigeons (ALL:C)
Elven Fortress (FEM:C)
Gorilla War Cry (ALL:C)
Lat-Nam's Legacy (ALL:C)
Lat-Nam's Legacy (ALL:C)
Lim-Dul's High Guard (ALL:C)
Lim-Dul's High Guard (DKM:S)
Necrite (FEM:C)
Piety (ARN:C)
Piety (ARN:C)
Undergrowth (ALL:C)
Varchild's Crusader (ALL:C)
Veteran's Voice (ALL:C)
War Elephant (ARN:C)
War Elephant (ARN:C)
Winter Blast (MED:U)
Wyluli Wolf (ARN:C)
Wyluli Wolf (ARN:C)
Missing period:
AErathi Berserker (LEG:U)
Oh fun! More Gatherer errors
It's all fixed now, site updated. Thanks for the heads up.
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!
I was stripping that data before publishing the web JSON files.
I have just updated the site to include the 'magicCardsInfoCode' code for all sets (except for the small handful that magiccards.info doesn't have). I've updated the docs too.
I'm still not publishing out the 'essentialMagicCode' as I only have that for 2 sets and don't feel like going and looking up the rest as nobody has ever asked for that info before. I also didn't include 'magicRaritiesCodes' as I only use it internally for some of the promo sets, which is a small number of the overall number of sets.
G Green Stompy
RG Shamans
UB Mill
UG Infect
WUBRG Slivers!
Just wanted to mention, the creatures in UGL seem to have the wrong "types" field:
currently they are "Summon"; I believe you intend them to be "Creature".
For things like this do you prefer to be informed here, or forked and mergerequested on Github?
Thanks, I'll look into this.
As for future bug reports/issues, probably best is to just file an issue on Github. No need to fork or send a pull request, I'll just handle the issue manually.
You can also e-mail me too, my e-mail address is on the page.
\
So, Gatherer currently lists them as 'Summon', even for the 'Oracle' fields. I usually fall to the side of gatherer being the official, correct source, unless I find some sort of rule or article or proof otherwise. UGL is a pretty weird set, so maybe they don't follow the same rules as other cards?
Not really sure.
I can certainly change it all on MTGJSON's side to be the current modern way of doing things, but not sure if I should. Anyone have any thoughts on this?
Minouris's Library - Collection manager and deck builder. It's nifty - Check it out!
Something very similar - the ideal one would be cross-referencing IDs, but that would require IDs to be something universally present in the data. My only qualm with doing it that way would be that it would require much extra work on Sembiance's part - he'd have to post-process the data he gets from Gatherer, since I don't believe gatherer implicitly states what is the backsuide of what.
Actually, looking at the data, I think there may be something we can use already there:
If you look at the entry for Daybreak Ranger, you can see that it has a "layout" of "double-faced", and an additional entry in the "names" array naming the other face. When parsing the data, we can link the two cards together by cross checking the names array
Minouris's Library - Collection manager and deck builder. It's nifty - Check it out!
Minouris's Library - Collection manager and deck builder. It's nifty - Check it out!