Skip to content

Diagnostics

Pro Diagnostics

The Diagnostics Panel collects tag issues, usage data, redirect information, and custom issues generated by the Behavior System.

Window | J2 Tags | Diagnostics

J2 Tags Diagnostics panel

QuestionCategory
Which used tags are not defined?Not Defined
Which defined tags have no references?Unused Tags
Where are old redirect names still used?Redirects
Is a tag used on the wrong target type?Scope Mismatch
Where is each tag referenced?Usage
What custom problems did behaviors report?Custom Issues
Are there structural problems in TagSets or behaviors?General Issues
CategoryMeaning
General IssuesNaming, behavior diagnostics, and structural issues that do not fit a more specific category.
Custom IssuesUser-defined issues produced by behavior rules or diagnostics.
Scope MismatchTag is used on Actor, Component, or Asset while its scope does not allow that target.
Not DefinedUsage without a Quick Tag or TagSet definition.
Unused TagsDefined tags without found references.
UsageRead-only overview of where tags are used.
RedirectsRedirect entries and redirect usage statistics.

The Scan menu can update the usage cache before diagnostics are refreshed.

ActionUse when
Scan Current LevelYou only need fresh data for the currently loaded level.
Scan Full ProjectYou need project-wide data, including level objects and Asset Tags.
Restrict Usage To Current LevelYou want usage diagnostics to show only references from the loaded editor level.
RefreshYou want to rebuild the panel from current cache data without starting a new scan.
ActionPurpose
Ignore / Show IgnoredHide accepted issues and bring them back when needed.
Open TagOpens the tag in the Tag Manager when it has a definition.
View ReferencesOpens the references for the selected usage or issue.
Resolve TagsConverts not-defined issue tags into Quick Tags or TagSet Tags.
Cleanup RedirectsRemoves unused redirects or prepares redirect cleanup.
Cleanup IssuesClears behavior-generated custom issues when appropriate.

Review diagnostics safely

  1. Make sure the Usage Database and tracking settings are configured.
  2. Run Scan Current Level or Scan Full Project.
  3. Review Not Defined, Scope Mismatch, and Redirects first.
  4. Select a message to inspect details and suggested action.
  5. Open references before applying cleanup.
  6. Run cleanup or migration actions only after confirming the intended source of truth.

Cleanup actions can change many assets or level objects. Before large cleanups, decide which source is authoritative: Quick Tags, TagSets, or intentionally accepted local tags.