Closed Thread
Results 1 to 4 of 4

  Click here to go to the first Rift Team post in this thread.   Thread: [FIXED] Returned to wrong location after Celestial Adventure

  1. #1
    Rift Chaser Goddessdavida's Avatar
    Join Date
    May 2014
    Posts
    326

    Default [FIXED] Returned to wrong location after Celestial Adventure

    During the course of Celestial Adventure in Gedlo Badlands, the "horns blew" (impending zone event) while the group was closing a rift. At the conclusion of that rift, we were all teleported to the fire rifts IA (the revamped ones). I stayed on two more IAs, the starting one and we closed one major rift.

    I left the party and (as expected) was kicked from the map. But I was teleported back to Gedlo Badlands, where the rift had been, and not to Tempest Bay, where I had started from. I was lucky, I didn't teleport into any mobs, and the Tempest Insignia got me "back home".

    I have done a lot of IAs, and I know that behavior is not correct. I suspect that the forced start is not getting passed the prior location data and uses the current location instead.
    Last edited by Yaviey; 09-27-2017 at 10:57 AM. Reason: updated title

  2. #2
    Rift Chaser Goddessdavida's Avatar
    Join Date
    May 2014
    Posts
    326

    Default

    This is still happening. It is not just from changes forced by zone events, anytime, even when a run in Gedlo ends and a new one starts in either of the splinters, the previous location is changed to be Gedlo instead of wherever you entered Instant Adventures from.

    As they say "it ain't right".

  3.   Click here to go to the next Rift Team post in this thread.   #3
    Community Manager Yaviey's Avatar
    Join Date
    Jul 2017
    Posts
    1,015

    Default

    Very strange! We will take a look and find out what's up.

  4.   This is the last Rift Team post in this thread.   #4
    Community Manager Yaviey's Avatar
    Join Date
    Jul 2017
    Posts
    1,015

    Exclamation

    Update 9/27: this was fixed during this week's game update. More info can be found in the patch notes here. Since this issue is now resolved, I'm closing this thread. Thanks for helping us get this fixed!

Closed Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts