WoW Forever quests

Every quest read from the World of Warcraft: Forever beta so far: 61 quests in 10 dungeons, one raid and one battleground, grouped by the instance the quest log files them under. Quests are server-side in Forever, so client build 1.60.1.69893 carries their ids and nothing more; every line below is an answer the beta server gave a running client. 15 of these quests did not exist in Classic Era.

Each name opens that quest's own page: the objective, who hands it out and who takes it in where the quest's own wording or the beta log names them, the text the quest giver reads out, everything it pays, and the chain it sits in.

Ragefire Chasm

Dungeon · finder level 13 · 6 quests

Ragefire Chasm: bosses and how to get in, with all 6 quests in one place →

The Hall of Thanes

Dungeon · finder level 13 · 4 quests · 4 new

The Hall of Thanes: bosses and how to get in, with all 4 quests in one place →

Ruins of Lordaeron

Dungeon · finder level 15 · 10 quests · 10 new

Ruins of Lordaeron: bosses and how to get in, with all 10 quests in one place →

Deadmines

Dungeon · finder level 16 · 7 quests · 1 new

Deadmines: bosses and how to get in, with all 7 quests in one place →

Wailing Caverns

Dungeon · finder level 17 · 9 quests

Wailing Caverns: bosses and how to get in, with all 9 quests in one place →

Shadowfang Keep

Dungeon · finder level 18 · 4 quests

Shadowfang Keep: bosses and how to get in, with all 4 quests in one place →

Blackfathom Deeps

Dungeon · finder level 22 · 8 quests

Blackfathom Deeps: bosses and how to get in, with all 8 quests in one place →

Stormwind Stockade

Dungeon · finder level 23 · 1 quest

Stormwind Stockade: bosses and how to get in, with all 1 quest in one place →

Razorfen Kraul

Dungeon · finder level 24 · 1 quest

Razorfen Kraul: bosses and how to get in, with all 1 quest in one place →

Gnomeregan

Dungeon · finder level 25 · 6 quests

Gnomeregan: bosses and how to get in, with all 6 quests in one place →

Molten Core

Raid · finder level 60 · 2 quests

Molten Core: bosses and how to get in, with all 2 quests in one place →

Warsong Gulch

Battleground · 3 quests

Warsong Gulch: the queue and the map, with all 3 quests in one place →

How this list is read, and how it grows

The client knows a quest only as a number. Its title, its objective, the text the quest giver reads out and the rewards all come from the server, so a quest reaches this page once the beta server has described it to a client that asked. 12 of the 52 instances in build 1.60.1.69893 have quests here today, and the list grows as more of the beta is played.

marks a quest that did not exist in Classic Era. A level is the level the quest log prints for the quest, not the level the door asks for, and a side is shown only where the quest is offered to one faction. Nothing here is copied from another site: every line is what the beta server told a client.

Where does this quest list come from?

Quests are server-side in World of Warcraft: Forever. Client build 1.60.1.69893 carries their ids and nothing more: no titles, no zones, no quest givers. Every quest here is an answer the beta server gave a running client, read out of the client's own quest cache.

Does it say who gives each dungeon quest and who takes it in?

Where the quest's own wording names them, or the beta log has shown it. The client's quest rows carry no quest giver at all, so a name here is one of two things: read out of the quest's own text — "bring his head to Gryan Stoutmantle", which is Blizzard's wording and not a sighting — or recorded from the beta log as the game is played, with the title under the name and where the NPC stands. 52 of the 61 quests listed here name at least one end, all of them read from the quest text, and every page marks which of the two it is showing.

Why do some quests have no Wowhead link?

Wowhead's Forever database has a page for every quest Classic Era already had, and none for a quest Forever added: 15 of the 61 quests here are new, so their pages say that no database lists them yet and print what the beta client itself returned instead.