Playtest Decks taking forever to update?

TappedOut forum

Posted on July 18, 2016, 1:14 p.m. by blinded2

The title explains it all, you have 60 cards in your deck and you change 4 of them and you hit "playtest" but 1 of the 4 cards you replaced are in your opening hand.

It seems to take at least 10m for it to update. Frustrating for anyone else? This did not happen a while ago, if I remember correctly.

Anyone know the "magic number" for how long you have to wait? Anyone want to shed some light on why its not instantaneous as it was before?

It makes me want to find a better option for online brewing. Unfortunately, I am not sure there is a better option.

I have not experienced this issue, but unfortunately it can take some time for changes to propagate across the site. Which version of the playtester are you using?

July 18, 2016 1:23 p.m.

TMBRLZ says... #3

I have experienced the same thing many times lately.

There's also a lag on the total card count. Your changes are remembered but the accompanying information across the site takes time to catch up.

I'll often just pretend the card is supposed to be the one I changed it for or whatever. It catches up eventually. Not too long a time.

July 18, 2016 1:45 p.m.

blinded2 says... #4

I'm using almost exclusively Version 1, version 2 is unplayable for me. Although, I have also tested both versions and they do the same thing.

Unfortunately, it doesn't seem to be 30s or 2m, its much longer and I may change more than 4 card. Changing 10 cards could really end up being confusing to try to pretend.

I usually end up just creating a whole new deck and copy and pasting. Pretty annoying sometimes.

Not trying to complain too hard here but its quite frustrating.

July 18, 2016 1:59 p.m.

sameraii007 says... #5

I've waited DAYS for the Playtest to update. I've restarted my computer. Cleared my browser history. Changed to a different browser. Nothing seems to help. I don't know if creating the deck in Chrome is the problem????

July 19, 2016 5:59 p.m.

blinded2 says... #6

I've tested all the browsers. Its nothing on our end that makes sense. It has to be the site

July 19, 2016 6:20 p.m.

This discussion has been closed