Do seeds reproduce the same ending?
Only when the rules version and the sequence of choices also match. A seed link alone shares the starting setup, not a player’s decisions.
Project Moonlife / GAMEPLAY GUIDE
Project Moonlife Seeds: How to Share and Replay
A Project Moonlife seed reproduces a starting setup under a specific rules version. It does not include another player’s choices. To replay the whole journey, export the life record, which stores the seed and commands.
What does a seed control?
The seeded random generator determines the district, home, family and initial stat variation. The same seed and rules version recreate those values. Language and resident name do not change the random sequence. After the beginning, the event sequence also depends on decisions and commands, so a seed-only link is a shared starting point, not a finished playthrough.
Why the version is part of the link
The simulator keeps published rules editions separate. Version 1 is the original rules set, version 2 adds City routes and branches, and version 3 preserves v2 event logic while adding an optional legacy starting bonus. A link with v=2 keeps v2 behavior even when newer rules exist. New lives use v3 outside Japanese routes; an unversioned legacy seed link continues to use v1 for compatibility.
How to share a seed
Use the in-game share action or copy the seed from the resident dossier. The link carries a seed, rules version and, for v3, whether a legacy talent was used. It does not expose the resident name, choices or local save. A daily City link uses the UTC date as its seed so everyone opening it on that date shares the same starting setup.
How to move a complete life
Choose Export in the player to download a JSON record. It contains the initial inputs and the sequence of advances and choices; importing rebuilds the journey instead of trusting edited attributes. Import it in the archive on another browser or device. Local lives stay in the browser, so export a backup before clearing storage or changing devices.
Compare seeds under the same rules
A fair comparison keeps the rules version, talent setting, and decision policy constant. Record the seed, birthplace, family, starting attributes, and the choices you made; otherwise a different outcome cannot be attributed to the starting seed alone. The game uses a seed to reproduce initial conditions, while later choices still shape the run. A seed that produced a rare event for one player is not a guaranteed route for another player who makes different decisions.
Use a repeatable seed note
When you find a start worth revisiting, save the complete versioned link and note why it was useful: a preferred birthplace, a starting attribute profile, or a particular family setup. In v3, the optional legacy talent is part of the run settings and is included in the link; keep it the same when comparing starts. Existing v1 and v2 links continue to use their original rules. This makes seed sharing useful for experiments without promising identical choices or endings.
A simple seed-testing checklist
Use the same rules version and talent setting, then write down the seed before the first decision. Record the starting district, family, and attributes so you can tell whether two runs really began alike. If you are testing a route, make the same choices up to the point where you want to compare outcomes. A changed choice is a new path, not proof that the seed stopped working. Keep notes with the shared link so another player can distinguish the initial setup from your later decisions.
FAQ
Can I share a community-recommended seed?
There is no built-in community ranking or verified seed list. You can share any seed you have tested, but label its rules version and describe the choices if you want others to reproduce the ending.
Does a v2 seed change when v3 is released?
No. The version parameter keeps v2 links on v2 rules. Versioned seeds remain reproducible across future releases.