We don't have these exposed yet on the pages themselves, they're only seen when linking the list on Twitter, Discord, etc. (Places that use meta data to display an image for a webpage)
The plan is to add a button to copy the image URL of the deck.
I've made some rather large changes to how we're dealing with these now and we shouldn't see any more cloudflare errors due to timeouts.
When you submit JSON, it is now destructive - anything not in your string is going to be removed from your collection if it previously existed. This was something we were missing for a long time and I'm happy to announce has changed.
Your collection will also now be queued without your browsing waiting for a response on its status. We update your local collection immediately based on the data submitted and then we store a copy when our queue has time to do so. There could be a potential issue during high site load where you will be browsing and we'll send you an old copy of your collection, but that should be quite rare and fixed shortly after as the details process on our end.
Previously we had two different systems for updates, the one that runs for deck tracking clients and the manual input here, now they both use the same system.
It looks like code wasn't updated in the correct space for this - my fault. I'm going to refactor it so we can get this data in the database, like it should have been from the start. I'll get this out soon and we'll run a recalculation of crafting costs across the site. Thanks!
It eliminates the hassle of the manual work involved in updating a collection, even if it is just copy-pasting a blob of JSON.
I'll have to dig deeper into exactly what is failing with it though. Cloudflare error is kinda weird, if it happens again I'd love the exact error you're getting and the code that comes with it so it can be referenced in logs.
It definitely should not be logging you out though, it makes me think you're being redirected to the generic server error page which does not contain any login data on it. If you go back to the homepage (or any page) from a server error page, you should be able to use the site as normal.
That brings back memories of dropping my Engi shortly after WotLK hit to pick up mining so I could "afk" farm gold. Making those green weapons to disenchant into Greater Cosmic Essence so that you could sell it at an insane premium. I made so much gold.
It's odd that this is happening at all though since the background image once loaded initially, should be cached locally and instantly loading.
With that said, this is a very easy fix and I could have sworn this was fixed at some point in the past - it may have gotten lost when we redid the way our theme works. But yeah, that's going out now and you can forget about seeing the white load once it goes live in ~5 minutes.
Pushed out another update to improve API response time to improve deckbuilder loading times and for everyone interacting with the collection manager manually.
Forgot to respond that this was fixed. The issue was due to an internal data change in how we flag decks based on the game mode they are meant to be played in.
The value!
Deployed code to fix issues with threads not updating.
Thanks, fixed!
Also, sorry about the slight downtime =)
Today's update includes a large upgrade to our underlying site framework so patch notes are thin as most of the work is backend related.
New Features
Hearthstone
Additions & Changes
Magic
Bug Fixes
General
Hearthstone
We don't have these exposed yet on the pages themselves, they're only seen when linking the list on Twitter, Discord, etc. (Places that use meta data to display an image for a webpage)
The plan is to add a button to copy the image URL of the deck.
We've covered Libram paladin enough :P. Paladin is currently destroying the ladder and certainly doesn't need any more help spreading the holy light.
It'll arrive
Happy Easter!
Additions & Changes
General
Runeterra
Hearthstone
Bugfixes
General
Hearthstone
Known Issues
General
I've made some rather large changes to how we're dealing with these now and we shouldn't see any more cloudflare errors due to timeouts.
When you submit JSON, it is now destructive - anything not in your string is going to be removed from your collection if it previously existed. This was something we were missing for a long time and I'm happy to announce has changed.
Your collection will also now be queued without your browsing waiting for a response on its status. We update your local collection immediately based on the data submitted and then we store a copy when our queue has time to do so. There could be a potential issue during high site load where you will be browsing and we'll send you an old copy of your collection, but that should be quite rare and fixed shortly after as the details process on our end.
Previously we had two different systems for updates, the one that runs for deck tracking clients and the manual input here, now they both use the same system.
Deploy is out with the change, dust recalculation is now taking place sitewide.
It looks like code wasn't updated in the correct space for this - my fault. I'm going to refactor it so we can get this data in the database, like it should have been from the start. I'll get this out soon and we'll run a recalculation of crafting costs across the site. Thanks!
Deploying, Happy Easter
Are you using HSTD on Windows? If so, I'd recommend using our Plugin
https://outof.cards/hearthstone/decktracker-plugin/
It eliminates the hassle of the manual work involved in updating a collection, even if it is just copy-pasting a blob of JSON.
I'll have to dig deeper into exactly what is failing with it though. Cloudflare error is kinda weird, if it happens again I'd love the exact error you're getting and the code that comes with it so it can be referenced in logs.
It definitely should not be logging you out though, it makes me think you're being redirected to the generic server error page which does not contain any login data on it. If you go back to the homepage (or any page) from a server error page, you should be able to use the site as normal.
That brings back memories of dropping my Engi shortly after WotLK hit to pick up mining so I could "afk" farm gold. Making those green weapons to disenchant into Greater Cosmic Essence so that you could sell it at an insane premium. I made so much gold.
It's odd that this is happening at all though since the background image once loaded initially, should be cached locally and instantly loading.
With that said, this is a very easy fix and I could have sworn this was fixed at some point in the past - it may have gotten lost when we redid the way our theme works. But yeah, that's going out now and you can forget about seeing the white load once it goes live in ~5 minutes.
Pushed out another update to improve API response time to improve deckbuilder loading times and for everyone interacting with the collection manager manually.
Forgot to respond that this was fixed. The issue was due to an internal data change in how we flag decks based on the game mode they are meant to be played in.
This has been resolved
https://outof.cards/forums/out-of-cards/site-updates/8560-out-of-cards-changelog-2020-03-31-v2
Additions & Changes
Hearthstone
Bug Fixes
Hearthstone
(NEW) Site