Well yes, that does explain things.

Adventureland was an early EA testing world that players were never really meant to see. Yes, it does look just like Sunset Valley except with a population of 2 or something like that. It's not harmful to play as a separate world, from all accounts, but again it was not meant to be there. It becomes revealed on new/fresh Patch 1.69 Origin installs that include WA; those of us who had upgraded our games from 1.67 to 1.69 at the time never saw it. Because it became available as an installed and viable homeworld to play, Traveler would include it among the others as possible destinations. Issues have been reported by players who try to have both Sunset Valley and Adventureland as Traveler connected worlds in the same ongoing game, probably because they both worlds would have the same hidden ID number and those are meant to be unique.

You can hide worlds you don't want to see on the Traveler menus by one of the mod's options.

For whatever it's worth, those of us on Steam installs don't get Adventureland but instead we get two very strange and incomplete worlds that everyone agrees we weren't meant to see either. One is a weird what must have been very early edition of Uni World and the other is a minimalist world that is supposed to have IP features, but there is no ocean and an unusable diving lot had somehow been placed in the middle of a vacant dirt lot. Those were fun to play around with for a short time each just to see what EA was doing, but I've long since hidden them from my Traveler menus as well. As I recall, the two worlds' names actually had the word "testing" in them someplace, or the equivalent.

igazor wrote: ↑

December 15th, 2020, 9:36 am

For whatever it's worth, those of us on Steam installs don't get Adventureland but instead we get two very strange and incomplete worlds that everyone agrees we weren't meant to see either. One is a weird what must have been very early edition of Uni World and the other is a minimalist world that is supposed to have IP features, but there is no ocean and an unusable diving lot had somehow been placed in the middle of a vacant dirt lot. Those were fun to play around with for a short time each just to see what EA was doing, but I've long since hidden them from my Traveler menus as well. As I recall, the two worlds' names actually had the word "testing" in them someplace, or the equivalent.

I'm so glad I saw this. I had NO idea what these "test" worlds were supposed to be, but I hated even SEEING them (and didn't know Traveler could hide worlds). I was always so scared I'd accidentally click on the wrong world and be sent into some AU abyss.

Hi everyone!

I've actually been having this problem consistently since changing home worlds in my save file, and, unfortunately, I am not accidently choosing the wrong world when sending my sims back (I've checked and re-done it multiple times).

The problem: I begun a family in a custom world. The family has since grown to the fifth generation with over 60 Sims connected in the family tree (this is due to one sim in generation 4 who had triplets twice AND twins TWICE. WHYYYY). I wouldn't be surprised if the large genealogy is the main fault for all of my issues.

• I moved three of the Sims from that original family using traveler to a different custom world, purchased a vacation home for them, moved them in, and changed their hometown to the new world using traveler.
• I've attempted to travel back to the original homeworld, both to visit and to play the households I've left, but each time I travel back, the world has reset completely. I've tried traveling back with a sim, with all three sims, and with no sims, and each time I load the original homeworld from five generations ago.

Any ideas on how to troubleshoot this? I've tried sending them back to visit immediately after the change homeworld was complete, and that still didn't work. I've given them some (sim) days in their new homeworld before traveling them back, and the same thing. They've even had their family visit and "return home" and I still had them arrive at a reset world.

The only thing I can think of is to revert back to the save in the OG homeworld and go through this whole process again. However, I don't have much confidence that it will work, since that would be my third time doing it.

Thanks for all of your help! I'm so grateful these forums exist

aanthony2 - Some custom worlds will never work properly with Traveler due to the way they were ID'ed at the beginning of their design stage. There is no fix for that.

To confirm though, I suggest setting your ongoing game aside temporarily. Start a new game in World A and make some changes to it that will look obvious (like add a bowling alley or something and delete some other lot). Travel a sim to World B and do the purchase home, change hometown thing, save as, quit, reload. Can your sim successfully travel back to World A now or does a fresh one without your obvious changes load?