To make a bug report please head over to: https://app.betahub.io/projects/pr-5642738318
Once you have signed in, on the right hand side you can use the "report bug" button to be able to fully report the bug you've encountered. Thank you.
Interested in volunteering to help moderate for the Forums? Please fill out an application here: https://dbd.game/moderator-application

Entity blocking bloodweb progression

_solaa
_solaa Member Posts: 11
in Bug Reporting

SUMMARY OF THE ISSUE: In the photo below you can see where the entity has bugged out my level progression.

You can see where the sacrificial ward was closed off by the entity, but further along the path you see the butterfly tape purchased. This is clearly a bug, as the sacrificial ward would need to be purchased to continue up that path to the butterfly tap and finally the crisp amaranth that is bugged out, keeping me from finishing the level. My survivors blood web is stuck like this, and has been for a few days.

This error occurred when clicking the autobuy button to level up. When clicking on the autobuy button, my screen locks up. I have to hover over the "tome eye" and go to the challenges, then back to this screen before the game will allow me to ready up.

Results: I am forever stuck at p94 until a fix is found. I cannot purchase anymore items/perks from the blood web until this is fixed. luckily i have all the perks i want, but any future perks that come out, will be not accessible to this survivor. And i cannot purchase anymore add-ons or offerings.

image.png

Thank you to developers who have opened my ticket and responded saying that they are aware, but there is unfortunately no timeline for a fix. Ive run into quite a few people on reddit who are experiencing this exact issue, and im really hoping you guys can keep this post active to allow people to engage, report the bug, and stay connected for future updates that will resolve this for us.

PLATFORM: Steam, PC

VIDEO: Screenshot provided above.

PLAYER LOGS:

2
Up
2 votes

Under Review · Last Updated

Thank you for taking the time to report this issue, we are forwarding this to the team for their review

Comments

  • _solaa
    _solaa Member Posts: 11

    Update: Not sure if this is a fix for everyone, or what steps within the scenario that I am going to explain truly fixed the bug. But hopefully this information can help anybody struggling with this.

    I opened a ticket with the dead by daylight support and reported the issue. It took a couple days and then devs mentioned that they found a fix. After being told they found a fix, i logged in to find that the bug was still happening on this survivor. Trial and error, it happens! (reading further will explain why this might be important)

    After their attempt to fix the bug I decided to crossplay link my accounts to another platform that i own, just to see what would happen. I linked both accounts and made sure to clink the "sync" button on their website, in my account settings, then logging in. Once i did this, the bug was totally fixed.

    Im not sure which step, or maybe all steps contributed to the bug fix, but i hope this info can help you out. The devs are extremely helpful and are very aware of this current bug.

    If you're on pc and dont have another platform, try linking to epic if you happen to have the game there. or for testers, just try resyncing your data from your linked accounts online, see what happens. Wonder if that step was the true solution.

    Thanks!

  • ILCENTAURO
    ILCENTAURO Member Posts: 2

    hello I have the same problem with my meg I get stucked at lvl 33 forever but I only have this platform, so I'm unable to sync this game….. what can I do ?

  • _solaa
    _solaa Member Posts: 11
    edited May 27

    Did you get it fixed? this is a late reply, sorry. Not sure if this will fix it, but try going to your crossplay connections on your bhvr account and refresh the data for your platform. Also verify the files of the game on whatever platform youre on. The first option is what seemed to work for me.

    If this doesn't work, open up a ticket with support. They were pretty quick to help me and understood how annoying it was. goodluck