crossoverAtt.9680

Same problem. Logged out after finishing Ch 11. When I loaded that character later I was back in the Wizard's Tower with no way to Nayos. Kind of a glaring oversight, particularly since it was the end of chapter. Looks like I'll have to replay Ch 11 as well.

No change on this for me with the 6/26 patches. Focus Assist on is terrible. Off is the micro flash every map change. Not listed in the patch notes, but that is clearly not definitive and we don't know whether it was implemented and doesn't work or it did not make the patch. Sort of underscores the point about the way the information is communicated. Obviously they have bigger problems at the moment.

If you want to comment on the quality and frequency of communication, please start a new thread with that as the topic. Someone did. I commented there. Someone moved that conversation here and cut out most of the context that differentiated that poster's question.

Chillax bro, the devs are aware of this issue and already stated that a fix is on the way :> Then it should say something like, "fix awaiting implementation" or something similar. Solved is pretty definitive and does not stop someone from thinking there is something wrong with their system, when the fault lies elsewhere. The last A-Net post about 10 lines above stated a fix was being worked on. That is not the same as "this should no longer be happening to you", which is what "solved" suggests.

They have marked this issue as "solved" in the Known Issue Tracker. Getting a little ahead of themselves. Nothing is really solved until you actually implement into the game and it works. Of course this has been going on for weeks and it seems a bit odd not to have put more effort into addressing it. Presumably adding a swim buff for a game that has done a lot to minimize water combat and travel was done for a specific purpose -- like the kind that lands on June 26th. Doesn't really help with the 24 keys I have sitting in my bag and can't use. https://help.guildwars2.com/hc/en-us/articles/231272908-Known-Issue-Tracker

Why is this marked as "solved" in the Known Issue Tracker (dated 6/13/18)? It certainly is not and there has been no change at all since it appeared with the 1803 update. https://help.guildwars2.com/hc/en-us/articles/231272908-Known-Issue-Tracker