EditorInspectorPlugin does not work for Debug Inspectors

[xTyrix]

Tested versions

v4.4.1.stable.official [49a5bc7b6]

System information

Windows 10 Education (but probably doesn't matter)

Issue description

Description:

Contents of EditorInspectorPlugins do not always display correctly.

More specific: Trying to call any function in an inspector opened from a Debugger Inspector on the object input into the the EditorInspectorPlugin will result in the following error (and the added control being skipped):

res://addons/myplugin/inspector.gd:8 - Invalid call function 'get_the_info' in base 'EditorDebuggerRemoteObject (SomeClass)': Attempt to call a method on a placeholder instance. Check if the script is in tool mode.

Educated guess:

There are 2 Inspectors, one "normal" one, that only displays all the @export information, one "debug" one, that displays all the information of an object. The debug inspector does not seem to correctly resolve all of its placeholders correctly.

Steps to reproduce

Steps:

1. Open and extract the MRP and start it in Godot 4.4.1.
2. Create a breakpoint at line 12 of main.gd (var x = 1 + 1) and run the game.
3. Open the Inspector of the some_class variable, by clicking on the object link in the members section of the debugger.

Result:

The Inspector opens without the added element of the plugin. In the Output section, the following error is displayed:

ERROR: res://addons/myplugin/inspector.gd:10 - Invalid call function 'get_the_info' in base 'EditorDebuggerRemoteObject (SomeClass)': Attempt to call a method on a placeholder instance. Check if the script is in tool mode.

Additional Info:

A similar Issue occurs when using some_info instead of calling get_the_info() in line 10 of inspector.gd

Minimal reproduction project (MRP)

testplugin.zip

[rsubtil]

Can confirm on v4.4.1.stable on Arch Linux

res://addons/myplugin/inspector.gd is not a @tool script indeed, but that seems like a red herring, because adding it doesn't change any behavior (and the script extends EditorInspectorPlugin, and the related tutorial doesn't specify that @tool is needed for this to work properly)

When running locally, the provided object is indeed a SomeClass. But when debugging, the object received is actually EditorDebuggerRemoteObject. More confusingly, it reports being of type SomeClass, but them attempting to use its methods doesn't work:

Peek.2025-07-01.15-34.mp4

[ydeltastar]

I can't reproduce the error in 4.5.beta.

The result in the remote inspector is expected. Note that it shows an ObjectID instead of a SomeClass reference. The running project communicates with the editor by serializing values over the network but references can't be serialized. What the remote inspector shows is a list of the of the object's properties encoded as basic types instead of the object itself. The inspector plugin has no effect because none of these fields are actually of type SomeClass.

[rsubtil]

Indeed, this looks fixed on the upcoming release (tested on v.4.5.beta.2), thank you @ydeltastar!

@xTyrix can you please test and confirm if everything works correctly for you in the new betas? If yes, please close this issue.