Last week we brought you word on the mean game crashing bug in Fable II which seems to be the result of some coding issue in the recently released online co-op patch. Now we have word that there is another killer bug present in the game, and this one has the potential to strike anyone who gets just a teeny bit careless during the main questline.

According to the reports, the bug is present in the "Monk’s Quest" mission, when the abbot tasks the player with completing a quest at the Temple of Light. Players are finding that if they walk away from the abbot without allowing him to finish briefing the player on the mission, the quest is rendered unpassable and gamers are unable to advance any further into the game.

Here’s what the folks at Lionhead have to say about the problem, as posted on the official community message boards:

"We are aware that a minority of people playing Fable II over the last few days have encountered an issue where the Abbot becomes unresponsive at the beginning of Monks Quest in Oakfield. This is an isolated issue, but we are currently looking into it as a matter of priority. If you have already encountered this issue, there is unfortunately no work-around at this time, but we will keep you updated on any progress made.

"If you want to avoid this issue, when you go to the Abbot for the first time don’t run away and leave the region after he has started talking to you. Listen to him, let him finish his cut-scene, and then you are free to do what you wish.

"Some things slip through the net during development, especially when a game is the size and scope of Fable II. Again, we can only apologise for this issue, but we are doing our best. We might be silent on these boards, but we are watching and listening to you, the community, and are looking into all serious issues that are bought to our attention."

Oh dear, for such a highly-reviewed game this one sure has a lot of big-time bugs doesn’t it? It’s too bad that most of the new we’ve been reporting on this game as of late falls into the "not the kind of news you like to hear" department. So we know a fix is incoming, but we have no idea when. Rest assured though, we’ll bring you word just as soon as a patch is released to help out all you poor souls who have already been bitten by this nasty little bug.