Input: Change the default deadzone value for new actions from 0.5 to 0.2

[rptfrg]

This changes the default deadzone value for new actions from 0.5 to 0.2 as discussed in godotengine/godot-proposals#7069.

---

I have failed to rebase my previous year old PR, (#80299) so I pressed the "Sync" button in the Github's UI, not knowing it what it would do 😊👍️
Turns out it erases all your changes with no warning and without any way to undo what you have done.

Please check the changes I've recreated and sorry for the mess.

Bugsquad edit:

• Closes Decrease the default deadzone value for actions to better match real world use cases godot-proposals#7069

[AThousandShips]

Once those minor details are fixed this looks good to me!

[Sauermann]

The reasoning for changing the default value, as discussed in the linked proposal, makes sense to me.

Can you please double check, if it would make sense to make additional adjustments to the following location in the code base:

godot/modules/gdscript/tests/scripts/project.godot

Line 15 in 506d6e4

"deadzone": 0.5,

[rptfrg]

I thought this could be left as it is, but I guess I could change that to the new default value (0.2) for the consistency's sake? I am not sure what to do with it.

[HolonProduction]

The action is only used for autocompletion tests at the moment, the dead zone isn't relevant there so changing it to the default makes sense to me.

[Sauermann]

From the input side, this looks good.

[akien-mga]

Thanks! And congrats for your first merged Godot contribution 🎉

[wareya]

Did this PR only apply to new input actions, or did it apply to the built-in UI actions as well? Diagnostic posts in #98982 seem to imply that it applies to the built-in UI actions too, which would result in these changes causing this issue: #103360

[Calinou]

Did this PR only apply to new input actions, or did it apply to the built-in UI actions as well? Diagnostic posts in #98982 seem to imply that it applies to the built-in UI actions too, which would result in these changes causing this issue: #103360

It applies to built-in actions too, as these are often used by people for gameplay logic during prototyping.

Built-in actions are not saved to project.godot unless you override them, so if we change it back to 0.5, it shouldn't affect custom actions.

Ideally, I think we should use custom deadzone handling for UI logic where it always uses a separate, fixed deadzone (e.g. as a project setting). This may be difficult to do though, so maybe reverting the deadzone for built-in actions only is preferable, even if it hurts the prototyping experience for users who don't create new actions (or people using the CharacterBody script template).