v0.6.4

✨ New Features

Editor Updater Confirmation Step

As the addon gets more refined over time, leading to potential breaking changes, the updater now requires an extra step to be completed before it can be triggered for major or minor releases. The only practical difference is an added dropdown menu, where you have to select Yes instead of the default No option, which will then make the update button appear. This is to give a bit of friction and to give some thought before pressing the big green Update button and risk causing project side effects.

This will, however, not occur for patch or hotfix releases.

Major and Minor Releases	Patch & Hotfix Releases

Term Reference Examples:

Major Release: v0.8 -> v1.0
Minor Release: v0.6 -> v0.7
Patch Release: v0.6.4 -> v0.6.5
Hot Fix Release: v0.6.4 -> v0.6.4.1

Editor Updater Project Settings

Tip

You may have to enable Advanced Settings in the top right-hand corner for the settings to appear in the panel. Alternatively, you can search for them.

Options to now disable the updater to two different levels (more below) have been added to the Project Settings.
This is meant to better support released projects where no further work is happening, but where the project is occasionally being opened.
💡 Thanks to @lunarcloud for the suggestion (#203)

Enable Updater	Show New Release Info on Editor Launch in Output
If enabled, it will trigger the updater dialogue when the Godot project opens and show an updater button in the addon's bottom editor panel. Important If you are using the addon by having forked the project, then the updater window will now always be disabled. This is to prevent an update from overriding your own changes. Pulling and merging the main branch should be done instead.	If Enable Updater is disabled or using a forked version of the project, this will appear by default in the Output tab within the Godot editor on startup. Like with the Editor Updater, this too can be disabled from the Project Settings.

🛠️ Changes & Improvements

• Added support for rotational tweening in 2D scenes. (#225)
  • 💡 Thanks to ZT2wo for the suggestion. (#214)

🐛 Fixes

• Resolved an issue where moving between multiple Framed Follow PCams would stack the dead zone fields in the viewport. (#226)
  • 🔍 Thanks @RichardStolp for the report (#208)
• Resolved an issue with setting various SpringArm3D properties such as collision_mask didn't get triggered during runtime. (#224)
  • 🔍 Thanks @eliaskowitz for the report (#222)