Expose internal variables, such as velocity, to the debugger inspector

[jitspoe]

Describe the project you are working on

Retro FPS

Describe the problem or limitation you are having in your project

I'm trying to debug some movement, but the debugger does not show the value of velocity in the inspector.

Describe the feature / enhancement and how it helps to overcome the problem or limitation

Exposing relevant values -- things like velocity that can be set in script -- to the inspector window while debugging would make things easier to debug.

Describe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams

Note how the velocity value can't be seen here by mousing over body.velocity nor can it be seen in the inspector.

Perhaps velocity is just an oversight, as things like the transform can be viewed and set here. Not sure if it makes sense to set velocity in the inspector, but maybe that's worth adding if it's more difficult to have a read-only view solution.

If this enhancement will not be used often, can it be worked around with a few lines of script?

I suppose velocity could be stored in a temporary variable, but that's not super great if you've found a rare bug and can't update the code.

Is there a reason why this should be core and not an add-on in the asset library?

Core debugger feature.

[Calinou]

Since Godot 4.0, the inspector is able to export properties as read-only, but I'm concerned about having this value displayed within the local editor inspector when it'll always be 0. (The only case where it won't be 0 is in the remote inspector.)

[jitspoe]

Wonder if it's worth adding the concept of remote-only read-only variables for cases like this.

[SaracenOne]

I think we've got an extra two bits left in the PROPERTY_USAGE_ flags. Perhaps we should add a PROPERTY_USAGE_REMOTE_ONLY flag for stuff we want to show up in the remote inspector, but not the regular inspector.

[SaracenOne]

Either that or we just make everything which doesn't have the PROPERTY_USAGE_EDITOR still show up in the remote inspector.

[jitspoe]

I'm always hesitant to add more flags when there are only a couple left. Wonder if there are any down sides to showing everything in the remote inspector. That might be the best option, as it wouldn't require a bunch of explicitly adding flags to all the properties.

[wyattbiker]

I was under impression that any property in the documentation, autocomplete or settable by the application, will show up in the inspector. Not sure why bother hiding them. In the case of velocity it is just like position.