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.
http://dbd.game/killswitch
Xbox Series X-Gatekeeper emblem not calculating points correctly
Step 1 : Boot the game
Step 2 : Play as any killer in a public match (bug encountered with Nemesis, Mastermind, Cannibal and Singularity so far).
Step 3 : Play the game normally (for more certainty of extending the game beyond 9 minutes, which should grant significant points according to the emblem descriptions, use generator slowdown perks such as Pain Resonance and/or Oppression).
Step 4 : After the game, notice how the "Gatekeeper" category has very little to no points, making pipping almost impossible at Gold/Iridescent Grade and very difficult even in lower Grades.
Additional information
- Frequency of the issue: Not 100% reliable, a game ending in a "Merciless Killer" rank seems to be exempt from this bug, forcing a full victory to avoid losing potentially 25% of (the maximum) possible emblem points.
- Slowdown perks used were Pain Resonance and Oppression.
- Picture of Post-Game Emblem attached
- In the game from the image, 2 Survivors died, one of them having purposefully sped up his 2nd hook phase, 2 escaped (both of them were on 2nd hook, one disconnected prior to getting hooked for the first time (not certain if this makes a difference)), the Survivors were quick to heal injuries and often used the basement of the school in Badham Preschool alongside Boil Over to essentially make hooking nigh-impossible and forcing me to either let them downed or have them wiggle out (which made me lose a lot of points in the Malicious Emblem category through them recovering).
- Side-note: wasn't there supposed to be a hook down there if Basement wasn't in the school to prevent this exact situation?
Comments
-
Update: Still an issue after update 8.1.2
I frequently get 0 points, or barely reach Bronze, in Gatekeeper category after very long games, no matter the amount of sacrifices.
Bug now tested to happen on any Killer.
0 -
Update: still an issue after 8.2.0 and still not in the known issues despite several threads about it, some of which have logs and videos.
0