Setting nonexistent properties on AnimationTree fails silently

[ValiantMaverick]

Tested versions

Reproducible in Redot 26.2

System information

N/A affects all systems

Issue description

animation_tree.set("headbob_intensity", headbob_amt)
should produce an error but instead fails silently. This property does not exist. The correct code should be:
a_tree.set("parameters/headbob_intensity/blend_amount", headbob_amt)

Steps to reproduce

Call set() on any animation tree using a nonexistent property. This will fail silently.

Minimal reproduction project (MRP)

fail.zip

[GeneralProtectionFault]

Tested versions

Reproducible in Redot 26.2

System information

N/A affects all systems

Issue description

animation_tree.set("headbob_intensity", headbob_amt) should produce an error but instead fails silently. This property does not exist. The correct code should be: a_tree.set("parameters/headbob_intensity/blend_amount", headbob_amt)

Steps to reproduce

Call set() on any animation tree using a nonexistent property. This will fail silently.

Minimal reproduction project (MRP)

fail.zip

So, not saying I love this, but this appears to be functioning exactly as intended:

It looks like it checks the script, GDExtension and some other stuff too, so there's probably internal behavior that depends on this behavior :-/

[Arctis-Fireblight]

Tested versions

Reproducible in Redot 26.2

System information

N/A affects all systems

Issue description

animation_tree.set("headbob_intensity", headbob_amt) should produce an error but instead fails silently. This property does not exist. The correct code should be: a_tree.set("parameters/headbob_intensity/blend_amount", headbob_amt)

Steps to reproduce

Call set() on any animation tree using a nonexistent property. This will fail silently.

Minimal reproduction project (MRP)

fail.zip

So, not saying I love this, but this appears to be functioning exactly as intended:

It looks like it checks the script, GDExtension and some other stuff too, so there's probably internal behavior that depends on this behavior :-/

From the documentation it looks like the method is operating exactly as designed, but as a result the user has no way of knowing if it failed. The immediate fix that comes to mind would be to modify the method to return a bool or integer error code. We'll need to investigate if adding a return value breaks anything in GDExtension, but it should not impact any existing GDScript code since it is already returning void.