Tequatl broken after patch
It is not tequatl specific. It affected a lot of Shattererererer maps and also people trying for SAM in Field of Ruins. From what various comments:
- It tends to happen when a lot of people are entering or leaving an instance.
- It might be related to a bug in volunteering, i.e. kicking everyone from an instance instead of offering an opportunity to move.
- Even so, somehow the client isn’t synchronizing its progress to the sever, so it’s not so much a “roll back” (from the server side) as it is, “you say you did what? I don’t remember that.” (Equally frustrating to the player, but probably an ickier problem to solve for ANet).
There are a lot of similar posts, btw; you probably didn’t see them because you were looking at Tequatl.
It is not tequatl specific. It affected a lot of Shattererererer maps and also people trying for SAM in Field of Ruins. From what various comments:
- It tends to happen when a lot of people are entering or leaving an instance.
- It might be related to a bug in volunteering, i.e. kicking everyone from an instance instead of offering an opportunity to move.
- Even so, somehow the client isn’t synchronizing its progress to the sever, so it’s not so much a “roll back” (from the server side) as it is, “you say you did what? I don’t remember that.” (Equally frustrating to the player, but probably an ickier problem to solve for ANet).
There are a lot of similar posts, btw; you probably didn’t see them because you were looking at Tequatl.
Had it happening with Svanir Shaman yesterday, and Silvewastes today, just Tequatl is the most impactful encounter of them. Hence the search for world boss aswell. My bad for having a too narrow search field then I suppose.
This does fit well with your description of it happening together when lots of players leave the map in a short period of time, since that’s the only common denominator for me atleast.
Thanks for that last bullet point, describing the problem with better words and in a better way than I could
Still hoping for some official word on this, since the content is for all intents and purposes broken. Not going to put myself in a situation where a possible ascended chest vanishes in front of my eyes.
One of the QA people posted recently about this in another thread, starting with:
https://forum-en.gw2archive.eu/forum/support/bugs/World-Bosses-causing-crashing-and-rollbacks/5085494
Short version: it’s on their radar, it’s elusive (in that it’s hard to replicate), and please (please please) use the in-game /bug reporting tool whenever it happens so they can collect as much data as possible. The QA person seemed confident they have a handle on it (either fixed in today’s patch or they need to implement the more complicated fix that wasn’t ready yet).
I forgot to say: I’m really sorry it happened. I’ve only suffered it twice and all it did was prevent me from starting a world boss fight; I didn’t end up missing out on anything myself, so I’ve been very lucky.