forums | blogs | polls | tutorials | downloads | rules | help
Home-> forums-> Technical support-> DS2 & BW Technical Support

"This quest has already been completed by someone else and cannot be completed in this session."

Submitted by Farigiss on Wed, 2017-01-04 14:08
AttachmentSize
Image icon Dungeon Siege II Screen - 0024.png828.61 KB

I've been playing the Steam version of DS2 and I used this guide on the Steam forums to unlock Broken World. I've not modified the game in any other way.

I've completed the original DS2 map and just started on Broken World with the same party.
The problem is that all the quests in the quest log show this error: "This quest has already been completed by someone else and cannot be completed in this session."
This error did not occur in the original map. This is the first time I've set foot in Broken World with this party and I haven't played these characters in multiplayer.

Does anyone know how to fix this?

Thanks for your time Smile

forums: 
DS2 & BW Technical Support
»
Submitted by bare_elf on Wed, 2017-01-04 15:03

Farigiss I am not sure because I currently do not have the steam version installed. But I have seen a similar issue when starting Broken World (retail version) with a premade character and not playing the DS 2 map to the end at least once. I hope some member who is using the steam version will have the answer for you.

Elf
»
Submitted by Farigiss on Wed, 2017-01-04 15:56

Is there perhaps some kind of editor I can use to reset quest progress?
»
Submitted by ghastley on Wed, 2017-01-04 17:14

That's a multi-player-only message, so I suspect you just started BW in the wrong mode.
»
Submitted by Farigiss on Wed, 2017-01-04 17:23

ghastley wrote:
That's a multi-player-only message, so I suspect you just started BW in the wrong mode.

I wish it was that simple Sad

As you can see I have 4 party members which is not even possible in multiplayer as far as I know. I have obviously restarted the game several times as well and that didn't fix it.

I have found one other person with a similar issue here, so I guess I'm not alone. Too bad there is no solution there either.
»