Deploying to published from @ godotengine/godot-website@d8cbaecac1 🚀

atom.xml

@@ -1,12 +1,13 @@
-<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom"><title>Godot Engine Official</title><link href="https://godotengine.org/atom.xml" rel="self"/><link href="https://godotengine.org/"/><updated>2025-04-25T15:40:52+00:00</updated><id>https://godotengine.org/</id><entry><title>Dev snapshot: Godot 4.5 dev 3</title><link href="https://godotengine.org/article/dev-snapshot-godot-4-5-dev-3/"/><updated>2025-04-25T12:00:00+00:00</updated><id>https://godotengine.org/article/dev-snapshot-godot-4-5-dev-3/</id><summary>Access the engine like never before!</summary><content type="html">&lt;p>If the past snapshot was any indication, you might think that development updates aren’t slowing down anytime soon. And… You’d be right! Indeed, progress has been booming, and the amount of new features added even compared to the previous release is staggering; curating this selection was especially difficult. As always, new features mean new bugs in need of fixing, so we encourage everyone interested to get feedback and bug reports in as early as possible.&lt;/p>
+<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom"><title>Godot Engine Official</title><link href="https://godotengine.org/atom.xml" rel="self"/><link href="https://godotengine.org/"/><updated>2025-04-25T21:16:57+00:00</updated><id>https://godotengine.org/</id><entry><title>Dev snapshot: Godot 4.5 dev 3</title><link href="https://godotengine.org/article/dev-snapshot-godot-4-5-dev-3/"/><updated>2025-04-25T12:00:00+00:00</updated><id>https://godotengine.org/article/dev-snapshot-godot-4-5-dev-3/</id><summary>Access the engine like never before!</summary><content type="html">&lt;p>If the past snapshot was any indication, you might think that development updates aren’t slowing down anytime soon. And… You’d be right! Indeed, progress has been booming, and the amount of new features added even compared to the previous release is staggering; curating this selection was especially difficult. As always, new features mean new bugs in need of fixing, so we encourage everyone interested to get feedback and bug reports in as early as possible.&lt;/p>
 &lt;p>&lt;a href="#downloads">Jump to the &lt;strong>Downloads&lt;/strong> section&lt;/a>, and give it a spin right now, or continue reading to learn more about improvements in this release. You can also &lt;a href="https://editor.godotengine.org/releases/4.5.dev3/">try the &lt;strong>Web editor&lt;/strong>&lt;/a> or the &lt;strong>Android editor&lt;/strong> for this release. If you are interested in the latter, please request to join &lt;a href="https://groups.google.com/g/godot-testers">our testing group&lt;/a> to get access to pre-release builds.&lt;/p>
 &lt;hr />
 &lt;p>&lt;em>The cover illustration is from&lt;/em> &lt;a href="https://store.steampowered.com/app/3454590/Cornerpond/?curator_clanid=41324400">&lt;strong>Cornerpond&lt;/strong>&lt;/a>, &lt;em>a fishing game that takes place entirely in the corner of your desktop. It is developed by &lt;a href="https://foolsroom.itch.io/">foolsroom&lt;/a>. You can get the game &lt;a href="https://store.steampowered.com/app/3454590/Cornerpond/?curator_clanid=41324400">on Steam&lt;/a> and follow the developer on &lt;a href="https://twitter.com/foolsroom">Twitter&lt;/a>.&lt;/em>&lt;/p>
 &lt;h2 id="highlights">Highlights&lt;/h2>
 &lt;p>In case you missed them, see the &lt;a href="/article/dev-snapshot-godot-4-5-dev-1/">4.5 dev 1&lt;/a> and &lt;a href="/article/dev-snapshot-godot-4-5-dev-2/">4.5 dev 2&lt;/a> release notes for an overview of some key features which were already in that snapshot, and are therefore still available for testing in dev 3.&lt;/p>
 &lt;h3 id="screen-reader-support">Screen reader support&lt;/h3>
-&lt;p>Accessibility should be every developer’s top priority, full-stop. Someone being excluded from an experience for factors outside of their control is an area that video games and applications have the potential to circumvent entirely. It does, however, take a solid framework to allow such accommodations to take place. To streamline this process for everyone—players and developers alike—our resident tech guru &lt;a href="https://github.com/bruvzg">bruvzg&lt;/a> took to the absolutely Herculean task of integrating &lt;a href="https://github.com/AccessKit/accesskit">AccessKit&lt;/a> to Godot as a whole.&lt;/p>
-&lt;p>&lt;a href="https://github.com/godotengine/godot/pull/76829">GH-76829&lt;/a> was a project two years in the making, changing over &lt;strong>32,000&lt;/strong> lines of code, and incurred hundreds of comments with feedback/testing. Users are encouraged to look at the pull request for more information, as there’s no feasible way we could properly summarize these changes. Unsurprisingly, this was &lt;em>by far&lt;/em> the change with the most ramifications of the entire snapshot, so much so that it’s already seen &lt;a href="https://github.com/godotengine/godot/pull/105197">multiple&lt;/a> &lt;a href="https://github.com/godotengine/godot/pull/105216">fixes&lt;/a> caused by its regressions, but it’s well worth it. After all, accessibility is our top priority!&lt;/p>
+&lt;p>Accessibility should be every developer’s top priority, full-stop. Someone being excluded from an experience for factors outside of their control is an area that video games and applications have the potential to circumvent entirely. It does, however, take a solid framework to allow such accommodations to be developed. To streamline this process for everyone—players and developers alike—our resident tech guru &lt;a href="https://github.com/bruvzg">bruvzg&lt;/a> took to the absolutely Herculean task of integrating &lt;a href="https://github.com/AccessKit/accesskit">AccessKit&lt;/a> to Godot as a whole.&lt;/p>
+&lt;p>&lt;a href="https://github.com/godotengine/godot/pull/76829">GH-76829&lt;/a> was a project started two years ago, which progressed in bursts alongside the AccessKit framework. For the 4.5 release, we made it a priority to finalize, and thus we now merged this major feature with over &lt;strong>32,000&lt;/strong> lines of code, after hundreds of comments with feedback/testing. Users are encouraged to look at the pull request for more information, as there’s no feasible way we could properly summarize these changes. Unsurprisingly, this was &lt;em>by far&lt;/em> the change with the most ramifications of the entire snapshot, so much so that it’s already seen &lt;a href="https://github.com/godotengine/godot/pull/105197">multiple&lt;/a> &lt;a href="https://github.com/godotengine/godot/pull/105216">fixes&lt;/a> to address regressions (even &lt;a href="https://github.com/godotengine/godot/pull/105764">one&lt;/a> right when validating this snapshot), but it’s well worth it. After all, accessibility is our top priority!&lt;/p>
+&lt;p>This is only the first but massive step towards making Godot more accessible. In particular for the editor, a lot more work will be needed to make it really usable, as well as integrate with accessibility frameworks for mobile or web platforms.&lt;/p>
 &lt;h3 id="script-backtracing">Script backtracing&lt;/h3>
 &lt;p>In any other snapshot, this would’ve been the main highlight, as adding backtracing to GDScript was among the most highly requested features from our users for years. Two brave souls, &lt;a href="https://github.com/mihe">Mikael Hermansson&lt;/a> (godot-jolt) and &lt;a href="https://github.com/reduz">Juan Linietsky&lt;/a> (up-and-coming developer), helmed this task and made this process possible with &lt;a href="https://github.com/godotengine/godot/pull/91006">GH-91006&lt;/a>. This will make it much easier for users to find the cause of warnings/errors that previously required manually hunting down bugs. Stack traces are now available in projects exported in release mode as well if the &lt;strong>Debug &amp;gt; Settings &amp;gt; GDScript &amp;gt; Always Track Call Stacks&lt;/strong> project setting is enabled. This can make it easier for users to report issues in a way that developers can track down.&lt;/p>
 &lt;p>&lt;img src="/storage/blog/dev-snapshot-godot-4-5-dev-3/backtrace-script.webp" alt="Backtrace script" />

rss.xml

@@ -5,8 +5,9 @@
 <h2 id="highlights">Highlights</h2>
 <p>In case you missed them, see the <a href="/article/dev-snapshot-godot-4-5-dev-1/">4.5 dev 1</a> and <a href="/article/dev-snapshot-godot-4-5-dev-2/">4.5 dev 2</a> release notes for an overview of some key features which were already in that snapshot, and are therefore still available for testing in dev 3.</p>
 <h3 id="screen-reader-support">Screen reader support</h3>
-<p>Accessibility should be every developer’s top priority, full-stop. Someone being excluded from an experience for factors outside of their control is an area that video games and applications have the potential to circumvent entirely. It does, however, take a solid framework to allow such accommodations to take place. To streamline this process for everyone—players and developers alike—our resident tech guru <a href="https://github.com/bruvzg">bruvzg</a> took to the absolutely Herculean task of integrating <a href="https://github.com/AccessKit/accesskit">AccessKit</a> to Godot as a whole.</p>
-<p><a href="https://github.com/godotengine/godot/pull/76829">GH-76829</a> was a project two years in the making, changing over <strong>32,000</strong> lines of code, and incurred hundreds of comments with feedback/testing. Users are encouraged to look at the pull request for more information, as there’s no feasible way we could properly summarize these changes. Unsurprisingly, this was <em>by far</em> the change with the most ramifications of the entire snapshot, so much so that it’s already seen <a href="https://github.com/godotengine/godot/pull/105197">multiple</a> <a href="https://github.com/godotengine/godot/pull/105216">fixes</a> caused by its regressions, but it’s well worth it. After all, accessibility is our top priority!</p>
+<p>Accessibility should be every developer’s top priority, full-stop. Someone being excluded from an experience for factors outside of their control is an area that video games and applications have the potential to circumvent entirely. It does, however, take a solid framework to allow such accommodations to be developed. To streamline this process for everyone—players and developers alike—our resident tech guru <a href="https://github.com/bruvzg">bruvzg</a> took to the absolutely Herculean task of integrating <a href="https://github.com/AccessKit/accesskit">AccessKit</a> to Godot as a whole.</p>
+<p><a href="https://github.com/godotengine/godot/pull/76829">GH-76829</a> was a project started two years ago, which progressed in bursts alongside the AccessKit framework. For the 4.5 release, we made it a priority to finalize, and thus we now merged this major feature with over <strong>32,000</strong> lines of code, after hundreds of comments with feedback/testing. Users are encouraged to look at the pull request for more information, as there’s no feasible way we could properly summarize these changes. Unsurprisingly, this was <em>by far</em> the change with the most ramifications of the entire snapshot, so much so that it’s already seen <a href="https://github.com/godotengine/godot/pull/105197">multiple</a> <a href="https://github.com/godotengine/godot/pull/105216">fixes</a> to address regressions (even <a href="https://github.com/godotengine/godot/pull/105764">one</a> right when validating this snapshot), but it’s well worth it. After all, accessibility is our top priority!</p>
+<p>This is only the first but massive step towards making Godot more accessible. In particular for the editor, a lot more work will be needed to make it really usable, as well as integrate with accessibility frameworks for mobile or web platforms.</p>
 <h3 id="script-backtracing">Script backtracing</h3>
 <p>In any other snapshot, this would’ve been the main highlight, as adding backtracing to GDScript was among the most highly requested features from our users for years. Two brave souls, <a href="https://github.com/mihe">Mikael Hermansson</a> (godot-jolt) and <a href="https://github.com/reduz">Juan Linietsky</a> (up-and-coming developer), helmed this task and made this process possible with <a href="https://github.com/godotengine/godot/pull/91006">GH-91006</a>. This will make it much easier for users to find the cause of warnings/errors that previously required manually hunting down bugs. Stack traces are now available in projects exported in release mode as well if the <strong>Debug > Settings > GDScript > Always Track Call Stacks</strong> project setting is enabled. This can make it easier for users to report issues in a way that developers can track down.</p>
 <p><img src="/storage/blog/dev-snapshot-godot-4-5-dev-3/backtrace-script.webp" alt="Backtrace script" />