Hi. I got one question: why does the Mercenaries -> Parties show me a list of decks, on the website?
Also, I don't seem able to complete the oozefest item of "visiting the mercenary parties list", even though i've accessed that section. Not sure if these 2 things are related or not.
Let me know if i'm doing something wrong. Thanks
Comments
Hi. I got one question: why does the Mercenaries -> Parties show me a list of decks, on the website?
Also, I don't seem able to complete the oozefest item of "visiting the mercenary parties list", even though i've accessed that section. Not sure if these 2 things are related or not.
Let me know if i'm doing something wrong. Thanks
Hey, I'm not sure if I understand correctly: what else would you expect it to show other than 6-man PvE or PvP parties for the mode? Or are you seeing something else? We'll have a look at the Oozefest thing.
I'm not having any problems completing the daily task for Oozefest. The Parties nav link is correctly taking me to the Parties feature on the site as I'd expect.
Could you please describe in detail exactly which steps you are taking and what you see when you are getting this problem?
I think I'm having the same issue and it's not just for Mercenaries only but also other portals. I'm not sure why but if you go to one of the portals it shows the decklist of whatever portal you were in before.
Sorry for the late reply. Here's a screenshot:
https://pasteboard.co/iUf1XKrTDj5h.jpg
The link in the titlebar is:
https://outof.cards/hearthstone/mercenaries/
As for the steps, i'm opening the main page, click on "mercenaries", then click on "parties".
Doing that again now seems to make the page show up properly, so i'm guessing some sort of caching issue.
Thanks for the more detailed report. Definitely seems like a caching issue of some kind and I know this one will be a huge pain to figure out because our deck widget system isn't the simplest thing. I'll see what we can do about it!
Not sure if you did anything, but I can't reproduce the bug anymore. Previously, it occurred on every "fresh" opening of the website (and I didn't update the browser i use).