Specific Card Printing Codes

TappedOut forum

Posted on Oct. 14, 2011, 10:59 a.m. by ZaLiTHkA

I originally posted this in the 'Deck Help' sub-forum thinking I was just making a stupid mistake, but I'm starting to wonder if this isn't maybe a problem (or area for improvement) on the site itself. Original thread.

To summarize, while using the Deck Builder, I found a note in the 'Formatting Help' link that allows me to specify the exact printing of the card to use, such as [M11], [ARC], [DDG], etc. But it doesn't actually affect the card displayed in the deck itself.

First example: Dragonspeaker Shaman on TappedOut vs the MTG Gatherer page. Here it's listed as a 'Creature - Barbarian', on Gatherer it's a 'Creature - Human Barbarian Shaman'.

Second example: Quicksilver Amulet vs MTG Gatherer page. The image and flavour text are different, I know it's minor, but it would be nice if it worked. :)

Apparently this works properly in the Binder (though I haven't actually tried that yet), so is there any chance this could be updated/fixed in the Deck Builder?

Balthasar says... #2

If you click on the card Dragonspeaker Shaman you'll see that the creature type is correct 'Creature - Human Barbarian Shaman'. The only thing lacking is the picture....

While yes this would be nice you have to remember T/O is mostly worked on by a small crew of volunteers.

October 14, 2011 6:26 p.m.

ZaLiTHkA says... #3

I do realise the description for the cards are correct, I wasn't implying they weren't.

Just to clear it up, I meant no disrespect to the people who created/maintain this site, my apologies if I came across rude at all... As mentioned, I said 'apparently' for my note on the Binder simply because I hadn't tested it myself (it was mentioned in a reply on the original thread). While the two examples I provided were only there as examples of what I was trying to describe.

No problem if it's not going to change, I just figured I'd mention it and see if either something I was doing wrong, or if it was a problem that had been missed.

October 15, 2011 8:11 p.m.

This discussion has been closed