Discussion for Usability Improvements (AnimationTree as Example)

[ShawnHardern]

Before opening an issue or a formal proposal, I wanted to start a discussion about usability

I've been working with the AnimationTree node in Godot and noticed that accessing its properties in GDScript and C# requires using the "parameters/" prefix. While this approach is perfectly functional, it feels somewhat unintuitive. It seems like these parameters could be more cleanly and efficiently accessed using something like an Enum for types or a function that returns the types, which would enhance readability and reduce potential errors introduced via string access.

an example of the "parameters/" access

In GDscript

# State Machine example
var state_machine = animation_tree["parameters/playback"]
state_machine.travel("SomeState")

# Transition example
animation_tree.set("parameters/Transition/transition_request", "state_2")

In C#

// State Machine example
AnimationNodeStateMachinePlayback stateMachine = (AnimationNodeStateMachinePlayback)animationTree.Get("parameters/playback");
stateMachine.Travel("SomeState");

// Transition example
animationTree.Set("parameters/Transition/transition_request", "state_2");

More info can be found on the docs

I’d love to hear what others think about this. Do you agree that there’s room for improvement here, or is there something I might be overlooking or not understanding? Additionally, I’d like to invite everyone to share any other usability issues you've encountered in Godot scripting or workflows that you think could be improved. Let’s discuss how we can make the engine even more user-friendly for developers.