WowAce

It seems like the threat indicator only works when your character is in combat. This is a problem for healing, because on most pulls the tanks will get into combat a few seconds before the healer does, meaning that the healer cannot see the very important threat information for these first few seconds of the pull.

Not sure if this is intended or a bug. I know it's possible to show threat when the character is out of combat, because there are other unitframe addons that do it (e.g. Vuhdo). Would be amazing if you could change it to work that way (or add it in as an option)

 What version of Grid2 and game type (classic or retail) are you using ? 2.0.14 in Classic TBC

What game client version (windows or mac) and language are you using ? Windows and English

What steps will reproduce the problem?

1. Make sure you have the threat indicator enabled

2. Join a group with another player

3. Have that player pull a mob while you are standing nearby

  
Did you try having Grid2 as the only enabled addon and everything else disabled? No

Was it working in a previous version? If yes, which was the last good one? Haven't tried in previous versions

Do you have an error log of what happened? If you don't see any errors, make sure that error reporting is enabled (`/console scriptErrors 1`) or install [BugSack](https://mods.curse.com/addons/wow/BugSack). Doesn't seem to be creating any errors.

Please provide any additional information below.

Update to 2.0.18-beta-bcc version

Thanks for accepting this as an enhancement!

I downloaded the 2.0.18 and 2.0.19 beta versions to test out what changed, but I'm not sure that it is working correctly yet. I noticed a "frequent updates" checkbox exists, but after I checked it I didn't notice anything different. The threat indicator still does not do anything when someone else in my group pulls a mob (until I am in combat myself).

The blizzard threat api is not updating the information fast enough. It seems another unit frames are checking if some enemy is targeting a player and in this case they are assuming the player has aggro.

This behaviour is programend in Grid2 in the banzai-threat status (not threat status). So you can link  banzai-threat to the same indicator than threat status.

But you must update to version 2.0.20-beta and uncheck the "Enabled only in combat" option (in the banzai-threat status configuration), because banzai-threat by default is only active when the player is in combat.

Just tested it out on 2.0.20-beta, using banzai-threat with that box unchecked. It works perfectly now! Thanks so much for changing that