The Dead by Daylight team would like your feedback in a Player Satisfaction survey! https://dbd.game/4dbgMEM

Achieve Challenge "Exposed Target" with Myers

Sharpefern
Sharpefern Member Posts: 422
in Bug Reporting

Achieve challenge exposed target did not count a single hit while I was playing myers and hit the survivors in tier III which occurred around 6 times

14
Up
14 votes

Pending · Last Updated

Comments

  • LadyOfEve
    LadyOfEve Member Posts: 1

    Same issue, xbox player if that matters

  • TheShakenCondor
    TheShakenCondor Member Posts: 13

    Same issue today. I had one hit left of the challenge so paired it with a Myres daily. Still had one hit left after the match while hitting the majority of hits in tier 3

  • Aneurysm
    Aneurysm Member Posts: 5,270

    Same. Started challenge, played a game of Myers, hit 5-6 survivors while in tier 3, zero progress made.

    PC- steam


    Map was dead dawg saloon

    Perks were Lethal persuer, hex: plaything, eruption, monitor & abuse

  • kenco12
    kenco12 Member Posts: 3

    PC- Steam

    Character- Meyers

    Loadout- Play with your Food, Ruin, Corrupt Intervention, Tinkerer,

    5 Year Cake, Judith's Journal, J. Myers Memorial

    Map- Mount Ormond Resort

  • Miszmii
    Miszmii Member Posts: 30

    Same here. Even used infinite tier 3 for the challenge, so got 10 downs while exposed. Didn't count.

  • LoolaHoop87
    LoolaHoop87 Member Posts: 45

    I tried it today with Myers, it didn't count either. Tried it with GF immediately after and it worked.

  • GoshJosh
    GoshJosh Member Posts: 4,992

    Still no acknowledgment or fix on this?

  • ShyPirate
    ShyPirate Member Posts: 377

    Apparently still not fixed. Played Myers just now with the Fragrant Tuft of Hair. 9 instant downs and no progress toward the challenge.

  • GoshJosh
    GoshJosh Member Posts: 4,992

    @MandyTalk , this bug is weeks old, been reported a few times. Could we please get an acknowledgment on it?

  • GoshJosh
    GoshJosh Member Posts: 4,992

    Still no update on if this is acknowledged or fixed?