Skip to content

Party members won't hold ground

Hi, in the hobgoblin ambush south of Beregost, I got Jaheira to cast Entangle and it worked brilliantly, snaring 3 hobs, but the other party members, all with ranged weapons selected, keep charging at the hobs and getting killed as they get entangled. They won't hold their ground no matter how often I try to back them off. Is this a bug? Is is some weird function of Entangle? What's happening?

Comments

  • elminsterelminster Member, Developer Posts: 16,317
    edited June 2013
    I'm assuming you are on PC? If so try going here http://forum.baldursgate.com/discussion/12053/imoen-just-ran-in-an-ogre-with-her-bow-again-and-got-smashed-again there is the default Baldur's Gate script you can download to solve this. Yes it is a bug and it reportedly will be solved in the next patch (which is coming out... "soon").
  • ShusakuShusaku Member Posts: 18
    Yes I'm on a Pc. Thanks for the link to the thread, which I just read. I think I might turn the AI off - which I never needed to do when I played the whole game through a couple of times 10 years ago. Seems like the BG Enhanced is just a different set of bugs, rather than cleaning up the old game, which was what I was hoping for when I bought it. Sigh...
  • elminsterelminster Member, Developer Posts: 16,317
    Shusaku said:

    Yes I'm on a Pc. Thanks for the link to the thread, which I just read. I think I might turn the AI off - which I never needed to do when I played the whole game through a couple of times 10 years age. Seems like the BG Enhanced is just a different set of bugs, rather than cleaning up the old game, which was what I was hoping for when I bought it. Sigh...

    From the sounds of things they are putting a lot of work into it and the next patch, but yea there are still a few kinks like what you've experienced.
  • mlnevesemlnevese Member, Moderator Posts: 10,214
    The character moving to shoot is actually a BG2 bug that was never fixed. As the EE is based in the BG2 engine the bug came along. It's now fixed in the next patch.
Sign In or Register to comment.