Gaun's Share Effect And Hotkeys

[Bronsteijn]

After a fight in the Woedica temple when either my main was hit with confusion, or eder was charmed I got hit in battle by gaun's share. But the effect is still displayed on my character portrait. I tried to hit myself again, but once the timer ends it's still there.

 

 

I also seem to unbind my hotkeys each time I try to use a bound skill using the mouse.

Edited August 26, 2015 by Bronsteijn

[celliott]

Hello, Bronsteijn.  Can you upload a saved and output log from a game that is experiencing this issue to Dropbox?  Post a link here so I can download your files and take a closer look at the issue.  Thanks!

[Bronsteijn]

Here the link with the last output log, the save and dxdiag

 

https://www.dropbox.com/sh/o2p7jlfyw3tnnbv/AADWEEbZOHMcZJ4QbWgWZdoYa?dl=0

[celliott]

Hello again.  Thank you for the files.  By the way, the unbinding keys bug was already in our database.  Forgot to mention that and didn't want you to think I was ignoring that part.  Thanks again, I'll see what I can do!

[celliott]

So after looking through our database more thoroughly I see that someone else has also experienced this issue.  I've added your files to the bug in our database in order to hopefully help the team get to the bottom of this.  Thanks for your patience and support during this issue.

[Lucid]

Greetings from OC, CA near Irvine.

I'm experiencing the same bug.
Steal 15 seconds from each buff is on the character sheet of my PC and now I can't really play. Lol

[pi2repsion]

As a workaround, I experienced the same Gaun's Share bug on one of my party members and resolved it by removing the party member from the party and then adding him to the party again, which cleared the effect.

 

This obviously won't help if the main character is affected.

[Lucid]

That's a good workaround. Respec'ing doesn't work.

[View619]

Confirming that this bug occurs in my game as well. There's also a bug where Gaun's Share's steal attribute is carrying over to secondary weapons.

[celliott]

Hello all.  We are looking into it.  Glad to see that there is a workaround however, that is good news.  In the mean time thank you for your patience and support while we work through this issue.