Blueprint Debugging
This document explains how to use a breakpoint to debug Blueprint logic in a remote Unreal Editor session.
Video Demonstration
Check timestamp (2:39-3:25)
Debugging with a Breakpoint
If your Blueprint logic is not executing as expected, you can use the Blueprint Debugger to trace the execution flow on the server.
In the remote editor session streaming in your browser, open the Level Blueprint (or the Blueprint you wish to debug).
Locate the node where you suspect the issue might be. For this example, we'll use the Print String node.
Figure 1. Locate the Node
If you press 1 it’ll print “Hello” on the screen
Figure 2. Press 1
Right-click on the Print String node and select Add Breakpoint from the context menu. A solid red octagon icon will appear on the node, indicating that the breakpoint is active.
Return to the main editor viewport and trigger the event. In this case, press the 1 key.
Expected Result: The remote editor session will pause, and the view will automatically switch to the Blueprint's Event Graph. A large red arrow will point to the node with the breakpoint, showing that the program's execution has paused at that exact point.
Figure 3. Remote Editor Session Paused
This confirms that the keypress is being detected and the Blueprint logic is running up to that point. You can now hover your mouse over the node's input and output pins to inspect the data values at that moment in time, helping you identify the source of the problem.
How to test in remote editor streaming
Remote Control Unreal Editor
How to do blueprint debugging incase something in not working
Need help?
🛠️ Contact our Support Team
💬 Join the Community on Discord
Follow us on:
Facebook | GitHub | LinkedIn | YouTube