View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0023899 | Legion Core | Classes - Warrior - Воин | public | 2023-01-21 15:12 | 2023-05-02 11:14 |
| Reporter | Officespace | Assigned To | Whoop | ||
| Priority | high | Severity | major | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Platform | Windows | OS | 10 | OS Version | x64 |
| Summary | 0023899: Warrior Quest "The Fate of Hodir" bugged | ||||
| Description | The quest for Warrior Campaign "The Fate of Hodir" is way bugged. It's a scenario. It was even bugged on Retail, according to the wowhead comments in 7.3.5. https://www.wowhead.com/quest=42974/the-fate-of-hodir#comments There is no "Dive" button, the bats up above just sit still, most of the time you can't even melee the Warlocks on them because it says you're facing the wrong way, so you have to rely on Arms warrior artifact and bladestorm or whirlwind, if you're a fury warrior. The bats are supposed to patrol overhead, not just sit there. Did delete the WTF, Cache, and Interface folders (moved them to another directory for backup), didn't help because I couldn't connect to uWow.biz server. Quest is not currently able to be completed. Legion x 100 realm, quest ID 42974. | ||||
| Steps To Reproduce | Make the bats patrol, then when we leap up on them please have us facing the proper way towards the warlocks so we can melee the warlocks properly. Also, Let us leap onto the final bat instead of making us just heroic throw it to death. If we can't leap onto the last one, we can't "fly" the bat near Hodir and "Dive" (a button that doesn't even show up), which means 'crash land near Hodir', so all we get to is to kill 6 bats and then get to Hodir who just stands still there and our only choice is to abandon the quest. | ||||
| Additional Information | Please watch the video from wowhead to see how the actual scenario is supposed to play out. Right now warriors are unable to finish it. Video: https://www.wowhead.com/quest=42974/the-fate-of-hodir#videos:id=120070 | ||||
|
|
My hardware is good but it was recorded uncompressed, so I had to compress it through video editor to reduce the file size..meaning lower frames/sec. Anyway, this is my experience on your server when I run the scenario: https://youtu.be/xENVSxABuuM |
|
|
It will be 1080p |
|
|
STILL bugged, even though now I can recruit 7 followers. There is SOMETHING wrong with my Legionfall campaign on my warrior Crystlmethod! It NEEDS to be completely reset starting with the "Armies of Legionfall" / "Breaching the Tomb" questline for Broken Shore, for my warrior. I told you, I DIED during the scenario when I first went to The Broken Shore scenario and never finished the scenario on my warrior. It's F'D up. |
|
|
https://imgur.com/a/czm0ctx |
|
|
You've got your quests out of order. Fix it for warriors. https://us.battle.net/support/en/article/119568 Look at the quest storyline on the right. https://www.wowhead.com/quest=42974/the-fate-of-hodir How am I supposed to do "Champions of Legionfall" when "The Fate of Hodir" comes BEFORE "The Fate of Hodir" in the questline??? This bug is now severe, and not high priority. FIX IT. Re-Script the questing. |
|
|
Can't do Champions of Legionfall questline until "A Hero's Weapon". And, since "A Hero's Weapon" comes BEFORE "The Fate of Hodir" in the quest chain, I can't do The Fate of Hodir. Believe me now? Fix it and re-script it. |
|
|
IDGAF what BTWQuests says about Battlelord Campaign. The very ending of that tier is WRONG. A Hero's Weapon comes BEFORE The Fate Of Hodir. |
|
|
IDGAF what BTWQuests says about Battlelord Campaign. The very ending of that tier is WRONG. A Hero's Weapon comes BEFORE The Fate Of Hodir. broken1.jpg (660,330 bytes) |
|
|
broken2.jpg (767,437 bytes) |
|
|
Warrior Campaign / Broken Shore for Warriors NEEDS to be re-scripted. All people ever care about is their stupid mythics, nobody ever actually cares to quest. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2023-01-21 15:12 | Officespace | New Issue | |
| 2023-01-21 15:12 | Officespace | Status | new => assigned |
| 2023-01-21 15:12 | Officespace | Assigned To | => Shadowraze |
| 2023-01-21 16:15 | Officespace | Note Added: 0064985 | |
| 2023-01-21 16:18 | Officespace | Note Added: 0064986 | |
| 2023-01-24 19:22 | Officespace | Note Added: 0065186 | |
| 2023-01-24 19:24 | Officespace | Note Added: 0065187 | |
| 2023-01-25 15:34 | Shadowraze | Assigned To | Shadowraze => Kyckax |
| 2023-01-26 09:47 | Officespace | Note Added: 0065273 | |
| 2023-01-26 09:56 | Officespace | Note Added: 0065274 | |
| 2023-01-26 10:00 | Officespace | Note Added: 0065275 | |
| 2023-01-26 10:23 | Officespace | File Added: broken1.jpg | |
| 2023-01-26 10:23 | Officespace | Note Added: 0065276 | |
| 2023-01-26 10:24 | Officespace | File Added: broken2.jpg | |
| 2023-01-26 10:26 | Officespace | Note Added: 0065277 | |
| 2023-02-08 11:40 | Kyckax | Status | assigned => confirmed |
| 2023-02-17 15:00 | Kyckax | Assigned To | Kyckax => Whoop |
| 2023-05-02 11:14 | Whoop | Status | confirmed => resolved |
| 2023-05-02 11:14 | Whoop | Resolution | open => fixed |