Android:
Cool that this finally works…
Kind of odd that when a notification exists and a player is in-game, that the notification tractor beams the player to the source of the notification from the tavern. If a notification appears and the player is in a match, the player will be tractor beamed to the source of the notification when the player leaves the current combat game mode.
In addition to what Lyrian wrote above.
Occasionally when I leave the game in the background and do something else on my phone. When I come back to the game it will sometimes go straight to the tavern or kingdom defense, when I haven’t even seen the notification. If I then check for a notification I see it’s there.
NB: I’m not sure if this happens only when the game reloads itself or if it is both when you reloads and when the game just opens again. Using Android 13.
I forgot to mention that occasionally puzzle Quest 3 blinks to a black screen when receiving a notification for the game as well.
Hmm, it is intended that if you interact with the notification it will take to to the source - but I’ll pass on that if you are in a battle, there should potentially be a confirmation if you interact with the notification
The newer seasonal dungeons have switched back to not being random anymore, I keep getting the Emberwing battle in A Broken Dream, and the Jellyfish woman from the Poison Sea.
I’m on PS4.
Hi Jeto, are there any updates regarding when the Android fixes / 3.3.1 might be going out?
I have several kingdom-mates patiently waiting for the Android crashing to be resolved before jumping back into the game.
Hotfix 3.3.1 hopefully next week, but at this stage I don’t think it will include the Android issue. That’s still being worked on, as we are trying to find the root cause and a fix for it.
They had no luck with changing their graphic settings?
Accidentally posted this update on my latest information, in the wrong thread.
Thanks for the update I can pass along.
Unfortunately, no.
It affects me, as well on a Samsung S23 (not 24) Ultra. I can brute force through the model loading crashes on the phone, but others (such as my other half, Ailile) do not have the patience to reload the game through the crashes and are mostly taking a time out while these issues are resolved.
Checked in… so the hotfix WILL have a fix that should resolve it for a large chunk of devices, as far as we can currently tell.
Seems like I misunderstood the results of the testing we were all doing last week
Not something we have a list of, like if you have X model phone or tablet it will or won’t be resolved.
I was told today that the Immortal Shields no longer appear as a sacrifice to refine the quality of the Lucky Clover Ring (only Elven gear does now). Is this intended or a bug?
According to the notes, it should be intended.
I thought we weren’t meant to be getting common loot in level 100 chests anymore?
The limitation is only for lvl 100 ruby and diamond chests, which shouldn’t have common and uncommon gear.
I don’t remember getting any common gear before the update, and I’m pretty sure I had a common from a ruby chest.
Here’s hoping that the 3.3.1 hotfix addresses the model loading uses, as the Halloween skins crash on Android if viewed more than once.