New patch bug!

all valid questions and suggestions made in this post have been ignored lol,

Only thing GGG addressed was the patch problem itself, all problems caused as a result of this patchissue... brushed under the carpet in the hope time will take it away.

Maybe there is nothing they want/can do about it, still doesnt mean that they shouldn't address/express their apologies to the hundred's of people screwed over by it, most of all the HC players who time has been wasted by them being cheated out of their characters...

The silence on the damage the patch caused is what stings the majority of people the most, but "its just beta, we must deal with it" lol.

The worst is they deployed the 0.10.3 patch to fix some bugs (3 I think) and there isn't a correction for the most important bug of all.

I have a quest taking place at the docks (normal), so I just can't play and continue the adventure. Ok I farm other zones, but at this rate I'll be lvl 45 without killing the general at barracks . . .

Please GGG react you're not blizzard !

"

Maccattack91 wrote:

all valid questions and suggestions made in this post have been ignored lol,

Only thing GGG addressed was the patch problem itself, all problems caused as a result of this patchissue... brushed under the carpet in the hope time will take it away.

Maybe there is nothing they want/can do about it, still doesnt mean that they shouldn't address/express their apologies to the hundred's of people screwed over by it, most of all the HC players who time has been wasted by them being cheated out of their characters...

The silence on the damage the patch caused is what stings the majority of people the most, but "its just beta, we must deal with it" lol.

It's a beta, if you don't want bugs then wait for the game to leave beta status. There is no reason for them to be apologetic about bugs because that's what's expected to be found during a beta.

"It's a beta, if you don't want bugs then wait for the game to leave beta status. There is no reason for them to be apologetic about bugs because that's what's expected to be found during a beta."

This is not some crappy bug you find now and then, this is making the game unplayable for a big chunk of the community. Hence, it should be prioritized.
Not to mention all the lost characters in HC. Most of the people are stuck in D3 simulation now, grinding the same (safe from crash) areas over and over again (I am talking about HC here, SC has nothing to lose on crash).
I personally crash on entering Lab, so my high level character is chilling for days now.
So I've started leveling alts. And now i am stuck in a2, since i crash on entering Chamber of Sins. Another alt is stuck in a3 normal since I cant enter docks.
I know it's still beta, but I was expecting at least a response from devs about this issue.

So am I right for reading these last posts as "the bug is still here" personally I havn't gotten any errors anymore.

If people are still getting those errors I would advice to open a new bug report or send one of the mod teams a message about it.

Ok I tried 1h ago and it works.

To remove the auto crash dock and sin bug, you just have to unistall your game and reload/install it. I don't know how and why but it works perfectly that's all I know . . .

http://www.pathofexile.com/forum/view-thread/253440/page/2/#p2207252

It's the most important that the game works again, but I don't congratulate GGG for the silence around this problem.

Hope to help you guys, have fun again in poe !

"

Dedisdead wrote:

Ok I tried 1h ago and it works.

To remove the auto crash dock and sin bug, you just have to unistall your game and reload/install it. I don't know how and why but it works perfectly that's all I know . . .

http://www.pathofexile.com/forum/view-thread/253440/page/2/#p2207252

It's the most important that the game works again, but I don't congratulate GGG for the silence around this problem.

Hope to help you guys, have fun again in poe !

I reported to them the steps to recreate my version of this bug and the error message received. They fixed the issue within 2 hours with a new small patch. I hardly call that sitting idle.