Advanced Runtime Logging UE5 plugin — Solution for Real-Time Logs in Editor or Shipping Builds

[FergiusTerro]

Hello, Unreal Engine community!

We are thrilled to introduce our plugin, Game Logs System (GLS), designed to revolutionize how you handle logs during development and in shipping builds. Whether you’re an indie developer or part of a large AAA studio, GLS provides a comprehensive and customizable solution for log collection, filtering, and analysis in real-time, even in final game builds.

Why Choose GLS for Your Project?

Debugging and monitoring logs is a vital part of game development, but it often becomes a time-consuming task, especially when working with large projects or across multiple platforms. GLS simplifies this by offering robust log management tools that work seamlessly in both the editor and gameplay environments, including shipping builds.

If you’ve ever felt limited by the default UE_LOG system or needed more control over your logs across different platforms, GLS is the tool you’ve been waiting for.

---

Quick Start Guide

1. To open the GLS overlay in the editor or during gameplay, press and hold Alt + Shift + G.
2. To open the overlay on a mobile device, press and hold two fingers on an empty area of the screen.
3. To open the overlay on a console, press and hold the Gamepad Special Right button.
4. Configure necessary settings in Project Settings → Plugins → Game Logs System (GLS). You can set up key bindings to open the GLS log overlay during runtime.
5. To be able to view logs in shipping builds please read about it here.

---

Key Features of Game Log System (GLS)

• On-device logs — see logs inside the game on your phone or VR headset without any PC connection.

• Debug Shipping builds in real time — see your logs directly on the device or console without ADB, console commands, or external tools.

• In-game overlay — open logs instantly during gameplay or PIE with one hotkey, no switching windows.

• Smart filtering — quickly isolate logs by category, verbosity, class, object, function, tags, network role, or PIE instance.

• GLS_LOG macros — clean structured logging with tags and context, fully available even in Shipping builds.

• Print String to GLS — Blueprint-friendly logging with custom colors and full support in Shipping builds.

• Custom Named Tabs — save separate views for different systems (AI, UI, networking, gameplay, etc.).

• Optimized & Production-ready — proven in large UE5 projects with heavy logging.

• Cross-platform support — works on PC, mobile, consoles, VR/AR.

• Session Log Files — automatic log files with configurable formats, available even in Shipping builds.

• Easy to use — Blueprint and C++ macros support (PrintStringToGLS, GLS_LOG, colors, tags).

• Persistent UI — all filters, tab layouts, and sizes are saved between sessions.

• Multiplayer-ready — isolate logs per client, role, PIE instance, or controller.

• Zero-setup — works in Development, Test, and Shipping without changing project settings.

• Log per-actor or per-object — easily isolate any object’s output during gameplay.

Useful links

• Documentation, FAQ, Changelog

• Forum feedback, Dev Blog, YouTube

• Free Demo Plugin, Example Builds (Windows, Android, Linux)

---

Why GLS Stands Out

With GLS, you get a complete, highly customizable system for managing logs across all stages of development. From its advanced filtering capabilities to the ability to collect logs in shipping builds, GLS is designed to make log management as efficient and user-friendly as possible.

Here’s why GLS is a game-changer for developers:

• Efficiency: Spend less time searching through irrelevant logs and focus on what matters most.
• Flexibility: Use advanced filtering, custom tags, and persistent settings to tailor logs to your project’s needs.
• Performance: Optimized for handling large datasets without compromising game performance.
• Cross-Platform Compatibility: Develop confidently across multiple platforms, knowing your logging system will work seamlessly everywhere.

Whether you’re working on a small indie project or a large-scale production, GLS provides the tools you need to debug efficiently, improve performance, and ultimately deliver a better product.

---

Get Game Logs System (GLS) Today!

You can purchase GLS on Fab. We offer quick user support and frequent updates to ensure the best experience across all platforms.

Contacts

• gamelogssystem@gmail.com
• Discord

---

Screenshots and Video

Video Demonstration (GLS with Lyra Game)

---

If you have any questions, feel free to ask in the comments. We’d love to hear your feedback and are always here to help!

[abuhanzala5]

GLS sounds like a game-changer for anyone dealing with complex log management, especially with the ability to view logs in shipping builds and the advanced filtering options. The cross-platform support and customizable overlay are standout features too. Definitely seems like a valuable tool for both indie and large-scale projects. I’m curious, how does the performance hold up with extremely large log volumes in a multiplayer environment? Great work on this!

[FergiusTerro]

Thank you for the kind feedback! We’ve put a lot of effort into optimizing performance, especially for multiplayer projects with large volumes of logs.

1. Optimization using UListView: We made a deliberate choice to display each log as a single element. This ensures that only the logs that fit on the screen are shown at any given time, with the rest loading as you scroll. This prevents overwhelming the interface with too many logs at once, which is crucial when handling large datasets.
2. Log processing and filtering: These processes have been optimized to minimize CPU usage. The system handles complex filtering and log management efficiently, maintaining performance even with a high number of logs.
3. Log retrieval limit per frame: We’ve set a limit of 1000 logs per frame to prevent freezing. This ensures that the overlay remains responsive and clickable, even during periods of high log volume.
4. Memory optimization: We’ve also focused on minimizing memory usage, which is especially important in multiplayer environments with large amounts of data.

So, performance holds up well even with massive log volumes in multiplayer projects. We’ve worked hard to ensure GLS runs smoothly and efficiently in all scenarios. Thanks again for your feedback!

[FergiusTerro]

We’re currently looking to expand our network and are seeking:

Collaborators – YouTube channels, content creators, or Unreal Engine experts who would be interested in showcasing GLS or collaborating on interactive demos. Our goal is to demonstrate how GLS can be used to address common development issues and improve workflows in a fun and informative way.

Testers – Unreal Engine developers who want early access to GLS and can help us refine it by providing feedback. We’re looking for testers who are working on different types of projects (single-player, multiplayer, etc.) to help us make sure the plugin performs well across a variety of use cases.

If you’re interested in collaborating with us or testing the plugin, we’d love to hear from you! We’re excited to work together to make GLS an even better tool for developers.

[FergiusTerro]

A short video demonstration of the GLS interface. An overlay with logs and filters opens on top of the Lyra Game.

[Zuriel_1]

Does the Plugin work with android builds for distribution?, My game is too big to be able to compile a debuggame/development build, Because of the 2GB/4GB limitation,
I need to test a Google release build

[FergiusTerro]

Yes, it’s possible.

The Game Logs System (GLS) plugin is compiled for all configuration modes and activates at runtime based on the settings. To enable the plugin in the shipping configuration, go to Project Settings → Plugins → Game Logs System → Enable Logs In Shipping builds in the editor.

To ensure that GLS captures logs in a distribution build, use GLS_LOG instead of UE_LOG. Unreal completely removes UE_LOG calls in shipping builds, so GLS needs to intercept logs differently.

In a shipping build, you can open the GLS overlay panel by holding two fingers on the screen of the mobile device during gameplay. This will display the logs in a tab on-screen, where you can filter them by specific categories as needed.

Additionally, make sure to set the following in your DefaultGame.ini file:

[/Script/GLS.GLSSettings]
bEnableLogsInShippingBuilds=True

These settings need to be applied when packaging the build.

[FergiusTerro]

To ensure logs are available in the shipping configurations of your game, you can add the following setting in your game’s repository:

DefaultGame.ini
[/Script/GLS.GLSSettings]
bEnableLogsInShippingBuilds=True

However, it’s essential to closely monitor the distribution builds submitted to the store.

When packaging these builds, you must include the -gls_disable build flag. This flag will disable the GLS plugin, preventing the overlay from appearing in the game and ensuring that logs are not collected, even if bEnableLogsInShippingBuilds=True is set to true.

By integrating the -gls_disable build flag into your build pipeline for final builds, you can effectively disable the overlay and log collection, ensuring compliance with the store’s requirements while still enabling logs during development and testing.

[Psychocist (foreverastudent)]

Is there any overhead for the logging nodes if GLS is disabled in particular builds?

I ask because the usual print/log has “Development Only” on the node, whereas GLS does not. Are there any performance implications for this?

[FergiusTerro]

GLS is designed with performance in mind. If GLS is disabled for a specific build (e.g., via Project Settings → Plugins → Game Logs System), all GLS subsystems remain inactive, ensuring that no GLS-specific logic or processing runs. This prevents any overhead in builds where GLS is not needed.

Additionally, the GLS_LOG macro is designed to seamlessly redirect logs to the default UE_LOG system if GLS subsystems are inactive. This ensures that log functionality remains intact while avoiding unnecessary processing by GLS.

Here’s how this is achieved:

1. Subsystem Activation Check:
   GLS subsystems are initialized only if GLS is enabled. If GLS is disabled, none of its subsystems (e.g., UGLSSubsystem) are activated, effectively bypassing all GLS-related code.

bool UGLSSubsystem::ShouldCreateSubsystem(UObject* Outer) const
{
    return FGLSUtils::IsGLSEnabled();
}

2. Macro Redirection:
   The GLS_LOG macro checks subsystem status. If GLS is inactive, it directly redirects logs to UE_LOG, ensuring minimal overhead.

#define GLS_LOG(CategoryName, Verbosity, Format, ...) \
if (FGLSUtils::IsGLSEnabled()) \
{ \
        GLSSubsystem->Log(CategoryName, Verbosity, Format, ##__VA_ARGS__); \
} 
else \
{ \
        UE_LOG(CategoryName, Verbosity, Format, ##__VA_ARGS__); \
}

Thanks for the great question!

[FergiusTerro]

Demo Version of Game Logs System (GLS) UE5 Plugin Now Available!

We’re excited to announce that a demo version of the Game Logs System (GLS) plugin is now available! After careful consideration, we decided to give users a chance to try out the plugin before purchasing. This will allow us to gather more feedback, fix any issues, and make the plugin even better for everyone.

Game Log System (GLS) Plugin is a powerful tool designed to enhance logging in Unreal Engine. It provides real-time log display directly in the game, making it easier to track and debug issues during development. GLS features intelligent filtering, customizable log categories, and an in-game overlay that allows developers to monitor logs without interrupting gameplay. It supports multiple platforms, including mobile and console, and is optimized for performance, ensuring minimal impact on frame rates even with large amounts of log data. Ideal for testing, debugging, and development, GLS simplifies log management and streamlines the debugging process.

For more details, visit our dev blog.

Here are some key details about the demo version:

• Platform: Available for Windows.
• Configurations: Works with Development and Debug builds.
• No Source Code: The demo does not include the source code.
• Installation: You need to integrate the plugin into the engine downloaded from the Epic Games Launcher. It will not work with a custom engine build compiled from source.

We believe this approach will give you a better idea of how the GLS plugin can enhance your development process. We’re looking forward to your feedback and suggestions!

Try it out and let us know what you think! Your input is invaluable, and we want to ensure GLS meets the needs of developers across different platforms.

You can download the demo version from the repository on github, please follow the instructions in readme.

[FergiusTerro]

Quick Start Guide

1. To open the GLS overlay in the editor or during gameplay, press and hold Alt + Shift + G.
2. To open the overlay on a mobile device, press and hold two fingers on an empty area of the screen.
3. To open the overlay on a console, press and hold the Gamepad Special Right button.
4. Configure necessary settings in Project Settings → Plugins → Game Logs System (GLS). You can set up key bindings to open the GLS log overlay during runtime.
5. To be able to view logs in shipping builds please read about it here.

[FergiusTerro]

Challenges of Creating a Free Demo Version of the c++ UE5 Plugin Without Source Code

Hey Unreal Developers!

We wanted to share some insights into our journey of creating a demo version of our Game Logs System (GLS) plugin for Unreal Engine. The idea was simple: offer a free, limited version to let users experience its full functionality before committing to a purchase. However, the process came with its own set of challenges that we weren’t prepared for!

If you’re interested in more details or facing similar challenges, check out our full dev blog where we dive deeper into the process.

You can try the demo version of the GLS plugin by cloning it from GitHub.

Here are some key takeaways from our experience:

Why a Demo Version?

We wanted users to try out the plugin’s full capabilities without cutting any features. The demo version is limited to Windows and Development/Debug builds, but it lets users see the plugin in action without needing to compile or access the source code.

Renaming the Plugin

To make the main and demo versions co-exist, we had to rename the plugin from GLS to GLSDemo. It sounds simple, but Unreal Engine doesn’t allow plugins with the same name to exist at once, which led to some unexpected challenges, like module conflicts and hardcoded asset references.

Asset Migration Woes

After renaming the module, all our blueprints failed to compile due to hardcoded references to the old module. We ended up migrating assets with Unreal’s Migrate tool, which saved us from manually fixing each one, but it’s clear there’s room for improvement in this area.

Demo Version Limitations

To protect our source code and control the demo, we precompiled it into a binary form. Some limitations were added:

• A shipping build message reminds users that it’s a demo version.
• GLS subsystems always return false in shipping builds.
• The demo only works for developemnt and debug configurations.

Data Type Redirects

Renaming also caused issues with data type redirects in blueprints. Even though we set up redirects, Unreal still didn’t transfer enums correctly, which we’re still trying to solve.

Key Lessons Learned

1. Keep Logic in C++ – Critical system logic should always reside in C++, not in blueprints.
2. Asset Migration – Migrating assets with the Migrate tool was key to keeping everything intact.
3. Distribution Ease – The demo version was made as plug-and-play as possible, ensuring users didn’t have to troubleshoot just to try it out.

[FergiusTerro]

Try Our UE5 Plugin: Black Friday 70% Off + Free Demo Available!

Check out GLS on Fab

Don’t forget to try the free demo and take advantage of the 70% Black Friday discount!

[general_8765]

Hello, Fergius

Before purchasing your plugin, I would like to make sure that I understand the functionality you provide. I have a few questions:

1. Can I use GLS in shipping builds for mobile devices and consoles (PS/XBOX)?
2. How much does GLS impact game performance?
3. Can I search and filter logs with complex conditions?
4. Does GLS support saving logs?
5. How quickly can I integrate GLS into my project?
6. How can I open the log overlay in a build on mobile or console?
7. How can I enable logs in shipping builds, and where will they be displayed?

Thanks

[FergiusTerro]

1. Can I use GLS in shipping builds for mobile devices and consoles (PS/XBOX)?
Yes, GLS allows you to display logs even in shipping builds, making it perfect for debugging platform-specific issues.

2. How much does GLS impact game performance?
GLS is highly optimized for minimal resource usage. Displayed data is limited to avoid slowing down the game.

3. Can I search and filter logs with complex conditions?
Absolutely! GLS supports filtering by categories, classes, objects, tags, keywords, so you can quickly find the information you need.

4. Does GLS support saving logs?
Yes, you can save logs to a file and load them later for analysis. This is especially useful for QA and debugging workflows.

5. How quickly can I integrate GLS into my project?
Integration takes only a few minutes. GLS is easily configured via project settings, and all the main features are ready to use right away. Just connect the plugin to your project and that’s it.

6. How can I open the log overlay in a build on mobile or console?
On mobile, press and hold two fingers on the screen for 1 second. On consoles, press and hold the “Special Right Options” button (this can be configured in Project Settings → Plugins → Game Logs System → Key Mapping). On Windows hold ALT + SHIFT + G.

7. How can I enable logs in shipping builds, and where will they be displayed?
To enable logs in shipping builds, make sure your project settings allow logging.

DefaultGame.ini
[/Script/GLS.GLSSettings]
bEnableLogsInShippingBuilds=True

Logs collected by GLS will be displayed in the game overlay for real-time debugging. To do this, you must use GLS_LOG instead of UE_LOG.

[FergiusTerro]

Check out the demo video of the plugin in action under real-world conditions!
Developing an Inventory with Advanced Log Filtering

Watch the full video at the link.

[StarKiller4011]

After purchasing your plugin and trying it out I am both sorely disappointed and also rather impressed.

Firstly, I was able to bring up the plugin in the editor and am very happy with what it provides however, when trying to actually use the plugin I am not only unable to open in a proper game window (selecting Launch Game from the uproject file context menu) but am also unable to use the GLS_LOG macro in my code. Either these features are non-existent or the documentation page requires a major update, perhaps even a video to show the steps to enable everything as currently the documentation site simply states to “Configure log categories, GLS_LOG macros, and filtering settings.” from the " Project Settings > Plugins > Game Logs System." but there are no settings there that mention GLS_LOG macro at all (See screenshot below).

It’s also worth noting that the discord link on the documentation page is invalid, further supporting my suspicion that the plugin itself is likely very good but the documentation is sorely lacking, the source of my disappointment as I still have not managed to get it working.

[FergiusTerro]

Hello!

Thank you so much for purchasing our plugin and providing feedback. We sincerely apologize for any difficulties you’ve encountered. Your comments are incredibly valuable to us, and we’ll make sure to address your concerns to improve the plugin further.

To open the overlay, please try holding down ALT + SHIFT + G for about one second in the PIE (Play in Editor) session or in a build. This should work without issue.

If you’d like to use the GLS_LOG macro instead of UE_LOG in your code:

1. Add the GLS module as a dependency to your module.
2. Include the following header:

#include <GLSMacroses.h>

3. Macros example: GLS_LOG(this, LogTemp, Warning, TEXT(“Test log ‘%d’ using GLS_LOG macros”), 123);

Here’s the updated link to our Discord: GameLogsSystemServer. We’re still gathering feedback and conducting beta testing to ensure the plugin becomes as polished and user-friendly as possible.

We plan to release updates every month, address user feedback, and fix any issues. We’re also working on improving the documentation and will release a more comprehensive version soon.

Additionally, we’re preparing a series of video tutorials to demonstrate how to make the plugin work effectively in all environments.

If you have any further questions or suggestions, please don’t hesitate to reach out to us on Discord — we’ll be happy to assist you and help get the plugin up and running.

Thank you for your interest in the Game Logs System (GLS)!

[FergiusTerro]

We’ve made a quick, short video for you.

In this video, learn how to open the GLS overlay and start using GLS logs to monitor and filter game logs in real-time. Perfect for debugging and testing during development!

In-Game Logging Made Easy: GLS Overlay for Shipping Builds (UE5 Plugin)