BriefingsSep 25, 2026 · RealmList Editorial

Rain Over Elwynn: Weather Effects Are Coming to the Forever Beta, Plus the Bugs Blizzard Is Chasing This Week

Kaivax teased increased weather effects for the WoW: Forever beta zones, confirmed the hunter auto-shot bug with a fix incoming, and the community spent September 23 cataloguing a Consecration flicker bug and an argument about spell ranks and caster scaling — all ahead of the September 24 weekly update.

Two Kaivax forum posts landed on September 23, and together they sketch what the next stretch of the WoW: Forever beta is going to feel like: wetter, and with hunters doing normal damage again.

The weather tease

The shorter of the two posts is also the more interesting one. Under the title "Increased Weather Effects", Kaivax linked a short video with a single line: "Coming soon to the Beta." The clip shows a heavy rainstorm rolling through Elwynn Forest — the dense, visibility-reducing kind of weather that long-time players remember from the original game and that Classic largely smoothed away.

What was not given is nearly as telling as what was: no zone list, no build number, no date. PC Gamer framed the tease as part of Forever's "first patch" of new content; other outlets simply reported "coming soon." Forum reactions split along a familiar line — nostalgia for Wetlands rain at one end, a literal "who asked?" at the other.

The design logic, though, connects directly to what the developers have been saying all month. Lead software engineer Nora has repeatedly framed Forever's pitch as "the world is the main character" — and weather is the cheapest, most ambient way to make a zone feel like a place rather than a backdrop. It is also a systems test in disguise: dense rain affects fog stacking, particle performance, audio occlusion in interiors, and readability of nameplates and rares. If you are in the beta when the weather patch lands, the useful feedback is measurements, not vibes — frame rates at different particle settings, whether interiors correctly cut exterior sound, whether fog and rain stack or cancel.

The auto-shot bug, confirmed and scheduled

The second Kaivax post confirmed a bug the community had already been measuring. In the beta, the 0.5-second cast time that precedes a hunter's auto-shot or wand use is not functioning — due to the bug, these auto-shots currently incur a much shorter cast time.

That sounds like a rounding error until you remember what auto-shot timing is in Classic: it is the floor of hunter DPS and the entire rhythm of wand use on cloth casters. A shortened auto-shot window means hunters and wand users are quietly overperforming, which contaminates every balance discussion happening in the beta right now. Kaivax's framing — a dedicated post naming the mechanic and committing to a fix — is the reassuring part: this is on the schedule, not lost in the tracker.

Consecration is flickering, and tanks are losing threat

From the community side, the most consequential new bug report of the week is on the other end of the threat spectrum. Paladin testers found that Consecration's damage ticks drop to 1–2 when a mob walks into the circle from the edge — even when it is the only mob in the circle. The "only the first four enemies take full damage" rule is working as designed; the near-zero ticks are not. Paladin tanks report it costs them most of their area threat, and bug reports are already in.

This one matters more than its ugly-visual reputation suggests: a tank's AoE threat tool that randomly whiffs is exactly the kind of bug that makes dungeon groups feel broken even when the underlying systems are fine — and with the dungeon experience rebalance pushing group content back toward the center of the leveling flow, tanks are the population the beta can least afford to frustrate.

Spell ranks, and the scaling argument underneath

A smaller annoyance turned into the week's best design thread: training a new spell rank does not replace the old rank on your action bar. Pet bars update themselves; player bars keep the old rank until you drag the new one on. The immediate workaround is casting by name in macros, and the obvious requested fix is a toggle that always puts the highest rank on the bar.

What made the thread run to 88 replies is the argument underneath. Forever's new caster scaling makes gear matter more and spell ranks matter less — which some testers read as flattening power spikes in an interesting way, and others (particularly hybrid healers) read as eroding the satisfying rhythm of rank upgrades that defined Classic casting. This is a design-values debate, not a bug report, and it is the kind of feedback Blizzard specifically wants from a paid-beta audience before launch.

What is still pending

Three open items to keep an eye on:

  • The four fixes tagged "fixed in the next Beta build" on September 18 — Waylaid Crates, Starshards not gaining Twilight Focus, Vengeance proccing from periodic crits, and the Coldridge Valley map reveal — were not confirmed in build 69977, and testers have not reported them fixed. The September 24 weekly update is their most likely home.
  • That weekly update itself was announced for September 24 and had not been posted at the time of writing; a larger package is expected to accompany the weather rollout.
  • The memory leak reported by testers has not appeared in any official note.

None of these are alarming on their own — this is what a weekly beta cadence looks like mid-cycle. But the weather patch plus the pending fixes make the next weekly update the most content-heavy one of the beta so far, and the Mac graphics stability saga is still unfinished business that dense weather effects will stress further.

Accurate as of September 25, 2026. The weather tease and the auto-shot confirmation are from Kaivax's September 23 official forum posts (archived by Blue Tracker); the Consecration and spell-rank items are community reports summarized by WowForeverBuilds; the pending-fix analysis follows WoWSoD Pro's September 23 build review. No zone list, build number, or release date for the weather effects had been announced at the time of writing, and the September 24 weekly update had not yet been posted — details may have changed by the time you read this.