Whole new "fun" waiting bug(s) to make you lose runestones?
I have now recently experienced twice that when leaving a chamber because no adequate team was formed within 2 minutes you are not returned to the chamber list immediately but you are kept waiting for that to happen while the timer keeps running down. Then you start to repeatedly tap the exit button hoping this will somehow 'help'. Eventually you exit.
The second time it happened with 4 players present. I tapped the exit button at 20 seconds. It took worryingly long. The timer went well below 10 seconds and had begun to make these alarming ticking sounds before I finally exited, making me worry that exiting would not happen before the timer would reach zero.
However after exiting I saw the counter of the room (Dark V) had dropped to zero indicating that you can now start over trying to form a new team, so I tapped on the chamber again. I got a message saying something that I couldn't join that room and then I suddenly found myself back in Dark V, with an Auror as the only other member (me Prof), 15 foes to go, three Acrumantulas (3, 4 and 5 star) and a five star Elite Werewolf. A setup that would no doubt require a substantial amount of potions to complete.
The Auror had started to fight the lowest spider. I watched it for a while until he had finished, it took him about a minute, and then left the room. I didn't want to leave while he was battling and afterwards finding himself alone in the room.
So there went another L4 stone. And after exiting the chamber I found I could not exit the fortress. The button reacted with a click, indicating my tap was registered, but nothing happened. The chamber buttons brought me to the runestone selection and back but I could not exit the Hogwarts fortress. I had to force close the app.
This waiting for the exit to actuallly be implemented is yet another very annoying bug which can apparently lead to other strange and unpleasant side effects.
I suspect that had I waited another couple of seconds before trying again this might not have happened. The chamber counter was somehow erroneously indicating an empty chamber. The clock counter maybe hadn't reached zero so I re-entered the chamber just before the timer reached zero. The Auror might have done the same, or he tried to exit later and the delay I experienced in exiting took too long for him causing the clock to run out before the exit was actually executed.
Whatever the case, this is another annoying bug. These bugs are piling up and they are taking a lot of fun out of the game very fast. I wonder whether others have experienced this chamber exit delay too.
I also wonder whether the first time I actually exited because I wasn't sure I hadn't lost a runestone. Could a 'ghost' version of you remain in the chamber as a part of this bug? Could this possibly (partly) explain people experiencing 'freeloaders'? I'm wildly theorising here but who knows.
These waiting bugs are very severe bugs that in my opinion should warrant a hotfix release in which these bugs are addressed. In my opinion this should already have happened several days ago. These waiting bugs are allowed to persist way too long.
Please fix this ASAP.
Posted Jun 4, 2020, 11:34 PM UTC · edited