Need help for AC p2
The problem is happening because the devs are too lazy to fix a game-breaking bug that has existed since the dungeon was created. There is no way to fix Deltha aside from killing her, and even that doesn’t work 100% of the time anymore. Many people believe it is due to the mobs in front of the boss area, and that killing them before entering will prevent her from glitching.
I wouldn’t call it laziness, but I certainly wish we could figure this one out. Truth be told I’ve spent days trying to dissect her script and fix this very problem, but there’s not a 100% repro for it, even with the ooze mobs being completely removed or killed it still happens from time to time.
I’ll get it one day though!
(edited by Robert Hrouda.1327)
I’ll get it one day though!
You got this. o_o)-b
It’s simple: Kill the Batman.
Youtube Channel – http://www.youtube.com/t3llularman
When you can’t solve a problem, work around it! Simply have her script periodically have her move toward the WP and initiate the trap placing sequence if a player is in range of it. That way, if it fails the first time, it will initiate again in a few seconds after.
When you can’t solve a problem, work around it! Simply have her script periodically have her move toward the WP and initiate the trap placing sequence if a player is in range of it. That way, if it fails the first time, it will initiate again in a few seconds after.
I reduced the occurrences of it happening by this very technique. She has a special script segment that activates and does something similar to what you described, and the occurrences lowered as a result… but… sometimes it still happens, lol.
Okay, “laziness” was a bit harsh, I agree.
I don’t believe it is the Ooze mobs that is the issue, though. The general consensus is that Deltha gets stuck in the “in-combat” status which will prevent the event from triggering. Presumably, killing Deltha resets her in-combat status, which is probably why she usually works afterward.
Generally, when people skip those mobs, Detha usually ends up tangling with the Graveling mobs, not so much the Oozes. This is why people have begun killing the Gravelings in the area before the boss room, and that seems to prevent her from bugging.
After observing the way Grast behaves on the Colussus fight, could there be issues with queued actions on the NPCs? It seems like if an action is queued, the AI will focus on nothing else besides that action, regardless of what the conditions call for. If that’s the case, could queued actions have a timeout that, if not executed within, say, 10s, it is purged? As a fellow developer by trade, just figured I’d throw things out there…
While I have not experienced the bug with Detha firsthand, it sounds like it might be related to the in-combat bug that players occasionally experience in non-instanced PvE. I’ve reported it several times in-game, but the bug has persisted since launch.
A short explanation: Every now and then, a player will finish a fight, either by killing the target or by breaking aggro and allowing the mob to reset. However, the game will not register that combat has ended, leaving the in-combat UI indicator active, as well as leaving the in-combat debuffs to movement speed, waypoint usage, etc., in effect.
Is it possible that something similar is happening with Detha as with human players? Is it possibly an issue with the in-combat scripting rather than her individual NPC scripting?
Just a thought.
Thank you for good advice. I hope in future they will fix this issues. Advice for dev, remove that speed run. Add more task to dungeon completion, like to clear a way to final room. So it will be easy to fix this bug. Running and skipping mobs is not good for new players. So make dungeon more reward-able but it takes more time to do. Like you kill mobs if you want to pass.