AC Explorable - Hodgins won't budgins
Our group had the same problem last night. We finally had to restart and it worked fine.
I have had issues with both Hodgins and Detha. The only option is to restart the instance completely. There will always be one person who is still attacheted to the instance even after the group disbanded and has exit the dungeon. In that case, request that person to rezone or login and logout to solve the issue.
It is a head ache. Don’t even get me started with the Miss! Miss! Miss! Miss! Miss! Miss! Miss! Miss! Miss! Miss! Miss! Miss! Miss! Miss! Miss! Miss! Miss! Miss! Miss! Miss!
In Ascalonian Catacombs, twice now Hodgins has “pulled a Detha” (i.e., done what Detha used to do at the Flooded Temple – and sometimes still does at the Hall of Champions) and simply ignored his waypoint.
He still follows players around but doesn’t trigger the “second scepter” script, so everyone is stuck. And since the tokens come only from the last boss now, all the work killing every boss until then goes without any useful reward.
So:
a) Please fix Hodgins or add some guaranteed way for players to reset him (we tried killing him, killing ourselves, killing every single mob in the instance, going out and back in, nothing worked).
b) Give players tokens for the work they actually did in the dungeon (i.e., X tokens for each boss kill, plus some tokens at the end) , instead of simply rewarding the player’s presence in the dungeon at the time the last boss dies. If someone plays through the dungeon, kills every boss, and then gets kicked (or disconnects, etc.) at the last boss, then that person obviously deserves to get tokens, while the guy who joined and just happened to be at the dungeon entrance when the final boss died doesn’t deserve to get 60 tokens (and yet that’s exactly what happens with the current system).
Obviously b) isn’t a true bug fix (just a less nonsensical design), but it would make the dungeon-breaking bugs a lot more bearable if people could at least get some tokens out of these bugged dungeons.
I have the same issue. My group and I took an hour trying to get through and learn this Dungeon just to find the second script is bugged. We all get to the location on the map, but nothing happens nor does the NPC initiate anything. Was very frustrating and discouraging considering the time we all put in to come together to do this and to not get even one token because we couldn’t complete the dungeon. This is seriously broken and must be fixed.
I just had this twice but my party disappeared and then after we got to boss it kicked us from the dungeon :s.
Problem with solution B is that ppl will just go in kill first boss, exit, reset and go in kill first boss and exit again (used to be that way in beta, and that is what happened).
This just happened to my group tonight. First time I’ve ever seen this bug and I’ve probably done the Howling King path 10 times.
Guardian – Commander – Officer of Rethesis [RE] Tarnished Coast
We’re aware of this issue, but we’ve had a hard time consistently reproducing it which makes it hard to fix. We’ll continue to investigate this, but if you have any additional information you can provide on this, we’d appreciate it. Thanks for the reports!
— Live Response Embed —
In my experience this happens when groups run through mobs without fighting them and Hodgins aggros onto them and then ports/runs to the players outside of the mob leash range. This also occurs sometimes with Detha if you run through the oozes to start the mortar fixing event. Solutions my guild has found is to have everyone run to the far side of that room and if that does work then kill all the mobs that you previously ran through, or lead hodgins to his death and rez him.
(edited by Hooya.6172)
I’ve gotten hodgins bugged in Path 1 at 2nd scepter pieces and Detha bugged at mortar building, as desribed above, multiple times as well. Just hit another instance of Path 1 today, with the total probably being ~5-6 abandoned dungeon runs out of a total of ~28 attempts (based on my full set armor progress). Hopefully from your telemetry, you have a better idea of success rate here at certain points. It’s getting pretty discouraging, especially since it’s harder to find party with FOTM now.
Things I remember:
Depending on the party, we would run past certain mobs, but I’ve had bugged runs for both cases (kill all enemies and run through maximum mobs). This doesn’t seem to be a deciding factor.
Occasionally, killing Hodgins or Detha and bringing to relevant location seems to work, less than 1/4 of the time though (Think I’ve had 2 successful resets this way). This may have to do with who NPC is following or latched onto. If we knew who the NPC was supposed to follow (as mentioned by a post above) ie the leader, closest party member, etc, this might help. Hodgins in particular seems to flit about a lot, especially when bugged.
I’m not certain, but I think the non-party leader has picked up the 1st scepter piece each time I’ve been bugged. This seems an unlikely cause and likely not remembered correctly.
Similar thing happened in Sorrow’s Embrace (story mode) the last time I was there. After Caithe and Zojja get to the closed door and play 3 movies, Zojja is supposed to start working on opening the door while several waves of dredge attack. Instead, both NPCs just stood there (not even following players), no dredge attacked, and the door remained closed.
We even kited some mobs from a long way off (using scorpion wire to prevent them from leashing back), used them to kill Zojja and Caithe, but after respawning they still wouldn’t open the door or trigger the event.
Seems like some fundamental design bug (as opposed to an accidental code bug) in the way events are triggered, possibly also responsible for the dozens of events stuck all over the game world (areas between level 50 and 79 seem to have more stuck events than working ones).
Our Party once this also happened. It was quite normal, but he just stand there doing nothing. Madness!
Asura thing.
How recently did this happen? I believe it should have been fixed with the last patch.
— Live Response Embed —