Preserve the choice before converting
Copy the complete save set and document the installed mod/loader state before the first upgraded launch. The reference reports that existing worlds convert rather than being automatically wiped. That is not a substitute for a backup, especially for previously modded worlds.
Choose the experience you want
| Goal | Better starting point | Reason |
|---|---|---|
| Learn the rebuilt progression | Separate fresh world | Missions, early equipment and new unlock timing matter |
| Explore late-game additions now | Continue a backed-up established world | Materials and a trained roster already exist |
| Keep favorites but replay the journey | Retain both worlds; investigate Global Palbox rules | Transfers and server permissions need a live check |
| Test old mods | Disposable copy first | Compatibility is separate from save migration |
Route a fresh start around useful work
Use Lamball for basic work and Wool, Cattiva for hauling and carry support, and Foxparks for Kindling and its active ability. Build food, beds, storage and a reachable bench, then activate travel and follow current missions. Do not assume a launch article’s Anubis suitability or an old Penking/Bushi cross matches the revised breeding roster; use the live local planner for the intended child.
Audit an existing world before the first expedition
- Confirm workers still have reachable food, beds and assignments.
- Inspect current recipes before expanding oil, aquatic building or Jetragon gear; v1.0.3 cuts several costs.
- Recheck equipped passives, active skills and partner requirements.
- Set one Sunreach/World Tree or base-upgrade objective instead of rebuilding every system at once.
- Keep the pre-conversion copy until load, save and restart behavior is proven.