PlayStation "A Distant Shore" not unlocking

MicrowaveHeart

Newcomer
Hi, I'm playing on PS5 on an old save with the new update. I reached Ginger Island ages ago but the trophy is not unlocking. I tried traveling there manually to trigger it, but no luck. First I used the obelisk, then Willy's boat but neither worked to unlock the trophy. Maybe using the obelisk first might have caused an issue? Not sure. But I also tried sleeping and trying again the next day, closing the game and retrying, etc but still no luck. Weirdly the one for having the altar in the mines activated did unlock retroactively for me, so not sure why this one is giving me issues.
 

AerisGainzbrah

Newcomer
Same here!

Playing co-op, neither me or my husband (the host) got this trophy, we also tried the boat rather than teleporting, but got nothing.
 

Kirblitz

Greenhorn
I ran into this issue as well, except instead of "A Distant Shore" achivement, I instead received "Danger in the Deep" achivement when arriving to Ginger Island for thr first time.
Got the video of it happening

 

AerisGainzbrah

Newcomer
I ran into this issue as well, except instead of "A Distant Shore" achivement, I instead received "Danger in the Deep" achivement when arriving to Ginger Island for thr first time.
Got the video of it happening

Ah you know what, I forgot but this happened to me too!
 

Rozalita

Greenhorn
I went to level 120 in the regular mines to toggle the shrine and got the distant shores achievement. Seems like the location to trigger it popping up is swapped with the danger in the deep achievement
 

toeguard

Newcomer
Go to lev 120 of mines and do the challenge then the next day go back to lev 120 and you should get the distant shore achievement! It seems that it's glitched and swapped with the dangerous mines one
 

evergreen oak

Sodbuster
This needs to be addressed in the upcoming console patch. It is unacceptable to leave trophies broken like this. "Just do the other thing" works as a very temporary solution, but it is not a permanent workaround. I really hope that CA and team are aware of this issue and including it in their list of bug fixes
 
Top