This makes a lot of sense! All the card markup uses the same formatting and they likely just have deck names inheriting it. I'm assuming its a mistake though and probably will be patched out if its causing client crashes.
Or they'll make it a real thing (which would be awesome) and handle bad formatting :D
Thanks for the report. Going to get those removed real quick...
Also, I should mention these were written in a way that people stuck would always be able to get tips from the comments so for those that instantly clued in on it, it would feel a bit more rewarding. Some of these are also very easy to Google, not that I'm saying anyone should do that but it certainly is a good resource when stuck!
Psymon wasn't able to respond here but got in touch with me off-site with some more information.
The issue was isolated to Edge and has been fixed. Edge users also weren't able to reply to comments, use the navigation properly, and all other sorts of JavaScript things. We have so few people on Edge that these things can go unnoticed.
I'd say yeah, we should probably test things out in Edge more often, but now that the newer versions of it are based on Chrome's rendering engine, that isn't really going to be needed.
I had a similar issue with my fingers just being a bit too big at times and I even have a larger than average phone screen now that I think about it. Gah, word searches on mobile really aren't that great. I definitely think there are some ways we can help improve the mobile accessibility in the future.
It should work by pressing the first letter and then dragging across the other ones.
If you're having an issue, please let me know your device type and browser and we can potentially look into it. I recommend making sure your browser is up to date on your phone though - I know I've encountered some people in the past that haven't had that be the case and it has caused issues.
The word search does work much better though with a more traditional setup. If the grid had of been a few columns less, it would work much better on mobile. Its a little disappointing this kind of puzzle doesn't translate well to mobile when a lot of words are involved.
The intention was to have the scavenger hunt up and ready by now but there are some last-minute things that need to be adjusted with it. Apologies for the delay!
So you're saying us planning on doing these throughout the year based on ongoing events would be a positive then? =)
Really happy with the response so far honestly. I wasn't entirely sure if this was going to succeed with the crowd but it's been overwhelmingly positive!
I love our little ferocious unicorn mutant!
Oops! That's been fixed.
Welcome to the club, EpicPickle! Glad to see more people putting an end to the lurking =D
Crayons. WHY DID I CHOOSE TO DO THIS WITH CRAYONS?!?!
I recommend not using crayons. Tough to get any detail. Sorry Priests, Druids, and Demon Hunters for I have failed you.
At least we don't have a huge Magic Arena logo on it! Haha
This makes a lot of sense! All the card markup uses the same formatting and they likely just have deck names inheriting it. I'm assuming its a mistake though and probably will be patched out if its causing client crashes.
Or they'll make it a real thing (which would be awesome) and handle bad formatting :D
Cheater! <3
Thanks for the report. Going to get those removed real quick...
Also, I should mention these were written in a way that people stuck would always be able to get tips from the comments so for those that instantly clued in on it, it would feel a bit more rewarding. Some of these are also very easy to Google, not that I'm saying anyone should do that but it certainly is a good resource when stuck!
That's the plan! It just would have been weird to leave her out when all the other champions were included.
Not a great user experience though I can agree.
Would love some constructive feedback on how you think things could be improved!
Number 8 is my personal favourite of the clues.
The search won't be going away and thereare no plans to turn the achievement off for it that grants the reward so it'll remain accessible forever.
Psymon wasn't able to respond here but got in touch with me off-site with some more information.
The issue was isolated to Edge and has been fixed. Edge users also weren't able to reply to comments, use the navigation properly, and all other sorts of JavaScript things. We have so few people on Edge that these things can go unnoticed.
I'd say yeah, we should probably test things out in Edge more often, but now that the newer versions of it are based on Chrome's rendering engine, that isn't really going to be needed.
I had a similar issue with my fingers just being a bit too big at times and I even have a larger than average phone screen now that I think about it. Gah, word searches on mobile really aren't that great. I definitely think there are some ways we can help improve the mobile accessibility in the future.
Glad you enjoyed it!
It should work by pressing the first letter and then dragging across the other ones.
If you're having an issue, please let me know your device type and browser and we can potentially look into it. I recommend making sure your browser is up to date on your phone though - I know I've encountered some people in the past that haven't had that be the case and it has caused issues.
The word search does work much better though with a more traditional setup. If the grid had of been a few columns less, it would work much better on mobile. Its a little disappointing this kind of puzzle doesn't translate well to mobile when a lot of words are involved.
The intention was to have the scavenger hunt up and ready by now but there are some last-minute things that need to be adjusted with it. Apologies for the delay!
So you're saying us planning on doing these throughout the year based on ongoing events would be a positive then? =)
Really happy with the response so far honestly. I wasn't entirely sure if this was going to succeed with the crowd but it's been overwhelmingly positive!
My most despised parts of word searches! Glad you enjoyed it.
Oof. Yep that looks like that's an issue. Good workaround for now though! :D