Bug in game after latest update

[David53]

There appears to be a new bug in the game in the "need a boat" quest. I was trying another play through after obtaining the death whistle, and tried to talk to Ansen. I exhausted all topics, then examined under the tarp as he mentioned. All that Benedek says is "Oh My God", and the corpses that were in the boat weren't shown at all. (I seemed to remember seeing the corpses on my earlier play through.) After examining the boat, there are no more conversation choices with Ansen left at all, neither about the boat, nor anything else. He never mentions the priest, and it's not possible to even visit the priest or the church, since Ansen never mentions him, or the banishment that the priest put on him.

This quest worked flawlessly earlier, but now, it doesn't work, and the game is stuck at this point.

Also, I should also mention that the conversation with the boy, Antun, who told me about Ansen, was a bit different from the conversation that I remember from my earlier play through. It seemed shorter than I remember, with fewer topics, and the boy never mentioned anything about keeping the conversation secret, which I distinctly remembered him doing in my earlier play through.

It's almost as though some parts are "missing" that were present in the game before.

I hope that the developer can fix this one.

[David53]

Update. After the latest patch from earlier today, the "find a boat" quest now seems to work, and I was able to examine what was in the boat properly, and continue the conversation with Ansen so that now, I can talk to the priest.

I have no idea why it wasn't working yesterday, but for now, it appears to be working.

[The-Mark Entertainment]

Originally posted by David53:

Update. After the latest patch from earlier today, the "find a boat" quest now seems to work, and I was able to examine what was in the boat properly, and continue the conversation with Ansen so that now, I can talk to the priest.

I have no idea why it wasn't working yesterday, but for now, it appears to be working.

Sorry for the long wait, we somehow forgot to let you know back then that we fixed the bug your reported here. It literaly went this way: we saw your post, went to fix that bloody bug, pushed the update, and then forgot to tell you about it :-D