WoW: Forever beta datamine roundup: gear, Skyborne and world assets

Wowhead's September 16–17 beta-client reports cover set bonuses, weapon models, Skyborne customizations, maps, creatures and other observed assets; none proves final use.

AI-written and automatically published after automated review ·

Responsible editor: Max · Editorial record: medium risk · automated review · AI assistance: draft

How automated writing and review work

World of Warcraft Classic screenshot showing an outpost in the Plaguelandsroundup briefing
Field image© Blizzard Entertainment. Official World of Warcraft Classic 20th Anniversary press screenshot; used as original-world context, not WoW: Forever footage.
In this article

The briefing

Wowhead’s September 16–17 reports on the WoW: Forever beta client surface observed records across gear, Skyborne customization, world files, creatures, totems, reputations, raid visuals, mounts and loading screens. No named build was recorded in this source cut, and client data can change before beta or launch.

What the reports cover

The set-bonus report records new and updated bonuses and includes an explicit Season of Discovery spillover caveat. That caveat stays attached to the observation. The two weapon-model reports add more item visuals, including models associated with Hyjal. None of these reports supplies a complete item table or final numeric values. The itemization and stat changes article owns the broader itemization explanation.

The male and female Skyborne customization reports, the Skyborne weapon report, and the Skyborne Shaman totem report point to character and class-adjacent client assets. The Forsaken Paladin mount report adds another observed model group. These records are useful checks for the Skyborne classes article, but they do not form a final customization or mount catalogue.

The remaining reports cover world map models, creatures, loading screens, reputation names, raid-tier models, and a CDN branch label. A branch label that refers to a retail branch is an implementation label; it does not mean the product is Retail WoW. The launch-hour and roadmap article retains the separate launch and beta schedule evidence.

What the client data does not establish

These are broad observations from manual Wowhead discovery. The files do not prove that an asset appears in the final game, how a player uses or acquires it, whether a model has every intended variant, or whether the client keeps it through launch. The source cut also does not record a named build, so it cannot support a version-specific claim.

This roundup intentionally leaves Legacy methods to the canonical Legacy article. It also does not reproduce Wowhead tables, galleries, images, numeric item data, or a complete list of every client record. A beta verification pass needs the build number, the in-client result, and a separate provenance record.

End of briefing

Keep the source trail close.