History UnwinnableByMistake / WorldofWarcraft

4th Apr '18 1:15:57 PM KelpTheGreat
Is there an issue? Send a Message


* The Battle of Darrowshire is known for two things: concluding an epic TearJerker storyline and being prone to bug. The player is supposed to use a quest item to summon ghosts to re-enact a battle, and then make sure one particular ghost isn't "killed" before his time. Sometimes the ghosts would simply refuse to appear. Other times Captain Redpath, the ghost you're supposed to keep alive, would simply drop off the face of Azeroth, and the battle would go on indefinitely, preventing anyone else from doing that quest until server reset.

to:

* The Battle of Darrowshire is known for two things: concluding an epic TearJerker storyline and being prone to bug. The player is supposed to use a quest item to summon ghosts to re-enact a battle, and then make sure one particular ghost isn't "killed" before his time. Sometimes the ghosts would simply refuse to appear. Other times Captain Redpath, the ghost you're supposed to keep alive, would simply drop off the face of Azeroth, and the battle would go on indefinitely, preventing anyone else from doing that quest until a server reset.



** The mad Blood Elf, Prince Kael'Thas Sunstrider, final boss was of the Tempest Keep raid was Unwinnable By Mistake because the mechanics of his encounter involve him being un-attackable until you've defeated several other challenges. Before being fixed, his aggro list (the priority order that determines who he attacks) would get filled up with all the healing that was being done to raiders during the first part of the fight. When he finally became active, he would attack and kill all the healers while tanks futily assaulted him, failing to get his attention as they tried to catch up with several hundred thousand points of healing aggro.
** Some fans have speculated this was more UnwinnableByDesign. Each expansion has tiers of gear. 2.0.10 was still in the first "season" of TBC and said bosses dropped gear for the second tier of the expansion. Around that one can note a sudden drop in "Unwinnable by Design" bosses and new bosses having other pacing mechanisms added that slow beating said bosses.

to:

** The mad Blood Elf, Prince Kael'Thas Sunstrider, final boss was of the Tempest Keep raid raid, was Unwinnable By Mistake Mistake, because the mechanics of his encounter involve him being un-attackable until you've defeated several other challenges. Before being fixed, his aggro list (the priority order that determines who he attacks) would get filled up with all the healing that was being done to raiders during the first part of the fight. When he finally became active, he would attack and kill all the healers while tanks futily futilely assaulted him, failing to get his attention as they tried to catch up with several hundred thousand points of healing aggro.
** Some fans have speculated this was more UnwinnableByDesign. Each expansion has tiers of gear. 2.0.10 was still in the first "season" of TBC and said bosses dropped gear for the second tier of the expansion. Around that time one can note a sudden drop in "Unwinnable by Design" bosses and new bosses having other pacing mechanisms added that slow down the beating said bosses.



* The 10-man version Horridon in the Throne of Thunder raid was nearly impossible to beat when the instance was first implemented. Somehow, the programmers forgot to scale the HP of the adds to 10-man difficulty, leaving them with the same HP as their 25-man counterparts. This meant it was mathematically impossible for the average 10-man group to defeat Horridon.

to:

* The 10-man version of Horridon in the Throne of Thunder raid was nearly impossible to beat when the instance was first implemented. Somehow, the programmers forgot to scale the HP of the adds mobs to 10-man difficulty, leaving them with the same HP as their 25-man counterparts. This meant it was mathematically impossible for the average 10-man group to defeat Horridon.



** Speaking of the worgen starting zone, it's possible to glitch your way out of the zone before you get fully turned into a Worgen... with no way to get back and never unlocking several features.
** Near the end of the Worgen starting zone, you have to fight [[spoiler: Sylvanas Windrunner]] by using an area-of-effect buff on friendly [=NPCs=], increasing their damage output and health generation. Unfortunately, the buff could also affect the boss, causing her health to keep regenerating faster than your NPC allies could deplete it, and if she wasn't killed fast enough, the entire quest would reset. Possibly overlaps with UnwinnableByInsanity, but keep in mind, this happens in a ''starting'' zone, and it was entirely possible for new players to unintentionally keep buffing her without realizing what they were doing.

to:

** Speaking of the worgen starting zone, it's possible to glitch your way out of the zone before you get fully turned into a Worgen...worgen... with no way to get back and never unlocking several features.
** Near the end of the Worgen worgen starting zone, you have to fight [[spoiler: Sylvanas Windrunner]] by using an area-of-effect buff on friendly [=NPCs=], increasing their damage output and health generation. Unfortunately, the buff could also affect the boss, causing her health to keep regenerating faster than your NPC allies could deplete it, and if she wasn't killed fast enough, the entire quest would reset. Possibly overlaps with UnwinnableByInsanity, but keep in mind, this happens in a ''starting'' zone, and it was entirely possible for new players to unintentionally keep buffing her without realizing what they were doing.
9th Jan '18 5:09:27 AM Cryoclaste
Is there an issue? Send a Message


''WorldOfWarcraft'', being an open ended {{MMORPG}}, is not subject to unwinnable situations as a whole (it's more of an EndlessGame). But there have been numerous occasions when specific quests or dungeons have been broken because of scripting failures or other issues. In most cases, these have to be fixed by a game patch. Notorious ones:

to:

''WorldOfWarcraft'', ''VideoGame/WorldOfWarcraft'', being an open ended {{MMORPG}}, is not subject to unwinnable situations as a whole (it's more of an EndlessGame). But there have been numerous occasions when specific quests or dungeons have been broken because of scripting failures or other issues. In most cases, these have to be fixed by a game patch. Notorious ones:
29th Jul '16 5:16:08 AM Digsu
Is there an issue? Send a Message

Added DiffLines:

** Near the end of the Worgen starting zone, you have to fight [[spoiler: Sylvanas Windrunner]] by using an area-of-effect buff on friendly [=NPCs=], increasing their damage output and health generation. Unfortunately, the buff could also affect the boss, causing her health to keep regenerating faster than your NPC allies could deplete it, and if she wasn't killed fast enough, the entire quest would reset. Possibly overlaps with UnwinnableByInsanity, but keep in mind, this happens in a ''starting'' zone, and it was entirely possible for new players to unintentionally keep buffing her without realizing what they were doing.
16th Oct '14 1:34:34 PM asilvahalo
Is there an issue? Send a Message


** Speaking of the worgen starting zone, it's possible to glitch your way out of the zone before you get fully turned into a Worgen... with no way to get back and never unlocking several features.

to:

** Speaking of the worgen starting zone, it's possible to glitch your way out of the zone before you get fully turned into a Worgen... with no way to get back and never unlocking several features.features.
* In the pre-patch for the ''Warlords of Draenor'' expansion, Blizzard instituted a "stat squish," which brought stats down to more manageable levels, and took out some of the exponential gear scaling between past expansions. Everything was fine at max level, but content from about level 40 to level 89 ended up very overtuned. A hotfix was put in a couple days later to fix this, and while it fixed the problem, it brought with it a worse GameBreakingBug : all monsters with some sort of resource bar (mana, energy) suddenly hit even harder than they had before. For example, some level 1 wyrms you have to kill for your first quest as a blood elf were ''meleeing'' for two or three times the amount of health a level 1 player actually has.
22nd Sep '14 7:06:42 AM Nirual
Is there an issue? Send a Message


* There is a nasty bug in the worgen starting zone which can leave characters completely unable to progress. You've just arrived in Duskhaven and you receive a quest to retrieve some potion reagents from a crate. When this happens, a Forsaken assassin is supposed to spawn, which you have to kill. Unfortunately for some players, they complete the quest to find the crate, but the assassin doesn't spawn. You can't go back and abandon the quest because you've completed it. There is no other way to make the assassin spawn. Killing them is the only way to start the next quest chain - but you can't, because, etc. Barring sending a ticket and waiting (and waiting...) for a GM response, there's nothing you can do. This bug is still in the game in patch 5.4.

to:

* There is a nasty bug in the worgen starting zone which can leave characters completely unable to progress. You've just arrived in Duskhaven and you receive a quest to retrieve some potion reagents from a crate. When this happens, a Forsaken assassin is supposed to spawn, which you have to kill. Unfortunately for some players, they complete the quest to find the crate, but the assassin doesn't spawn. You can't go back and abandon the quest because you've completed it. There is no other way to make the assassin spawn. Killing them is the only way to start the next quest chain - but you can't, because, etc. Barring sending a ticket and waiting (and waiting...) for a GM response, there's nothing you can do. This bug is still in the game in patch 5.4.4.
** Speaking of the worgen starting zone, it's possible to glitch your way out of the zone before you get fully turned into a Worgen... with no way to get back and never unlocking several features.
13th Jul '14 7:33:39 AM Medraut
Is there an issue? Send a Message


* The 10-man version Horridon in the Throne of Thunder raid was nearly impossible to beat when the instance was first implemented. Somehow, the programmers forgot to scale the HP of the adds to 10-man difficulty, leaving them with the same HP as their 25-man counterparts. This meant it was mathematically impossible for the average 10-man group to defeat Horridon.

to:

* The 10-man version Horridon in the Throne of Thunder raid was nearly impossible to beat when the instance was first implemented. Somehow, the programmers forgot to scale the HP of the adds to 10-man difficulty, leaving them with the same HP as their 25-man counterparts. This meant it was mathematically impossible for the average 10-man group to defeat Horridon.Horridon.
* There is a nasty bug in the worgen starting zone which can leave characters completely unable to progress. You've just arrived in Duskhaven and you receive a quest to retrieve some potion reagents from a crate. When this happens, a Forsaken assassin is supposed to spawn, which you have to kill. Unfortunately for some players, they complete the quest to find the crate, but the assassin doesn't spawn. You can't go back and abandon the quest because you've completed it. There is no other way to make the assassin spawn. Killing them is the only way to start the next quest chain - but you can't, because, etc. Barring sending a ticket and waiting (and waiting...) for a GM response, there's nothing you can do. This bug is still in the game in patch 5.4.
26th Dec '13 6:02:14 PM Valiona
Is there an issue? Send a Message


* Many quests involving scripted [=NPCs=] could break if the script failed to leave the NPC in an interactive state upon completion. This prevents any other players from getting or completing its quest(s) until the server is restarted or a kind GM despawns the offending NPC.

to:

* Many quests involving scripted [=NPCs=] could break if the script failed to leave the NPC in an interactive state upon completion. This prevents any other players from getting or completing its quest(s) until the server is restarted or a kind GM despawns the offending NPC. NPC.
** One common example is one quest in Gilneas, the Worgen starting zone, when, as you're sent to retrieve a cat, you encounter a Forsaken spy, but [[spoiler:Grandma Wahl, in her worgen form]], arrives and helps you take down the spy. However, sometimes, the spy doesn't die, leaving you and any other Worgen players at that point unable to proceed.
3rd May '13 1:19:00 PM spoonofevil
Is there an issue? Send a Message


* Vanessa [=VanCleef=], last boss of Heroic Deadmines, sometimes despawns if her aggro target falls off the top deck.

to:

* Vanessa [=VanCleef=], last boss of Heroic Deadmines, sometimes despawns if her aggro target falls off the top deck.deck.
* The 10-man version Horridon in the Throne of Thunder raid was nearly impossible to beat when the instance was first implemented. Somehow, the programmers forgot to scale the HP of the adds to 10-man difficulty, leaving them with the same HP as their 25-man counterparts. This meant it was mathematically impossible for the average 10-man group to defeat Horridon.
22nd Sep '12 1:55:35 AM greymalkin
Is there an issue? Send a Message


* On the first few days of ''Cataclysm'', the final quest of Vashiir was prone to this. To avoid spoilers, a large battle happens, and is supposed to go into cutscene mode. However, sometimes it didn't, letting your character wander about and attack people. If you attacked even one person, the semi-cutscene would break, and the quest would not be flagged as completed, so you would have to restart the quest with no idea of what you did wrong.

to:

* On the first few days months of ''Cataclysm'', the final quest of Vashiir was prone to this. To avoid spoilers, a large battle happens, and is supposed to go into cutscene mode. However, sometimes it didn't, letting your character wander about and attack people. If you attacked even one person, the semi-cutscene would break, and the quest would not be flagged as completed, so you would have to restart the quest with no idea of what you did wrong.
11th Jun '12 5:43:14 PM emobob
Is there an issue? Send a Message


** The mad Blood Elf, Prince Kael'Thas Sunstrider, final boss was of the Tempest Keep raid was Unwinnable By Mistake because the mechanics of his encounter involve him being un-attackable until you've defeated several other challenges. Before being fixed, his aggro list (the priority order that determines who he attacks) would get filled up with all the healing that was being done to raiders during the first part of the fight. When he finally became active, he would attack and kill all the healers while tanks futility assaulted him, failing to get his attention as they tried to catch up with several hundred thousand points of healing aggro.

to:

** The mad Blood Elf, Prince Kael'Thas Sunstrider, final boss was of the Tempest Keep raid was Unwinnable By Mistake because the mechanics of his encounter involve him being un-attackable until you've defeated several other challenges. Before being fixed, his aggro list (the priority order that determines who he attacks) would get filled up with all the healing that was being done to raiders during the first part of the fight. When he finally became active, he would attack and kill all the healers while tanks futility futily assaulted him, failing to get his attention as they tried to catch up with several hundred thousand points of healing aggro.
This list shows the last 10 events of 18. Show all.
http://tvtropes.org/pmwiki/article_history.php?article=UnwinnableByMistake.WorldofWarcraft