Please check if your issue has already been reported first!

When reporting a bug, please follow the template provided, otherwise the report will be declined. The information requested is vital to allow us to correctly reproduce and then fix what you are reporting.
We have temporarily disabled The Houndmaster (Bone Chill Event queue) and Baermar Uraz's Ugly Sweater Cosmetic (all queues) due to issues affecting gameplay.

Visit the Kill Switch Master List for more information on these and other current known issues: https://forums.bhvr.com/dead-by-daylight/kb/articles/299-kill-switch-master-list
The Dead by Daylight team would like your feedback in a Player Satisfaction survey.

We encourage you to be as honest as possible in letting us know how you feel about the game. The information and answers provided are anonymous, not shared with any third-party, and will not be used for purposes other than survey analysis.

Access the survey HERE!

Error code 112!Can't get any bloodpoints

TomSasaki
TomSasaki Member Posts: 4
1
1 votes

Duplicate · Last Updated

https://forum.deadbydaylight.com/en/discussion/181298/error-112-another-111#latest please refer to this thread.

Comments

  • TomSasaki
    TomSasaki Member Posts: 4

    My game has been bugged since last month and it is still happening even the game is updated

  • Ttran
    Ttran Member Posts: 3

    Error Code 111 was supposedly fixed with the most recent patch but now there is a new error code 112 which does the same thing and kick you back out to the main loading page and again blood points and stats being lost.

  • St1ngBG
    St1ngBG Member Posts: 23

    Platform: Steam (PC )

    Description:Sync Error 112 Even after the 4.1.2 hotfix, still receiving this error.. Atleast now I don't have any lagspikes. But the error(btw not it's called 112, not 111) and the lose of progress still persist.. Hope it will be fixed asap , and the rift extended..

    Steps to reproduce (if possible): End of the match

    How often does this occur: At the end of every match

This discussion has been closed.