Read updates by what they can change
A notice is not a reason to reset every tracker. First classify its scope, then inspect only the connected player route.
Access or account
New invite, test start, platform, or closure language changes who can play and which client is safe.
Release status →Download route →Event or reward
Dates, milestones, prize tasks, and codes change the daily loop—not your collection data.
Event status →Code check →System rule
Cooking, fishing, gifting, shops, or decorating language tells you which tool needs a small current-build check.
Choose the affected tool →Build-sensitive detail
Costs, windows, reactions, and stock should stay marked as recheck items until the playable build confirms them.
Run one recheck →- Copy the dated notice and its scope.
- Name one affected page.
- Verify one value before changing a saved plan.
What the September Notices Changed
These historical test dates explain when invited players could prepare a client, enter the test, or receive an invitation. Public launch is now announced for December 4, 2026; use the newer campaign for launch preparation.
- Access checks and pre-download openedOfficial notice ↗
Selected accounts could prepare the assigned client. This was not a public installer.
- Final Beta beganOfficial notice ↗
Invited players could enter the data-wipe test. The end time remained unannounced.
- All invitations were sentOfficial notice ↗
Check Access is the account result. If eligible without email, follow the notice's folder and support steps.
If an update only changes access, leave saved fish, recipe, gift, and furniture values as reference data until the current build confirms them. Open the current access route for the account and device steps.
Update Index
December 4 Launch Date and PTPL1204 Reward Code
The official launch campaign now announces December 4, 2026 (UTC+8), replacing the seasonal window. It links Epic Games Store, App Store, and Google Play. PTPL1204 grants Curio Sea Whistle ×10 after launch and is valid until January 3, 2027 at 10:00 (UTC+8). The current prize-draw window ends November 30 at 23:59 (UTC+8). This is a launch and campaign update, not gameplay balance patch notes.
October Archive: Earlier Winter 2026 Window
At the October 1 check, the official homepage showed a Winter 2026 window. The newer launch announcement replaces that seasonal window with December 4, 2026. The September prize-draw deadline and Final Beta invitation completion remain historical context.
All Final Beta Invitations Sent
The official notice says all Final Beta invitations were sent by September 24 at 19:00 (UTC+8). Check Access gives the account result. If it shows eligibility but no email arrived, check spam and subscription folders, then contact the support address in the official notice.
Final Beta Began September 20
The invited Final Beta began September 20 at 09:00 (UTC+8). It is a data-wipe test with no in-game purchases on PC Windows, iOS, and Android; the end time will be announced separately. This start date is not the public launch date.
Final Beta Invites and Pre-Download Open
The official Final Beta guide opened access checks and pre-download for invited accounts from September 19, 2026 at 10:00 (UTC+8), ahead of the September 20 test start. This was selected-player preparation, not a public launch installer.
Final Beta Download and Installation Guide
The official installation guidance points eligible players to Check Access or their invitation email. Verify the assigned account and platform before installing; the selected Final Beta client is separate from a public launch installer.
Stardrift Test Ended May 25, 2026
Official notice states that the Petit Planet: Stardrift Test would end on May 25, 2026 at 10:00 (UTC+8), with test data wiped by default after conclusion.
All Stardrift Test Access Sent
Official notice stated that all Stardrift Test invitations had been sent by April 26, 2026 at 10:00 (UTC+8), with players directed to the official access page or invitation email.
Stardrift Test Began April 21, 2026
Official post says the Stardrift Test went live on April 21, 2026 at 09:00 (UTC+8), with access times shown on the official access page or invitation email.
Stardrift Test Fair Play Statement Published
Official fair-play statement named test access limits, account sharing restrictions, and prohibited tools or altered environments for the Stardrift Test.
Petit Planet Content Guidelines Republished
Official content guidelines described basic rules for in-game customization and shared creations during the Petit Planet test period.
Stardrift Test Guide Published
Official guide described the test as limited-access, data-wipe, no in-game purchases, and available on PC Windows, iOS, and Android for selected players.
Stardrift Test Sign-Ups Opened
Official sign-up post announced Stardrift Test sign-ups, supported languages, PC/iOS/Android platform scope, and age/device binding notes.
Coziness Test Shutdown Notice Published
Official shutdown notice set the Coziness Test end time as December 1, 2025 at 10:00 (UTC+8) and stated that test data would be deleted after closure.
Coziness Test Server Went Live
Official notice announced that the Coziness Test server opened for first-batch players on November 7, 2025 at 09:00 (UTC+8), with later entry times shown through eligibility routes.
Coziness Test Guide Published
Official Coziness Test guide described Petit Planet's first small-scale closed beta with a data wipe, PC Windows/iOS platform scope, language support, and device recommendations.
Coziness Test Invites Started
Official invite notice described eligibility checks, pre-download, email notifications, and platform details for selected Coziness Test players.
Coziness Test Fair Play Statement Published
Official fair-play statement described account, age, sharing, and tool restrictions for the Coziness Test.
Cozy Cosmos Trailer Published
Official trailer post introduced Petit Planet as a cosmic life sim about building, planting, harvesting, befriending fuzzy neighbors, and exploring the Starsea.
How To Read Updates
Check the status label
The December 4 launch announcement replaces the seasonal window. September invitation dates, Coziness, and Stardrift remain test history; they do not establish today's access or final gameplay values.
Follow source links
Official source links are shown so players can verify dates, platform scope, and data-wipe notes.
Use related pages
Jump to Events, Release Date, Download, or Stardrift Test when a notice changes a practical player question.
Update Action Planner
Use each update by what it changes. Access notices, system hints, and reward notices should send you to different follow-up pages.
If an update changes sign-ups, test access, platform scope, or closure timing, check Release Date, Download, and Platforms next.
Open releaseIf a notice mentions fishing, cooking, decorating, neighbors, or shops, recheck the matching database page before planning around old values.
Open wikiIf an update mentions campaign rewards, event tasks, or gift codes, check Events and Codes before changing your daily route.
Open eventsWhat Updates Can Confirm
Official notices can confirm test dates, platform scope, data wipe, sign-ups, access rollout, and closure.
Check release pagePosts can reveal systems like planting, neighbors, fishing, cooking, or decorating without locking every value.
Open wikiGift preferences, fish times, recipe ingredients, shop refreshes, and reset behavior still need current-build checks.
Open checklistUpdate Coverage
This index keeps official notices useful without over-reading them. A post can confirm test access or timing while still leaving database values pending.
Reveal, sign-up, access rollout, server live, ending, and shutdown notices are strongest for release and playable-status questions.
19 tracked noticesPosts and test pages can reveal systems such as neighbors, fishing, cooking, decorating, and exploration without confirming every table value.
19 tracked noticesFish locations, recipe ingredients, favorite gifts, furniture unlocks, reset rules, and shop stock need in-game or current-build checks.
19 tracked noticesOfficial Timeline At A Glance
Post-Update Tool Audit
When a new build or official notice appears, translate it into a short audit instead of assuming every old tracker entry is wrong. Start with rules that affect access or spending, then revisit only the databases touched by the update.
Recheck release status, download route, platforms, test scope, data wipe, and account eligibility before using an old client.
Open download statusRecheck code redemption, event tasks, gift limits, shop refreshes, and reset behavior before carrying yesterday's checklist forward.
Open daily routeReview craft costs, recipe ingredients, furniture unlocks, shop stock, and material uses before spending rare resources.
Open crafting plannerRecheck fish and bug windows, shore distribution, neighbor gifts, plant behavior, and owned/caught marks only where the new build changes them.
Choose affected toolFAQ
Are these launch patch notes?
This is an official announcement timeline. The latest check covers the December 4 launch and pre-launch rewards. It does not provide a public-build gameplay balance changelog.
Why track test updates?
They explain which systems appeared in public official posts and help players avoid mixing closed-test dates with launch information.
What changed in the latest official campaign?
The official homepage now names December 4, 2026 (UTC+8), replacing the earlier seasonal window. It publishes PTPL1204 for after-launch redemption, a January 3, 2027 code deadline, and a separate November 30 prize-draw deadline.
What changed between September 19 and September 24?
September 19 opened Check Access and pre-download for invited accounts; September 20 began the Final Beta; September 24 completed the invitation rollout. The test end time was still to be announced separately.
Do patch notes confirm database values?
No. Patch notes can confirm official status or test context, while fish, recipe, gift, and furniture values still need current-build checks.
Should I treat closed-test changes as launch rules?
No. Coziness and Stardrift notes are test context until a public build or official launch notice confirms the same rule.
Where should I verify a new update?
Open the official source link first, then check whether the notice affects release, download, platforms, events, or database pages.