Group member got a different mission instance than the rest of us

Discussion in 'Bug Reports' started by Senthiele, Feb 4, 2024.

  1. Senthiele New Member

    Category: Quest
    Date/Time: Sun Feb 04 21:14:08 2024

    Character: Level 125 Wizard (Main)
    Zone: Pal'Lomen 8445
    Location: 859.10, -732.65, 6.01, 387.78

    Description: Very interesting bug experienced otnight in the Pal'Lomen mission. Our group of 6 was working through this as we do multiple times a day. One person was on a Persona, which he had swapped to after the Hero's Forge mission. When we all zoned in, 5 of us were in Pal'Lomen 8445, but one player was assigned to Pal'Lomen 8446, which we observed on the guild roster when he landed in his very own instance of the mission. We attempted to drop and re-add him to the task multiple times. We had him log out and back in, but each time he was re-added, he would zone and land in 8446, while the rest of us were in 8445. When the mission was complete, we opened the chest, and all 6 of us got the lockout. The player in question was in POK or GL, and it told him that he had pending rewards from a completed task. He attempted to zone in to us one last time, but still landed in 8446. He did recieve his exp and coin when he landed, but this was a strange enough one that I wanted to bug report it. I do not know if we could replicate it at this point, or if we would even want to.
  2. Moege Augur

    Were group leader zoning when requesting task ? that bugs raids out in the same way,
  3. Senthiele New Member

    Negative, but interesting.