The Debugger panel and C# limits

An error does not imply a pause

Run the project from the editor and open the bottom Debugger panel. Find the first error of the current run: message, source file, line and available stack. PushError reports an error without itself stopping gameplay logic.

A C# message with a .cs source path is transmitted. This does not prove the built-in panel can set managed breakpoints, show every C# local or evaluate arbitrary expressions in a paused CLR frame. Interactive locals/members functions and parts of CSharpLanguage's stack interface are unfinished in this version.

Inspect a running object

The check level creates this object:

using Reckfell;

public partial class DebugInspectionTarget : Entity
{
    [Export] public int DiagnosticToken { get; set; } = 424242;
}

While it runs, switch to the remote tree, select InspectionTarget and check DiagnosticToken=424242. This is the running instance's value rather than only the source property in the open project. After shutdown its instance ID no longer identifies a live object; an old selection does not prove current state.

Remote inspection receives supported engine-object properties, including exported C# properties. It does not automatically expose all fields of ordinary .NET objects or replace managed-heap inspection.

If data is missing

Check that the application is running, the correct project is launched and remote diagnostics are enabled. A standalone launch without a connection does not automatically create an editor session. For a C# source-line pause, separately configure managed debugging and verify matching binaries, PDBs and sources.

Output and errors · Preserve logs