Edit: probably not the cause (?), code was checked by Excru

End June/Begin July a staff member told me the dev team would fix a bug regarding the dungeon queue.

The bug: Players are able to move during Queue Waiting Time by opening and closing a book item/revelation.

To fix the bug, the devs inserted a code which affects all players. To prevent the players of moving around and acting, the code teleports players back to the

position they were when they queued/when they opened the book item/revelation.

Furthermore, after teleporting them back to their original position, it corrects their ability to move around by re-LOCKING them in place (you aren’t

supposed to move during queue). This fix did not work, and it does not need to work.

However the same code in the opening of the book item/revelation is applied during party questing CINEMATIC too.

I noticed this when I quested with my partymembers (in the past). When I open a book during the party cinematic, I am able to move and am

not stuck. I am able to move before the cinematic boss is able to act or hit, it will still be in its ‘introduction’ mode.

Exactly 1 month ago a new party cinematic bug was introduced.

The past month nobody was able to play together due to this party bug. The person activating the quest is able to move.

All other party members will be stuck (unable to take any action, just like in dungeon queue waiting), and are teleported back to 1 spot repeatedly.

This questing cinematic bug is well-known by the community.

The party-play ‘questmovie mode locks party members in place’ bug started end June/Begin July,

during the same time a staff member told me the devs had FINISHED fixing the queue bug.

So I believe, unluckily, the code DID work, AND it was applied to the wrong place.

Too long, didn’t read: a fix which should’ve been applied to dungeon queue has been accidentally applied to cause party quest stuck bug.

Related?:

