The Pre-Release Celebration Codes update sits between Early Access and the full release code waves. It matters because older reward names can still appear next to current codes, which makes every old launch code look worth counting. That is a bad way to plan a new account. This window is an old reward check, and the current in-game redemption result decides whether any code still belongs in an active list.
The order is the whole point. The newest milestone and release codes come first. After that, test older celebration names such as `Tysm5kCCU!`, `EarlyAccess!`, `ThankYouEA!`, and `Sorry4Bugs!` only if you are clearing the full history. If the code fails, stop counting it as income. If it works, record the exact reward and keep it separate from later release rewards because it came from a different launch-week window.
This update affects beginner advice because free rewards can change the first summon and upgrade path. Gems and Gold can push a player into earlier pulls or upgrades. Trait Shards, Trait Rerolls, Stat Cubes, and Perfect Cubes can be wasted if they go into a unit that falls out of the squad. Since pre-release codes are older and less reliable, they belong after current codes instead of inside guaranteed starter rewards.
This update also keeps old and new rewards apart for players. Current codes sit first, expired codes stay apart, and test-again historical names stay behind the newest rewards. That prevents a player from typing old celebration codes repeatedly while ignoring newer rewards such as 10MilVisits! or 50kCCU!.
The June 8 date is the history marker. It explains why these names appeared before release and why they may fail now. For current play, the live redemption result wins: accepted means the code still helps, rejected means it belongs in expired history.