UX Improvement: Make instance-level behavior property overrides clearer in the Instances panel

[PANDAKO-GitHub]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

Since v5.6.273, behavior properties can be customized per instance. While this is a great feature, it currently causes confusion among users due to subtle UI feedback:

1. Unclear visual distinction: When a behavior property is customized on an instance, the property label color only changes very subtly (from grey to white). This is almost unnoticeable to most users.
2. Lack of feature awareness: Many users are unaware that behavior properties can now be overridden at the instance level. When they modify the property on the base Object, the changes appear to be "ignored" or "broken" because the instance-level override silently takes precedence.
3. Inconsistent UI controls for resetting: The "reset to default" button currently only appears on single-line text input fields, leaving checkboxes, multiline text, and other property types without an explicit way to revert instance overrides.

As a result, users frequently report this as a bug in behaviors or extensions, assuming property editing is broken.

Steps to reproduce

The property indicated by the red arrow has been customized, but it is difficult to distinguish.

GDevelop platform

Desktop

GDevelop version

v5.6.273 or later

Platform info

Details

OS (e.g. Windows, Linux, macOS, Android, iOS)

Windows

OS Version (e.g. Windows 10, macOS 10.15)

Windows 11

Additional context

To prevent confusion and improve usability, I would like to propose the following UX enhancements:

1. Clearer distinction between Object and Instance editing: Make it obvious in the Side Panel whether the user is currently inspecting/editing an Object or an Instance.
2. Enhanced visual feedback for overridden properties: Provide a more visible visual indicator (e.g., a highlighted badge, border, icon, or clearer color contrast) for properties that have been overridden on an instance.
3. Universal "Reset to Object Default" button: Ensure that all property controls (including checkboxes, dropdowns, multiline text, etc.) have the "Reset to Object Default" option when overridden on an instance.