A manual change log of the official surfaces this guide opened, the scope of each check, and the editorial conclusion that followed. It records no-change sweeps as well as announcements so a stale date is never made to look new.
Primary sources last reviewed: 2026-08-31
Original research record
Manual source-sweep history
Every row answers three separate questions: which surface was checked, whether the source materially changed, and what conclusion the evidence supports. Repeated no-change checks remain visible instead of being repackaged as news.
Regional routing clarified
English product site, direct notice, and publisher-linked route
The direct notice still confirms pre-registration without an exact launch date. The publisher-linked route is region-sensitive and may fall back to a general store page in unsupported regions, so reader guidance now requires destination verification.
English product site and direct pre-registration notice
The August 29 notice officially opens pre-registration and a registration-count reward campaign. The product page now carries a pre-register call to action, but neither source publishes an exact public launch date.
The news index still ends with the two July 18 notices. No exact launch date, public store page, preregistration route, or additional test notice is listed.
Applications and the selected-tester window are closed. The published test ran during July 22 at 11:00 PM – July 29 at 10:59 PM PDT; no extension or new test is listed on the current official English news feed.
Bandai Namco's August 29 notice opens pre-registration and a reward campaign tied to total registrations. Regional availability may vary, and it does not name the exact public launch day.
As of the 2026-08-31 source sweep, pre-registration is open, but no exact public launch date, dated store availability, or new test is published on the official English site or news feed.
The 2026-08-31 source sweep found no verified public redeem code or redemption path. Pre-registration campaign rewards are not redeem codes. Pull-rate, pity, or final launch-banner claims remain unverified without an official notice or reproducible permitted client evidence.
A link alone is not analysis. Each update passes four checks before it changes a guide, alert, or planning assumption.
1. Capture the exact claim
Record the publisher wording, publication date, region, platform, and whether the material describes a test build or public service.
2. Resolve scope and time
Normalize time zones and separate application deadlines, test windows, store dates, and launch dates so one milestone is not mistaken for another.
3. Check conflicts
Compare the claim with newer official news and support pages. A newer scoped source wins; reposts and search snippets do not.
4. Publish the decision boundary
State what a reader can safely do now, what remains TBA, and the precise evidence required before the answer changes.
Current reader decisions
Can I play now?
No public service is available. The selected-tester app expired after the July window and is not a download route.
What can I plan?
A budget and deadline using editable assumptions. Official pull rates, pity, banners, and rarities are not yet safe defaults.
What changes next?
A dated publisher launch notice, a store availability date, another test notice, or public-service support documentation.
Primary-source directory
These links support the ledger above. Descriptions identify the question each source can answer so readers do not have to infer authority from a URL or repost.
Search snippets, copied articles, anonymous posts, fan wikis, untraceable screenshots, and simulator output are not primary evidence. They may identify a question worth checking, but the claim remains pending until its original source is verified.
Verification standards and correction handling are documented in the Editorial Policy.