Announced launch change
Irisalis encounters were redesigned
Exploration and story can provide legendary tokens used to craft a Legendary Aniipod, followed by a one-time encounter.
Returning players / Official change log
What is changing for launch?
The September 3 developer letter announces these changes for the September 16 PC and console launch. As of September 12, the release is still upcoming; this summary describes announced systems, not live-client testing.
Announced launch change
Prismana uses a clearer trigger loop
Prismana has a flat base trigger through nurturing. Lucky Strikes provide items, increase area Prismatic Energy and improve the chance of a Prismana Flow.
Announced launch change
Wild Surges can include Umbral Aniimo
Umbral Aniimo can appear in Wild Surges and can also be encountered in the open world; the official letter says they have Perfect Potential.
Announced launch change
Offering and ecosystem rules changed
Offering quality no longer affects Wild Surge quality. Ecosystem nurturing provides fixed Prismatic Energy, and season-exclusive Prismana spawn rules were clarified.
Announced launch change
Training was simplified
Random rune slots and the rune system were removed. Legendary Star Dust was increased, a sub-Lv60 Capability Awakening reset was allowed, and caps unlock gradually.
Announced launch change
Home and Journey received broad improvements
Home gained a larger multi-area map, house building, furniture sharing codes, interactive furniture, better Home Aniimo behaviour, Home events and more. Journey guidance was rebuilt.
Announced launch change
Controls and activities were updated
The launch letter also calls out improved mobile and controller controls, multi-language voice-over, Sparkling Cube Perfect Potential guarantees, Egg Heist improvements, higher 9/9 and 10/10 wild spawn rates, Pathfinder Challenge rematches and Holo-Battle AI teammates.
Still separate from this guide
Exact drop rates, spawn coordinates, evolution conditions, balance rankings and platform-specific differences are not filled in from community memory. They belong in a later Atlas update when an authoritative source makes them identifiable.