Health Checker
Health Checker is a diagnostic tool that analyzes the currently open map and automatically detects factors that may lead to performance degradation or quality issues.
It primarily targets the following elements, focusing on areas that commonly cause problems.
The analysis results are presented as scores and graphs, allowing you to intuitively identify potential issues.
Note: Health Checker does not modify your project automatically — it is strictly a diagnostic tool.
How to Run a Check
-
Install the plugin.
-
Enable Health Checker in your project and restart the editor.
-
Open the map you want to analyze.
-
Click the heart icon added to the Play toolbar and select “Health Checker.”
-
Reports will be generated in HTML, MapCheck, and Log formats.
How to Review Results
-
Start by checking the HTML report to get an overview of the map’s issues.
-
Once you identify the areas to fix, review the details in MapCheck or the Output Log.
- The details of the warnings are also output to the log.
Tips
Too many items make it hard to see elements clearly
Zoom in on the HTML report.
You can also limit the number of displayed elements, but note that the oldest entries are trimmed first.
Graphs with few elements appear too narrow
Click on the graph elements to toggle them on or off.
Hide those with the largest share to improve readability.
Cannot copy error messages from MapCheck
Use Ctrl+C to copy text.
Since MapCheck doesn’t support search, use the Output Log instead when searching.
Cannot jump to actors in MapCheck
In Health Checker Settings, disable Unload Levels After Check to keep loaded actors in the level after the check.
However, note that saving the level in this state may alter level visualization settings, so use it with caution.
Plugin Usage
Although distributed as an engine plugin, Health Checker can also function as a game plugin.
Blueprint Usage
You can also execute Health Checker from Blueprints using:
UHealthCheckerEditorSubsystem::RunHealthChecker()
About the Details Link
By default, detailed links use Google’s search AI.
The search address is stored in HealthChecker/Resources/DocumentURL.txt
.
If you prefer to switch to another AI or search engine, replace the URL in this file.
Settings Overview
Unload Levels After Check
When disabled, actors loaded during the check are not destroyed afterward.
If this option is not enabled, component links will not function correctly, making investigation difficult.
Be aware that saving the level with this setting enabled may alter its initial state, so the default is OFF.
Even if saved accidentally, it only affects editor-level visualization and does not impact runtime behavior.
Ignore Editor Only Actors and Components
Ignore EditorOnly actors and components. Enabled by default.
Post to Map Check
Controls whether results are posted to MapCheck.
Post to Log
Controls whether results are posted to the Output Log.
Open Report when Finished
Automatically opens the HTML report after the check is completed.
Open MapCheck when Finished
Automatically opens MapCheck after the check is completed.
Use UserName in Report
Includes the PC name and user name in the report.
Useful for team sharing or automated workflows.
Add Engine Version to Search Hints
Adds the engine version to the search query when opening detailed links.
This helps retrieve version-specific information but may increase the likelihood of AI hallucinations, so adjust depending on your environment.
Report Actor Categories
Reports are categorized by actor type.
You can disable unnecessary categories to make the report easier to read.
Planned Future Updates
Future updates will extend Health Checker to include runtime performance diagnostics.
-
Health checks during runtime (PIE)
-
URO (Update Rate Optimization) analysis
-
SignificanceManager efficiency evaluation
-
Culling load detection
-
Raycast usage analysis
-
LumenCard rendering load analysis
-
Chaos physics performance diagnostics
-
Niagara effect performance analysis