SureAI

Having trouble with this quest.

While talking to Jespar on the Watchtower, I got to the point in the conversation where he's talking about Lysia. (I think that's her name)

After the sentence "Well, she started to expect more from our partnership" he just stops talking and I regain the ability to move my character around, and when I go up to him to interact it just says 'This person is busy' so I can't progress any further.

Is this a known bug?


EDIT AND TEMPORARY FIX: If you click on him with console open and type in resetai, he will walk to another side of the Watchtower and start talking again.

So, the quest started, everything was nice and easy, until Jespar decided just to stay still and eternally smoke his pipe. Like, really, eternally. Game kept telling me that "the person is busy" and I reloaded one of the past saves.

This time Jespair found something really interesting in the wine box and became "very busy" again.

I reloaded the same save again, walked to the tower... a-a-a-and Jespar stopped even noticing my character. I've read the forum, tried to use "resetai" command, tried to reload another saves, but nothing worked.

Is there any possibility of completing quest without skipping dialogs via console? I mean, 600exp are nice, but I would really appreciate if I have an opportunity to control what my character is saying and, like, understand the story more.

How did you use resetai command? Did you point Jespar (clicked on in console command mode) ? I had the same problem but resetai worked for me.

I've also read that waiting 10 minutes or so should help "unlock" him

Yeah, I clicked on him in console mode, he... flashed? - like when you use "resurrect" command on mobs/npcs. He changed his pose (unfolded his arms), but nothing more, not a tiny spark of intelligence in his beautiful high-textured eyes.

Well, I have a thought, that I just have to give him a few more minutes. I guess, I should really give it a try

UPD: I don't know what happened, but it seems, that you could repair this bug by simple quiting and starting the game again. The most obvious method, of which I, of course, haven't even thought. Wow.

These are navmesh bugs of which we are aware off. Thanks for the reports.