Post-patch - Runtime Error - "Deserialized a mod that we don't recognize"

So after today's patch and the emergency shutdown, I get this error when logging on with a character that has master-crafted items (PunctyBrewster). It shows up when the town tries to load. Other characters without crafted items load fine.

I realize you guys may still be having issues with the emergency shutdown, so I'm just reporting this here in case this requires any additional time-sensitive action on your end.

Screenshots below:

http://imgur.com/sjCoNCY
http://imgur.com/8IOeK8u

i get the same error when i try to enter my shop stash tab poe freezes and the error Shows up

same problem, cant open stash or shop, game unplayable

I'm having the same issue with my character "Lorastin" but no other character I've tried. The character has a few master-crafting mods but other characters do as well and don't have the issue. The character is standard if that could be part of the issue.

It happens to me when I select my character to log into the game with it.

Experiencing same issue, can get to character select screen, but errors out when trying to log into the game.

"

SittinDucky wrote:

i get the same error when i try to enter my shop stash tab poe freezes and the error Shows up

Yep, I can confirm the same happens here when trying to access a tab with master-crafted items.

Hopefully it gets sorted out soon.

Just before patch i died on my ranger in the Beyond league, after patch I rerolled scion, did the opening zone killed hillock, got to town opened stash and tried to view tab 3, game crashed with the same error as the OP. I relog to the scion again tested the shop, game crashed, and again, and again.

This happens to me after selecting my character and during loading into the game itself.

So far tried steam local verification. no issues.
i tried packcheck no issues.
i tried logging into other characters no issues.


Only my character Zendariah. Could this crash be related to bow issue i'm seeing? I have this equipped:

im having the same issue