[TERA PC & Console] En Masse is closing, but TERA lives on! We will continue to support TERA PC (NA) and TERA Console until service is transferred. Stay tuned for more information.
[TERA Console] The Grotto of Lost Souls update (v85) is now live! Read the patch notes here: https://bit.ly/TERACon_v85
[TERA PC] The 64-bit update (v97) is now live. Check out all the changes delivered on August 11 here: https://bit.ly/tera64_patchnotes
[TERA PC & CONSOLE] Summerfest Part 2: The Beach Bash is on from August 11 until September 1! Participate in event activities to earn tokens redeemable for costumes, consumables, mounts, and more! Details: https://bit.ly/tera_sf20
Nightmare Lachelith will not reset after a player drops party.
Character info:
Name: Amoretti
Level: 65
Race: Elin
Class: Priest
Party member info:
Names: Kyattsu (Mystic), Kudisai (Lancer), Ponzun (Ninja), Lynwannabe (Reaper)
*All party members are level 65 & of the Elin variety*
This was not an Instance Matched group, so all members are from the Mount Tyrannas Server.
Date & Time: 11/04/16; somewhere between 8:30pm - 9:30pm EST.
What happened, you say? WELL,
The players listed above and myself were running Ruinous Manor (Hard). It was the lancer's first time running hard mode, so the run was a little hectic, but still a very clearable run with some practice. The time had come, we'd reached last boss, Nightmare Lachelith. We explained a few mechanics, buffed, and away we went. We were somewhere around 80% and Lynwannabe (Reaper) died and decided they were going to leave the party. Shortly after Lynwannabe left our party, we forced a wipe so we could find a new DPS. Before we found our replacement DPS, we went back into the dungeon and were greeted with this:
*The image above is a screenshot of Nightmare Lachelith attacking the floor continuously where Lynwannabe died before leaving our party and subsequently logging out*
Even though every single one of us remaining in the party died, Nightmare Lachelith would not reset, no matter what we tried. We tried to all enter the dungeon and die again, didn't work. We tried making sure that every single one of us was outside the dungeon, didn't work. We even tried asking someone from guild to hop on an alt to see if having five people in the party would reset her. It still didn't work... She just persisted to attack the floor and the gate did not open.
We are not 100% sure as to what may have caused the bug, but we think it may have been caused by a member of the party leaving the party while we were still fighting Nightmare Lachelith. If that assumption is correct, you should be able to recreate the bug by doing the following:
How to recreate this bug:
- Create a party of 5 players
- Enter Ruinous Manor (Hard) and fight Nightmare Lachelith
- Once combat has started, have one player die.
- Have the dead player resurrect outside the dungeon, leave party, and then log out.
- Once they have logged out, have the rest of your party die to the boss and resurrect outside
- Upon entering the dungeon again, Nightmare Lachelith should not have reset and should be attacking nothing.
Normally, I probably would have just overlooked this and not bothered reporting it, like many other bugs I've come across in TERA. I would have just dropped party and moved onto my next run, but with Instance Reset Scrolls being disabled for the time being, it's kind of a big deal.
Name: Amoretti
Level: 65
Race: Elin
Class: Priest
Party member info:
Names: Kyattsu (Mystic), Kudisai (Lancer), Ponzun (Ninja), Lynwannabe (Reaper)
*All party members are level 65 & of the Elin variety*
This was not an Instance Matched group, so all members are from the Mount Tyrannas Server.
Date & Time: 11/04/16; somewhere between 8:30pm - 9:30pm EST.
What happened, you say? WELL,
The players listed above and myself were running Ruinous Manor (Hard). It was the lancer's first time running hard mode, so the run was a little hectic, but still a very clearable run with some practice. The time had come, we'd reached last boss, Nightmare Lachelith. We explained a few mechanics, buffed, and away we went. We were somewhere around 80% and Lynwannabe (Reaper) died and decided they were going to leave the party. Shortly after Lynwannabe left our party, we forced a wipe so we could find a new DPS. Before we found our replacement DPS, we went back into the dungeon and were greeted with this:
*The image above is a screenshot of Nightmare Lachelith attacking the floor continuously where Lynwannabe died before leaving our party and subsequently logging out*
Even though every single one of us remaining in the party died, Nightmare Lachelith would not reset, no matter what we tried. We tried to all enter the dungeon and die again, didn't work. We tried making sure that every single one of us was outside the dungeon, didn't work. We even tried asking someone from guild to hop on an alt to see if having five people in the party would reset her. It still didn't work... She just persisted to attack the floor and the gate did not open.
We are not 100% sure as to what may have caused the bug, but we think it may have been caused by a member of the party leaving the party while we were still fighting Nightmare Lachelith. If that assumption is correct, you should be able to recreate the bug by doing the following:
How to recreate this bug:
- Create a party of 5 players
- Enter Ruinous Manor (Hard) and fight Nightmare Lachelith
- Once combat has started, have one player die.
- Have the dead player resurrect outside the dungeon, leave party, and then log out.
- Once they have logged out, have the rest of your party die to the boss and resurrect outside
- Upon entering the dungeon again, Nightmare Lachelith should not have reset and should be attacking nothing.
Normally, I probably would have just overlooked this and not bothered reporting it, like many other bugs I've come across in TERA. I would have just dropped party and moved onto my next run, but with Instance Reset Scrolls being disabled for the time being, it's kind of a big deal.
0
Comments
Edit: I asked the other group and they said no one dropped from their party when it happened so that doesn't seem to be the cause.