marking recall positions in desert.

Caylin · Post by **Caylin** » Sun May 05, 2019 2:13 pm

I am unsure if its a bug or on purpose but whenever I mark a port place on my stone of recall that is anywhere between oasis and great chasm I always end up on the same map (the one right before chasm I think). Hence marking anywhere in that whole area is nonfunctional for me. i have tried with different stones, toons and accounts and it happens globally.

Post by **driller** » Sun May 05, 2019 2:57 pm

Do you have an empty slot available on your rune when you try to save it?

Caylin wrote: ↑Sun May 05, 2019 2:13 pm I am unsure if its a bug or on purpose but whenever I mark a port place on my stone of recall that is anywhere between oasis and great chasm I always end up on the same map (the one right before chasm I think). Hence marking anywhere in that whole area is nonfunctional for me. i have tried with different stones, toons and accounts and it happens globally.

Caylin · Post by **Caylin** » Mon May 06, 2019 1:30 am

Yes. It also saves it just fine and shows the graphic but i end up in arid plains everytime i use that location no matter where i actually set it. Everywhere else works fine so i figured it was something that happened to everybody.

Caylin · Post by **Caylin** » Mon May 06, 2019 1:50 am

Retested on both accounts:

I use waypoint to go to great chasm, walk away a bit and mark the location. Then i try and port to my newly marked spot while standing next to it. I end up in Arid plains. The name on the stone is also Arid plains and there was no difference between two different accounts.
I had several available slots on my stone.

Maybe someone else can confirm it also happens to then? It happening on both my accounts strongly suggests it isnt a problem specific to me though.

Mask-inc · Post by **Mask-inc** » Mon May 06, 2019 4:26 am

Tested it, it's doing the same thing.
Save the rune anywhere in the waste, always end up in the exact same location when you port back.

Mask

Caylin · Post by **Caylin** » Fri May 10, 2019 2:52 pm

Bump.

Any news on this issue?

Post by **driller** » Fri May 10, 2019 3:44 pm

I do not see anything wrong. I will have to do some testing.

Caylin · Post by **Caylin** » Fri May 10, 2019 5:51 pm

You mean you cannot recreate the bug as a player even though we have confirmed 3 accounts it happens to?

Post by **driller** » Fri May 10, 2019 6:18 pm

I mean when I look at the code, it should just work. There is no reason for it not to. So I will have to debug it.

Caylin wrote: ↑Fri May 10, 2019 5:51 pm You mean you cannot recreate the bug as a player even though we have confirmed 3 accounts it happens to?

Post by **driller** » Sat May 11, 2019 6:47 am

This should be fixed now.

ghost11x · Post by **ghost11x** » Sun May 12, 2019 1:32 pm

Who is The Man?

Post by **driller** » Sun May 12, 2019 1:46 pm

The same guy who created the bug I assume...

ghost11x wrote: ↑Sun May 12, 2019 1:32 pm Who is The Man?

Caylin · Post by **Caylin** » Sun May 12, 2019 1:58 pm

Nice fix. It works for me now.

blackstonekeep.com

marking recall positions in desert.

marking recall positions in desert.

Re: marking recall positions in desert.

Re: marking recall positions in desert.

Re: marking recall positions in desert.

Re: marking recall positions in desert.

Re: marking recall positions in desert.

Re: marking recall positions in desert.

Re: marking recall positions in desert.

Re: marking recall positions in desert.

Re: marking recall positions in desert.

Re: marking recall positions in desert.

Re: marking recall positions in desert.

Re: marking recall positions in desert.