LOGS VIEWER
All your ALS logs can be accessed in Runtime / Editor. Filter by instance / Play session / Context / Severity or by manual search. Track and differentiate logs of different worlds or instances easily.
🔓 How to Open
Shortcut: Press [Ctrl + Shift + L] at any time to open/close the logs viewer. Configurable in plugin settings.
Click [X] button to close the viewer.
⚠️ Important Notes:-
You can disable Override Mouse & Input Mode in ALS Plugin Settings to handle input focus manually when opening or closing the inspector.
For Android Platforms or non-game projects use the Open and Close Helper functions to Handle input configurations accordingly.
You can adjust the sizeboxes of ALS_LogsViewer based on the device you are working on for better control.
You can enable and use ALS_LogsViewer for Shipping builds in plugin settings with caution.
If you are packaging your project with CookOnlyMaps then Include this path to enable this in builds Go to Project Settings → Packaging → Additional Asset Directories to Cook. Add this path: /AdvancedLoggingSystem/UMG
2️⃣ Overview
Instance ID
Shows each PIE or packaged instance (Server, Client #1, etc.).
Session ID
A new session number is generated every time you hit Play—ideal for A/B testing.
Context
Filter logs by the Blueprint, Actor, or Component that emitted them.
Severity
Quickly drill down to Info, Warning, or Error only.
Search
Case‑insensitive, supports partial strings and phrases.
Group Messages
Collapse identical entries into a single row with count & timestamps.
Sort Order
Toggle newest → oldest or the reverse.
3️⃣ Multiplayer Support
Auto-Lists every running game windows as Instance ID (Standalone, Server, Client #1)
Session ID gets created for each Play session, Keeps every game test logs intact.
Perfect for side‑by‑side comparison of Server vs. Client output.
4️⃣ Message Grouping
Group messages by its count triggered and timeline or Ungroup identical messages. The row shows first timestamp → last timestamp and an occurrence counter.
Great for spammy events that fire every tick—keeps the list readable.
Disable Group Messages to expand the full stack.
⚠️ Ungrouping thousands of logs triggers a warning—entries are still virtualised, so memory impact is minimal.
5️⃣ Search, Filter & Sorting
Search Box – live string filtering, case‑insensitive.
Context / Severity Filters – stackable drop‑downs for pinpoint views.
Sort Order – flip between chronological and reverse‑chronological.
Engine noise is gone—only ALS‑originated logs appear here.
6️⃣ File Logging Location
All sessions are archived under:
<Project>/Saved/Logs/ALS/Configure the folder in Project Settings → ALS → Logs Directory.
7️⃣ View Logs Post‑Game
Even after the game ends you can open the Logs Viewer inside the editor to analyse what happened. Old sessions are auto‑archived, so nothing gets overwritten.
8️⃣ File Message Only
⚠️ You can silently file log messages using these functions. This will neither show on screen or create output logs.
✅ Features Summary
Works in PIE, packaged dev/test, multiplayer, and multi‑instance setups.
Logs are context‑tagged, timestamped, session aware, and group aware.
File logging is auto‑sorted by Session ID and Instance ID.
Seamless integration with:
ALS Enhanced Print String Node
ALS C++ Debug Macros
ALS BT Print Task / Service
ALS Runtime Property Inspector
Behaviour Tree and Property Inspector suppress duplicate logs. C++ macros and nodes emit every call so you never miss a message.
Last updated