New patch bug!

There was a 100KB patch released to fix my specific error message at 2:43PM GMT+10 13/03/2013. That patch worked for me, so I would hazard a guess that other players that received the same error message will also no longer experience it.

"

error message wrote:

---------------------------
Exception
---------------------------
"Audio/Sound Effects/MonsterSounds/Bandits/bandits/bow_bandit_attack15.ogg": Decoded no data
---------------------------
OK
---------------------------

same here, entering docks => crash!!!

Crashes on entering Lab. Syncing didn't help...

reddit thread on the issue

people are dying left and right to this on hardcore.... I had it happen to me but I managed to survive cause I was on windowed mode.

Same problem for me, fortunately I'm in SC :

http://www.pathofexile.com/forum/view-thread/253440

I didn't change anything before the patch, it's just a bug brought by the patch.

when the game comes out of open beta will this policy of no HC restores be changed reconsidered?

i died on HC at 74 at docks, i might play again when the game comes out of open beta if theres going to be at least an appeal process for deaths caused by game breaking errors.

GGG, Chris, other mods/devs:

We all know this is a beta, and we love to be able to play this beta with you guys and make it better. But the recent patches have all resulted in an immediate hotfix patch for problems introduced by the new patch.

Last night this faulty patch actualy killed quite some people, be it HC or SC.

With the last two(3?) hotfixes in mind I am under the impression that the release strategy should be changed. There are a couple solutions that could be used that I could come up with in 5 minutes:

- When introducing a new patch, do not sneek in last minute additions that have not been tested by the alpha tester team. I am aware that this is probably already being done. but! the last patches show that this is not done imo... A generic error that pops up while loading a map, that keeps the map loading until you click it away could have been spotted by someone that doesn't even play the game. Reason for me to believe there was a last minute rush that was not taken through the appropriate testing channels. Although, yes, we like new content, we do like them to be safe when they are launched. Only one way to do this... testing...

- Automated client testing: Set up a test that launches the game and enters a map and let it watch for generic errors, these errors are easy to find because NONE should be raised on a production release! Start with these two main functions and expand where needed.

- Delay patches for HC mode by 1 hour from SC patches. Us SC folk don't mind dying as much as a HC player, USE THAT... we only lose some exp and feel sad that we have gained +1 on /deaths but for a HC player it means starting to doubt if you'll ever want to start another tune again...

Use the SC players as test subjects, they have nothing to lose. Every time you want to release something give it to SC players one hour before so you can filter out the stuff that could go horribly wrong for a HC player. I can imagine that this might be hard to setup with the current release strategy and infrastructure (SC/HC probably need to be patched at the same time). But spending time and resourced on such a function would definitely not be wasted!

Last but not least, change the waypoints to not have mobs next to them! Make an invisible barrier that disrupts their patching functions, that way they won't be able to attack anyone. Of course this would have only stopped the previous bug and it would be better to tackle the under-laying problem. Patches themselves.


Please chris, devs read this post!

cheers

"

VRShiva wrote:

- Delay patches for HC mode by 1 hour from SC patches. Us SC folk don't mind dying as much as a HC player, USE THAT... we only lose some exp and feel sad that we have gained +1 on /deaths but for a HC player it means starting to doubt if you'll ever want to start another tune again...

as a person who lost his 76 HC Ranger to this bug, i feel as though this is actually a good idea.

Not sure how easy this would be to implement but still a good idea.

So now the problem isn't resolved yet, hope they will find a solution soon because it's very boring . . .

yeah there's no legitimate way to tell that hardcore players died by clicking on a wp.


i even clicked a fresh one, that's how long it took suspended for my toon to die.