🛈 Announcement
Greetings! The Division forums are now archived and accessible in read-only mode, please go to the new platform to discuss the game
  1. #1

    [BUG]The Division 2 - Glitched Exclamation Mark in Inventory

    I exited a Conflict match and now I have a exclamation mark stuck in my inventory I’ve looked through literally everything and cant get rid of it. Unfortunately I’m very OCD about this.
    Share this post

  2. #2
    Ubi-Mark.'s Avatar Ubisoft Support Staff
    Join Date
    Nov 2017
    Location
    Base of Operation
    Posts
    6,899
    Hekllo ETERNALxDARKNES,

    Sorry to hear that. I've reported the issue regarding exclamation mark today to the development team. Could you please provide us with a short video of this occurring? Once received, I'll be able to add it to the report. Apologies for any inconvenience caused.
    Share this post

  3. #3
    I also have this problem. The exclamation mark has been there for about a month or so and is very very annoying.
    Ive checked every possible place for any new inventory items and there are none.
    Share this post

  4. #4
    Ubi-Redbeard's Avatar Ubisoft Support Staff
    Join Date
    Mar 2017
    Posts
    7,279
    Originally Posted by markenbach Go to original post
    I also have this problem. The exclamation mark has been there for about a month or so and is very very annoying.
    Ive checked every possible place for any new inventory items and there are none.
    Can you remember roughly when you first noticed this issue?

    Was it after completing a certain mission or did it occur after picking up some loot, for example?
    Share this post

  5. #5
    Ubi-Redbeard - I can answer your question. I made a second character and when I exited the DZ East tutorial for opening up DZ East the exclamation marks appeared on the Character and Inventory sections of the main screen. Once this occurs those exclamation marks can never be cleared. Something about the DZ East tutorial mission glitches the character forever or until Ubisoft fixes this bug.
     1 people found this helpful
    Share this post