Checklist de test de la bêta WoW Forever

These are dated checks from Blizzard announcements, not confirmation of current gameplay. On October 18, 2026 at 07:49:41.886 UTC, Blizzard's wowclassicbeta version feed listed build 1.60.1.70450. The feed does not show the current build installed on a player's client or running on a realm. Record the build you test and what you actually observe.Source: Blizzard's WoW Classic Beta version feed, retrieved 2026-10-18T07:49:41.886Z.

Checks Announced October 15 EDT

Blizzard's Beta development update, post 6, announced these additional test candidates:

Wetlands respawns: Rates in several areas, including Dragonmaw Orcs, Gnolls, and Incendicite Ore, were increased and evened out. Check these separately from the five-zone list in the October 1 notes. The post announces a change; it does not show what your client or a realm currently does.

Cooldown Manager: Spells of different ranks should appear as one entry. Check several ranks on the build you have installed and record the result. The October 8 notes had already announced support for all classes, racial abilities, and trinkets; post 6 adds rank grouping.Source: Blizzard Beta Development Notes, October 8 post 5, Cooldown Manager; created and edited 2026-10-08T21:32:38.124Z, retrieved in the retained topic response at 2026-10-18T07:49:41.413Z.

The post was published October 15 EDT and edited October 16. Treat both as announced changes until you test them in your installed client.Source: Blizzard's Beta Development Notes, post 6; the post's exact timestamps and retrieval time are recorded below.

October 21 Stress Test Announcement

Blizzard announced a temporary Stress Test on October 21. Its announced start times are 19:00 CEST in the EU, 2:00 p.m. PDT in the Americas and Oceania, 5:00 a.m. in Taipei on October 22, and 6:00 a.m. in Korea on October 22. The forum announcement says any player with a WoW account is eligible and no active subscription is needed. The linked news article also says no Game Time, invitation, or Beta access is required.

Blizzard says the regular Beta will go offline shortly before the event and is expected to return shortly after; its forum post says the Beta will reopen after the Stress Test. The news article says the event window may end earlier or later as needed. It scopes the wipe to characters, names, and guilds created on the Stress Test servers. Do not read that as a statement that pre-existing Beta characters are wiped.

Blizzard's separate Beta article calls October 21 the last full day of testing, while the roadmap graphic reads “SEPT 17 - OCT 22.” The date boundary remains unresolved, and the temporary Stress Test announcement does not establish a permanent Beta end date.Sources: Blizzard's Stress Test forum announcement, updated Stress Test news article, Beta article, and What's Next roadmap.

October 1 Snapshot: The Five-Zone Respawn List Is One Bullet

Blizzard's October 1 notes place the five named zones in one increased-rate bullet, not the whole respawn change list. That snapshot also lists adjustments in Dun Morogh, Loch Modan, Westfall, Redridge Mountains, and Wailing Caverns, including slower respawns in Loch Modan and different changes by target in Westfall. Post 4 set a Beta level cap of 30 for that stage; this is a dated note, not a verified cap for the build listed above.

Blizzard's request is: “Please continue to submit any areas where you have difficulty completing quests, and we will continue to make adjustments.” Try one quest that is hard to finish, then record what prevented progress and whether your next attempt differed.Source: Blizzard Beta Development Notes, October 1 post 4, Quests; retained October 8 retrieval.

Partager l’image : écran de chargement de la bêta de WoW Forever pour Excavations : les Paluns, un croquis orange d’un chemin forestier avec un chariot et un tonneau sous des arbres qui forment une voûte

Rédiger un rapport reproductible

Pour un rapport utile, indiquez :

• La build du client et la date du test
• La classe, la race, le niveau et la zone
• La quête, la cible, le donjon ou le sort exact
• Les étapes qui reproduisent le problème
• Le résultat attendu et le résultat obtenu
• Une capture d’écran ou un court clip, si utile

Ce sont des champs éditoriaux, pas un formulaire Blizzard. Notez la build, car une note datée ultérieure peut modifier ou corriger une cible précédente. Pour une quête, nommez l’objectif exact et la créature ou l’objet, puis notez l’attente et ce qui s’est passé ensuite. Pour une récompense de donjon, indiquez la quête, le niveau du personnage et les valeurs affichées. Pour un problème de Cooldown Manager, indiquez la classe, le sort, le réglage et si le sort est apparu.

For sharing or comparing player feedback, browse a relevant conversation in the WoW Forever Beta Discussion category. Its October 17 listing includes feedback threads. The link is to public discussion, not a designated bug-report form.

Vérifier les dates avant de répéter un problème

Le post de notes de développement du 1er octobre répertorie un problème de chances de toucher de Spécialisation Ambidextrie pour le guerrier dans les problèmes connus, alors que la section guerrier du même post signale un correctif. Une mise à jour distincte pour le guerrier, publiée le 2 octobre à 02:57 UTC (le 1er octobre à 19:57 PDT), indique que le correctif figurait dans cette même build bêta du 1er octobre et renvoie aux notes du 1er octobre. Gardez ce conflit visible ; ne le présentez pas comme un nouveau correctif du 2 octobre.

Le fil de maintenance du 6 octobre annonçait, à 21:20Z, un redémarrage à 15:00 PDT, environ 40 minutes plus tard. Un des correctifs listés visait les quêtes dont les objets censés être réapprovisionnés dans des coffres avaient disparu. À 21:52Z, le même fil listait deux autres correctifs intégrés à ce redémarrage : les déconnexions en ascenseur ou en transport, et une erreur en rejoignant ou en quittant une guilde. Ce sont des déclarations d’annonce de Blizzard, pas des résultats testés de façon indépendante.