Can anyone who is affected by this issue themselves please give me the following information:
Thanks everyone, we found the cause of the issue, it does require a client update, however we’ve made a temporary fix in the meantime. This temporary fix required us to visually hide Unlock Scrolls and Dooms Defeated in specific circumstances, the full details are here, please help me spread the word and share this article with your Guilds:
The temporary fix will be live on 5.0 soon (Switch). IT’s still being pushed out. Sorry about that.
This is out on Switch now too.
@SerfThomas I’m asking any players with that issue to try force closing and re-opening the game to see if that issue persists.
@Earnham Can you please link me to the bug report thread for this from 2 months ago so I can review it? I wasn’t able to spot it in the bug reports section when I went looking for it just now. If you can even just point me in the right direction to find it that would be very helpful, thank you.
Aha, so I can certainly understand your frustration if this is indeed the same issue (with the same cause) as the ToD issues we experienced on all platforms this week.
I can see from the thread that only 2 players reported it and I was leaning towards it being a technical issue based on the nature of the issue and the lack of bug reports on the topic.
I tried finding the tickets about it but they don’t seem to have the invite codes in them so they didn’t come up in my search. You would definitely have a response to them by now, I may have suggested some troubleshooting steps and asked some follow up questions to work out what caused this for you before taking next steps.
The reason we were able to act on this ToD so quickly was because we received MANY reports, which continued after the server issues were corrected, so from that point we knew it wasn’t the server issues causing it and clearly it wasn’t a technical issue as too many players were affected.
It is unusual for a bug of this nature to only affect 2 players, which is why my original leaning was it was a technical issue and that I needed to gather more information and try solutions which may work for individuals. It had nothing to do with which platform you were on.
If it is exactly the same issue, with exactly the same cause then I’m sorry I didn’t realise sooner that this was a bug. I would need to see the tickets from 2 months ago again to make sure it is the same bug.
It’s all fine if everyone tells you, but if they don’t tell a Dev, we’re not psychic, and yes this sort of thing could be a simple connection issue if 1 or 2 people report it, but when 50 people report it I start looking at “well was there some major internet shenanigans or did something on the game’s backend bork” because it points at a larger issue.
That’s why we do troubleshooting and why I asked the 2 players who reported in August to write a support ticket so I could troubleshoot with them so I could 1. Try to solve the issue for them or 2. Work out what was causing the issue. I can’t call an all stop on the programmers and server admins every time any player has a long loading screen - there’s too many factors playing into it and most of the time it’s nothing to do with the game itself - I try to do a logical ruling out of things.
Your issue wasn’t ignored, it was just handled via ticket as it didn’t appear anyone else had the issue as no one else said anything - next time tell your guild mates to never assume someone knows something just because you know it so we can actually help. We don’t want a broken game but we’re literally not psychic, if we don’t experience the issue ourselves we can’t know there is an issue.
devtrackers.gg