Useful as history
Beta dates, announcements, and documented system discussions can show what was tested and what the team later addressed.
Home / Servers & Accounts / Beta Changes
Returning from beta? Start with the Irisalis token route, the removed rune system and the revised training reset. These are developer-announced launch changes, not results of a play test by this site.
Unofficial fan-made guide. Official announcements are not hands-on testing, and historical beta evidence is not launch confirmation.

The September 3 developer letter gives specific changes. The table pairs each published change with its practical consequence for someone returning from beta.
| Area | What the official material supports | What to change in your plan |
|---|---|---|
| Irisalis | Collect legendary tokens, craft a personal Legendary Aniipod, then enter the marked story encounter. | Replace beta advice about repeating catch challenges with the token-and-story path. |
| Prismana / Umbral | Nurturing has a flat base Prismana chance; its guarantee remains. Lucky strikes can trigger Prismana Flow. | Do not carry forward beta probability decay. No numerical base rate is given. |
| Training | Rune slots and runes were removed. Awakening below level 60 can be reset with items returned. | Check level and current reset wording before spending training items. |
| Home / RV | Furniture groups can be shared by code; unused furniture can be resold at a discount. | Check resale value rather than assuming a full refund. |
| Egg Heist | More egg types and a high-difficulty Chaos Mode were announced. | Choose the mode deliberately; no reward odds are established here. |
| Task guidance | Journey quest guidance was rebuilt to address unclear requirements and blockers. | Recheck the current objective before following beta instructions. |
A data-wipe beta can help explain why older guides exist, but it is a poor substitute for a current launch source when the player needs a value, route, or reward.
Beta dates, announcements, and documented system discussions can show what was tested and what the team later addressed.
Beta values, drop rates, interface behavior, task order, and rewards should not be copied into a launch guide without a current check.
Recheck the official source after launch patches or new system announcements before treating a changed category as settled.

Keep the source date visible and separate an historical observation from a current instruction.
Terminology, official beta dates, and a clearly attributed historical explanation can remain useful context.
Routes, exact numbers, rewards, task sequence, controls, and interface details need a launch or patch-specific source.
Do not use beta-only rankings, drop claims, or “guaranteed” outcomes as current player advice.
These answers keep historical beta evidence in its proper place.
No. The official material describes the Global Closed Beta as a data-wipe test, and beta content is not a guarantee of launch values or quality.
It announced changes involving Irisalis, Prismana and Umbral, training, Home, Egg Heist, and task or mission guidance.
Use it as historical context only. Recheck current official information before relying on its routes, values, rewards, or interface details.
The links below support the category list and the data-wipe boundary; they are not a substitute for a full launch patch archive.
Related: servers and account boundaries →
The official developer letter is the source for the announced Irisalis, Prismana/Umbral, training, Home, Egg Heist, and guidance categories.
Official developer letterThe official welcome notice states that the Global Closed Beta was a data-wipe test and should not be read as final-quality proof.
Official beta noticeThe beta handbook can provide historical context, but values and routes still require a launch-specific check.
Official beta handbookClaim eligible beta rewards without confusing them with save progress
Separate pre-launch no-gacha statements from later cosmetic draws.