My wife and I have been playing Terraria for a couple of years now, first on the PS4 then on Switch then back to the PS4 recently. We play together using worlds generated by her with me joining her hosted session. We each have well over 50 hours in both versions (PS4 multiple times.)
The issue we've had since the beginning is that, no matter what we do, all of the map I've revealed is reset every time I join the world. It's like I'm joining a world that's been thoroughly explored for the first time.
Is there any way to force the revealed map to save before I exit (or when I exit?) I've tried some tricks such as joining the world with another character and exploring a bit before saving and exiting and returning to my main character. We've always made sure to have me save and exit before her (so I'm not pre-maturely kicked out without saving.)
Any help would be appreciated. The game would be a lot more enjoyable if I could see what I've already explored!
Edit: Also, I'd love to know if anyone out there is playing on PS4 and/or Switch, joining multiplayer games and NOT experiencing this issue. If so it gives me hope that it'll be fixed (or there's a method to avoiding the issue!)
The issue we've had since the beginning is that, no matter what we do, all of the map I've revealed is reset every time I join the world. It's like I'm joining a world that's been thoroughly explored for the first time.
Is there any way to force the revealed map to save before I exit (or when I exit?) I've tried some tricks such as joining the world with another character and exploring a bit before saving and exiting and returning to my main character. We've always made sure to have me save and exit before her (so I'm not pre-maturely kicked out without saving.)
Any help would be appreciated. The game would be a lot more enjoyable if I could see what I've already explored!
Edit: Also, I'd love to know if anyone out there is playing on PS4 and/or Switch, joining multiplayer games and NOT experiencing this issue. If so it gives me hope that it'll be fixed (or there's a method to avoiding the issue!)