Remove old Godot version references to simplify documentation

This follows the documentation writing guidelines, specifically
the "When to refer to a specific Godot version" section.

This also removes warning blocks for a known issue that was resolved in Godot 4.5.
This commit is contained in:
Hugo Locurcio
2025-10-07 19:01:12 +02:00
parent 6ebd201367
commit b3cbe5f777
24 changed files with 63 additions and 81 deletions
@@ -305,7 +305,7 @@ Color given as red-green-blue value (alpha will always be 1).
Nodes
-----
Since Godot 4.0, nodes can be directly exported without having to use NodePaths.
Nodes can also be directly exported without having to use NodePaths.
.. code-block:: csharp
@@ -11,8 +11,8 @@ As explained in the :ref:`doc_debugger_panel` documentation, Godot features a
graphs showing their evolution over time. The data for those graphs is sourced
from the engine's :ref:`class_Performance` singleton.
Since Godot 4.0, you can declare custom values to be displayed in the Monitors
tab. Example use cases for custom performance monitors include:
Godot lets you declare custom values to be displayed in the Monitors tab.
Example use cases for custom performance monitors include:
- Displaying performance metrics that are specific to your project. For
instance, in a voxel game, you could create a performance monitor to track the
@@ -859,7 +859,7 @@ Negative indices count from the end.
Typed arrays
^^^^^^^^^^^^
Godot 4.0 added support for typed arrays. On write operations, Godot checks that
Godot also features support for typed arrays. On write operations, Godot checks that
element values match the specified type, so the array cannot contain invalid values.
The GDScript static analyzer takes typed arrays into account, however array methods like
``front()`` and ``back()`` still have the ``Variant`` return type.
@@ -253,8 +253,8 @@ Color given as red-green-blue value (alpha will always be 1). See :ref:`@export_
Nodes
-----
Since Godot 4.0, nodes can be directly exported as properties in a script
without having to use NodePaths:
Nodes can also be directly exported as properties in a script without
having to use NodePaths:
::