Getting Card Sets to stick
TappedOut forum
Posted on April 13, 2014, 10:37 p.m. by NeoHazard
I have been having this issue almost right from the get go with TappedOut. I will build a list with the cards having the correct set associated with for the cards I have in paper. Randomly I will sign in and find that all the cards have been changed to their oldest printings only. Does anyone know of a way to stop this from happening? I just dont understand why it gets changed all the time.
That may be whats doing it. I use it some times to set foils and swap some cards but thats easy to stop. I'll give it a try. Thanks
April 14, 2014 6:14 p.m.
HarbingerJK says... #4
you can add the three letter acronyms for each set in the deck editing. For example if I want my basic lands to be Zendikar art I will write in as so:
6x Island [ZEN]
4x Swamp [ZEN]
April 14, 2014 8:39 p.m.
That feature seems to only work when it wants to. For instance in my deck Mistmeadow Skulk (PEDH) I tried using the common version of Vulshok Morningstar from Darksteel and have it as "1x Vulshok Morningstar [DST]" in my main board, but it still shows the uncommon 9th Ed. version. However the Oblivion Ring in the same list correctly shows the common Alara version when specified.
April 14, 2014 8:46 p.m.
HarbingerJK says... #6
I mean we are talking about an amateur website, it's all fan run and no one runs this website as a career so nothing works %100 of the time...not that I'm saying if there were professionals running the site that things would work %100 of the time...lol
April 14, 2014 9:03 p.m.
Yeah thats what I've done is set the set names to the correct ones but randomly it will reset them to the oldest printings. Its obviously not something that must work in order to use the site but just something thats bugged me for a while. So far not using the edit board feature seems to be keeping everything set correctly
Dritz says... #2
Have you been using the 'Edit Board' feature? When I've used that it auto-assigns sets to everything in the deck. I've never encountered this problem elsewhere though.
April 14, 2014 5:57 a.m.