Magic Data

[Arch]

You're welcome to Marek. Not sure if you're a user or co-author at this point though.

{P} for generic on the one card.

What's this? I do not seem to have any {P} in the data. Did I miss a card?

[Ark]

http://gatherer.wizards.com/Pages/Card/ ... eid=214385

I consider this a bug in Gatherer already, as they already said the official symbol for that one card is {P} somewhere.

[Marek14]

You're welcome to Marek. Not sure if you're a user or co-author at this point though.

{P} for generic on the one card.

What's this? I do not seem to have any {P} in the data. Did I miss a card?

"Power user"?

[Marek14]

Spawnsire of Ulamog has a problem in its {20} activation cost

[Arch]

I consider this a bug in Gatherer already, as they already said the official symbol for that one card is {P} somewhere.

Yeah, seems like quite an obvious bug.

Also noted that Draco has the same problem as Spawnsire. Will fix these for future releases.

[Marek14]

BTW, there should be an Oracle update soon (probably happened already). Check Cocoon -- new wording should have it use +1/+1 counter.

[Marek14]

Prismatic Dragon has [2] instead of :

[Marek14]

Commander is on Gatherer

[Arch]

New release available.

[Marek14]

Pandora's Box doesn't have {} around symbols in text -- I did that one, so the same bug might exist for other Astral cards, and maybe dreamcast

[Arch]

Something is done in the incorrect order which causes those cards to not be cleaned up properly. Will fix in next release.

[melvin]

Thanks Arch and Marek14 for maintaining this data. It is very useful for prioritizing which Magic rules/effects to add to an existing game engine such as Magarena.

Two small requests:
1. List exactly one keyword ability per rule. I noticed that some of the cards lists multiple keyword abilities in a single rule eg "Flying, haste", this requires the user to further parse the text to split them.

2. Separate tag for type and subtype, currently both are tagged as type. Easiest would be to add a subtype tag

Thanks!

[Huggybaby]

Good suggestions melvin.

I would like to see more programmers using these files. I know it's fun to write *yet another* parser for Gatherer. But not as much fun as writing another deck or inventory viewer.

I think we can progress faster if we quit reinventing the wheel!

[Arch]

1. List exactly one keyword ability per rule. I noticed that some of the cards lists multiple keyword abilities in a single rule eg "Flying, haste", this requires the user to further parse the text to split them.

This is a good idea and it should be done. I still would like to be able to be able to map one-to-one with actual cards, or possibly have a way to convert back. I have two ideas for this so far, not sure I like either though.

Code: Select all

     <rulelist>
       <rule number="1">Flying</rule>
       <rule number="1">Trample</rule>
       <rule number="2">5: Each player sacrifices a creature.</rule>
     </rulelist>

     <rulelist>
       <rule>Flying, trample
         <rule>Flying</rule>
         <rule>Trample</rule>
       </rule>
       <rule>5: Each player sacrifices a creature.</rule>
     </rulelist>


Protection will/should be split with this as well. "Protection from red and white." -> "Protection from red." & "Protection from white."

2. Separate tag for type and subtype, currently both are tagged as type. Easiest would be to add a subtype tag

Will probably do something like this:

Code: Select all

     <typelist>
       <type type="super">Legendary</type>
       <type>Creature</type>
       <type type="sub">Bunny</type>
       <type type="sub">Ogre</type>
     </typelist>


[melvin]

For keyword abilities, the first encoding using "number=X" looks better as it does not nest the rules tag.

For types, the <type type="X"> looks rather weird having the word "type" repeated, how about <type kind="X">.