You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
13.30 caused an issue where the nameplates are not showing unless you are targeting a player. The screenshot below shows me targeting an enemy player in the background, but the foreground enemy nameplate is not active.
What is the expected behavior?
Would like it where nameplates always show unless i turn them off
What actually happened?
downloaded 13.30 and logged on. Updated all Curseforge addons
I have verfied ElvUI is up to date by checking /estatus.
I have verfied my issue doesn't exist in the ElvUI Issue Tracker.
I have not read step six and I am just clicking all boxes.
I have verfied my issue doesn't exist in the default UI.
I have disabled all addons except the three called 'ElvUI', 'ElvUI Libraries', and 'ElvUI Options' by using /edebug on? This is important in order to rule out that any of your other addons are causing the issue. If you manage to pinpoint a conflict between ElvUI and another addon, make sure you include that information.
The text was updated successfully, but these errors were encountered:
What is the issue you are having?
13.30 caused an issue where the nameplates are not showing unless you are targeting a player. The screenshot below shows me targeting an enemy player in the background, but the foreground enemy nameplate is not active.
What is the expected behavior?
Would like it where nameplates always show unless i turn them off
What actually happened?
downloaded 13.30 and logged on. Updated all Curseforge addons
Suggested Solution/Workaround
no change except chat disappeared
Errors
ElvUI Changelog & Troubleshooting
/edebug on
? This is important in order to rule out that any of your other addons are causing the issue. If you manage to pinpoint a conflict between ElvUI and another addon, make sure you include that information.The text was updated successfully, but these errors were encountered: