When we released mods in version 1.1.0, we opened up the game to be expanded in a million different, creative ways.
Since mods can change just about everything about the game, we separate modders into a separate “realm”, where mods won’t allow you to do things like click a button to unlock all of Okri’s Challenges. That would be a bit unfair.
However, in order to make sure that mods weren’t able to change player data on our backend, we had to rewrite some of our network code to add extra layers of security.
The infamous backend error 1342 that kept popping up after 1.1.0, was a direct result of that rewrite.
This patch - 1.1.0.3, is a small patch which aims to resolve these backend errors.
Since the release of 1.1.0, we’ve also seen outages from both our backend hosting company, and Steam itself. We’re truly sorry about these issues impacting your games - we just want you to have fun killing rats.
There are still a few known issues with Challenges since 1.1.0 which we’re planning to patch this week.
Fixes & Tweaks
Optimised creation/opening of chest and crafting requests to the backend to avoid 1342 errors and cases where trusted players were meeting with a “denied” response upon manipulating their inventories.
Great stuff. However, does this still mean we can get a 1342 error when finishing a map? I no longer care for crashing in the Keep but me and my friends are always paranoid about having our runs completely erased.
I received a steam connection error via vt2 last night. We were close to the end of a level. VT2 prompted for me to quit or retry. Retry did not return vt2 to the active session. The need for a pat on the head increasing…