Bug: Unread Notification Dots Reappearing After Clearing Quests, Prestige, and Inbox
This issue
might be a
duplicate of #1839 Prestige Crest Notification Mark Persists After Clearing Notifications.
Unread Notification Dots Reappearing After Clearing Quests, Prestige, and Inbox
| Status: | Pending Moderation |
| Priority: |
High |
| Added by: |
|
| Assigned to: |
Unassigned
|
| Due date: | |
| Reported for: | |
| Actual Result: |
"Unread" red notification dots either never are cleared, despite viewing all unread items, or returns after being cleared despite no new unread items
|
| Expected Result: |
"Unread" red notification dots should clear when all items that have not been seen yet are seen, and should not return until new, unseen items have appeared.
|
| Severity: |
Cosmetic
|
| Reproducibility: |
Always
|
| Platform: |
Steam
|
| Additional Notes & Comments: |
Not set
|
Steps to Reproduce
- Log into Dead by Daylight
- Quest icon in the main and lobby menu, the "Inbox" icon on the bottom of the screen, and the Prestige Crest of any character who has unlocked any Prestige rewards will have an "unread item" red notification dot.
- Go through the Quests, clicking on each category until all "unread" red notification dots are gone from the Quest categories.
- Return to the main menu or lobby screen. The Quests "unread" red notification dot will still be present.
- Go through a character's Prestige unlocks, and check the Inbox. Both "unread" red notification dots will disappear from the menu screens once you've returned to them.
- Go into a match as any character of any role.
- Complete the match and return to the lobby. The Inbox "unread" red notification dot will have returned.
- Exit the game. Relaunch the game. All cleared Prestige Crest "unread" red notification dots will have returned.
Explanation
"New item" notification dots will not disappear/keep reappearing on Quests, Prestige unlocks, and Inbox.
Watchers
Screenshots
None
Video Clips
None
Log Files
None
No comments yet.
Loading comments...
Loading comments...
0 comments loaded
You need to join this project to comment on issues.
Join Project