The Forever beta closes in thirteen days, on October 21, unless the roadmap graphic reading October 22 is right instead. That split is still open, and it is not the only one.
The nine open items
| # | Question | What closes it |
|---|---|---|
| 1 | Onyxia at launch vs December 9 | Either date arriving with the content |
| 2 | Beta close 21 vs 22 | An in-client message or official confirmation |
| 3 | Server Slam date | Any dated announcement |
| 4 | Level-30 activation date | Any dated announcement |
| 5 | Auto-shot and wand bug | Client notes or a tester report |
| 6 | Spearing Strike | A spell listing or blue post |
| 7 | Heroic storefront price | A price on a page |
| 8 | Forsaken mount model | A model in files or a screenshot |
| 9 | 2027 fine print | Any official detail past December |
Items 3 and 4 have been open since the beta opened. Item 5 has survived four client builds and one round of realm fixes. Item 1 has two first-party sources in direct conflict.
What thirteen days means for each
Dated items (3, 4) either get dates or they do not happen before launch, and silence is itself an answer worth publishing. Content items (1, 6, 8) resolve the moment the content ships or the launch notes land. The price item (7) resolves at the storefront. The beta-close split (2) resolves the day the realms go dark.
None of these needs investigation. All of them need waiting, which is why the list exists: so that when each resolves, the resolution is recorded against the open question rather than published as if it were new.
The PAX variable
Tonight's dungeon segment could close or open items depending on what it shows. A new dungeon with a date attached would add a tenth row. Mechanics shown without dates would move nothing. Hands-on reports from the booth could answer the bug item first-hand.
Tomorrow's coverage starts from this list.
SOURCES: our own verification hit list, maintained since September 14 2026, with each item's sources cited in its rounds. Related: the hit list, the PAX preview, and the launch runbook context.