Merge pull request #11352 from Calinou/remove-old-version-references

Remove old Godot version references to simplify documentation

Author: mhilbrunner

engine_details/development/compiling/introduction_to_the_buildsystem.rst

@@ -485,7 +485,7 @@ create its own template.
 The ``version.txt`` file should contain the corresponding Godot version
 identifier. This file is used to install export templates in a version-specific
 directory to avoid conflicts. For instance, if you are building export templates
-for Godot 3.1.1, ``version.txt`` should contain ``3.1.1.stable`` on the first
+for Godot 4.4.1, ``version.txt`` should contain ``4.4.1.stable`` on the first
 line (and nothing else). This version identifier is based on the ``major``,
 ``minor``, ``patch`` (if present) and ``status`` lines of the
 `version.py file in the Godot Git repository <https://github.com/godotengine/godot/blob/master/version.py>`__.

engine_details/development/compiling/optimizing_for_size.rst

@@ -78,7 +78,7 @@ Optimizing for size instead of speed
 - **Difficulty:** Easy
 - **Performed in official builds:** Yes, but only for web builds
 
-Godot 3.1 onwards allows compiling using size optimizations (instead of speed).
+It is possible to compile Godot using size optimizations (instead of speed).
 To enable this, set the ``optimize`` flag to ``size``:
 
 ::

tutorials/2d/2d_lights_and_shadows.rst

@@ -114,10 +114,9 @@ transparent white, and move its starting location to be in the center.
 Directional light
 -----------------
 
-New in Godot 4.0 is the ability to have directional lighting in 2D. Directional
-lighting is used to represent sunlight or moonlight. Light rays are casted
-parallel to each other, as if the sun or moon was infinitely far away from the
-surface that is receiving the light.
+Directional lighting is used to represent sunlight or moonlight. Light rays are
+casted parallel to each other, as if the sun or moon was infinitely far away
+from the surface that is receiving the light.
 
 DirectionalLight2D offers the following properties:
 
@@ -265,8 +264,8 @@ the surface receiving light (on a per-pixel basis). Specular maps further help
 improve visuals by making some of the light reflect back to the viewer.
 
 Both PointLight2D and DirectionalLight2D support normal mapping and specular
-mapping. Since Godot 4.0, normal and specular maps can be assigned to any 2D
-element, including nodes that inherit from Node2D or Control.
+mapping. Normal and specular maps can be assigned to any 2D element,
+including nodes that inherit from Node2D or Control.
 
 A normal map represents the direction in which each pixel is "pointing" towards.
 This information is then used by the engine to correctly apply lighting to 2D

tutorials/2d/using_tilesets.rst

@@ -157,7 +157,7 @@ three vertical dots menu button at the top of the TileSet editor and choose
 Using a collection of scenes
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Since Godot 4.0, you can place actual *scenes* as tiles. This allows you to use
+You can also place actual *scenes* as tiles. This allows you to use
 any collection of nodes as a tile. For example, you could use scene tiles to
 place gameplay elements, such as shops the player may be able to interact with.
 You could also use scene tiles to place AudioStreamPlayer2Ds (for ambient

tutorials/3d/global_illumination/using_lightmap_gi.rst

@@ -20,9 +20,9 @@ light bleeding, and indirect light will often look better. The downside is that
 baking lightmaps takes longer compared to baking VoxelGI. While baking VoxelGI
 can be done in a matter of seconds, baking lightmaps can take several minutes if
 not more. This can slow down iteration speed significantly, so it is recommended
-to bake lightmaps only when you actually need to see changes in lighting. Since
-Godot 4.0, lightmaps are baked on the GPU, making light baking faster if you
-have a mid-range or high-end dedicated GPU.
+to bake lightmaps only when you actually need to see changes in lighting.
+Lightmaps are baked on the GPU, making light baking faster if you have a
+mid-range or high-end dedicated GPU.
 
 Baking lightmaps will also reserve baked materials' UV2 slot, which means you can
 no longer use it for other purposes in materials (either in the built-in

tutorials/3d/global_illumination/using_sdfgi.rst

@@ -4,7 +4,7 @@ Signed distance field global illumination (SDFGI)
 =================================================
 
 Signed distance field global illumination (SDFGI) is a novel technique available
-in Godot 4.0. It provides semi-real-time global illumination that scales to any
+in Godot. It provides semi-real-time global illumination that scales to any
 world size and works with procedurally generated levels.
 
 SDFGI supports dynamic lights, but *not* dynamic occluders or dynamic emissive surfaces.

tutorials/3d/particles/attractors.rst

@@ -73,12 +73,6 @@ on each system's :ref:`visibility layers <class_VisualInstance3D>`. A particle s
 affected by an attractor if at least one of the system's visibility layers is enabled in the
 attractor's cull mask.
 
-.. warning::
-
-   There is a `known issue <https://github.com/godotengine/godot/issues/61014>`_ with
-   GPU particle attractors that prevent the cull mask from working properly in Godot 4.0. We will
-   update the documentation as soon as it is fixed.
-
 Box attractors
 ~~~~~~~~~~~~~~
 

tutorials/3d/particles/collision.rst

@@ -28,12 +28,6 @@ on each system's :ref:`visibility layers <class_VisualInstance3D>`. A particle s
 collision node only if at least one of the system's visibility layers is enabled in the
 collider's cull mask.
 
-.. warning::
-
-   There is a `known issue <https://github.com/godotengine/godot/issues/61014>`_ with
-   GPU particle collision that prevent the cull mask from working properly in Godot 4.0. We will
-   update the documentation as soon as it is fixed.
-
 Box collision
 ~~~~~~~~~~~~~
 

tutorials/animation/animation_tree.rst

@@ -12,14 +12,13 @@ function calling, audio, and sub-animation tracks.
 
 However, the support for blending those animations via ``AnimationPlayer`` is limited, as you can only set a fixed cross-fade transition time.
 
-:ref:`AnimationTree <class_AnimationTree>` is a new node introduced in Godot 3.1 to deal with advanced transitions.
-It replaces the ancient ``AnimationTreePlayer``, while adding a huge amount of features and flexibility.
+:ref:`AnimationTree <class_AnimationTree>` is a node designed to deal with advanced transitions.
 
 AnimationTree and AnimationPlayer
 ---------------------------------
 
 Before starting, know that an ``AnimationTree`` node does not contain its own animations.
-Instead, it uses animations contained in an ``AnimationPlayer`` node. You create, edit, or import your animations in an ``AnimationPlayer`` 
+Instead, it uses animations contained in an ``AnimationPlayer`` node. You create, edit, or import your animations in an ``AnimationPlayer``
 and then use an ``AnimationTree`` to control the playback.
 
 ``AnimationPlayer`` and ``AnimationTree`` can be used in both 2D and 3D scenes. When importing 3D scenes and their animations, you can use
@@ -38,8 +37,8 @@ and an ``AnimationTree`` node was created.
 Creating a tree
 ---------------
 
-To use an ``AnimationTree``, you have to set a root node. An animation root node is a class that contains and evaluates sub-nodes and outputs an animation. 
-There are 3 types of sub-nodes: 
+To use an ``AnimationTree``, you have to set a root node. An animation root node is a class that contains and evaluates sub-nodes and outputs an animation.
+There are 3 types of sub-nodes:
 
 1. Animation nodes, which reference an animation from the linked ``AnimationPlayer``.
 2. Animation Root nodes, which are used to blend sub-nodes and can be nested.
@@ -59,7 +58,7 @@ Blend tree
 ----------
 
 When you make an ``AnimationNodeBlendTree``, you get an empty 2d graph in the bottom panel, under the AnimationTree tab. It contains only an ``Output``
-node by default. 
+node by default.
 
 .. image:: img/animtree_emptyblendtree.webp
 
@@ -202,11 +201,11 @@ StateMachine
 ~~~~~~~~~~~~
 
 When you make an ``AnimationNodeStateMachine``, you get an empty 2d graph in the bottom panel, under the AnimationTree tab. It contains a ``Start`` and ``End``
-state by default. 
+state by default.
 
 .. image:: img/animtree_emptystatemachine.webp
 
-To add states, right click or use the **create new nodes** button, whose icon is a plus in a box. You can add animations, blendspaces, blendtrees, or even 
+To add states, right click or use the **create new nodes** button, whose icon is a plus in a box. You can add animations, blendspaces, blendtrees, or even
 another StateMachine. To edit one of these more complex sub-nodes, click on the pencil icon on the right of the state. To return to the original StateMachine,
 click **Root** on the top left of the panel.
 
@@ -219,7 +218,7 @@ There are 3 types of transitions:
 
 .. image:: img/animtree_transitiontypes.png
 
-* *Immediate*: Will switch to the next state immediately. 
+* *Immediate*: Will switch to the next state immediately.
 * *Sync*: Will switch to the next state immediately, but will seek the new state to the playback position of the old state.
 * *At End*: Will wait for the current state playback to end, then switch to the beginning of the next state animation.
 
@@ -240,12 +239,12 @@ Advance Condition and Advance Expression
 The last 2 properties in a StateMachine transition are ``Advance Condition`` and ``Advance Expression.`` When the Advance Mode is set to *Auto*, these
 determine if the transition will advance or not.
 
-Advance Condition is a true/false check. You may put a custom variable name in the text field, and when the StateMachine reaches this transition, 
-it will check if your variable is *true*. If so, the transition continues. Note that the advance condition **only** checks if a variable is *true*, 
+Advance Condition is a true/false check. You may put a custom variable name in the text field, and when the StateMachine reaches this transition,
+it will check if your variable is *true*. If so, the transition continues. Note that the advance condition **only** checks if a variable is *true*,
 and it cannot check for falseness.
 
-This gives the Advance Condition a very limited capability. If you wanted to make a transition back and forth based on one property, you would need to make 
-2 variables that have opposite values, and check if either of them are true. This is why, in Godot 4, the Advance Expression was added. 
+This gives the Advance Condition a very limited capability. If you wanted to make a transition back and forth based on one property, you would need to make
+2 variables that have opposite values, and check if either of them are true. This is why, in Godot 4, the Advance Expression was added.
 
 The Advance Expression works similar to the Advance Condition, but instead of checking if one variable is true, it evaluates any expression. An expression
 is anything you could put in an ``if`` statement. These are all examples of expressions that would work in the Advance Expression:
@@ -308,14 +307,14 @@ is controlled to determine the blending:
 
 .. image:: img/animtree_blendspace2d.gif
 
-You may place these points anywhere on the graph by right clicking or using the **add point** button, whose icon is a pen and point. 
+You may place these points anywhere on the graph by right clicking or using the **add point** button, whose icon is a pen and point.
 Wherever you place the points, the triangle between them will be generated automatically using Delaunay.
-You may also control and label the ranges in X and Y. 
+You may also control and label the ranges in X and Y.
 
 .. image:: img/animtree_blendspacepoints.gif
 
-Finally, you may also change the blend mode. By default, blending happens by interpolating points inside the closest triangle. When dealing with 2D 
-animations (frame by frame), you may want to switch to *Discrete* mode. Alternatively, if you want to keep the current play position when switching 
+Finally, you may also change the blend mode. By default, blending happens by interpolating points inside the closest triangle. When dealing with 2D
+animations (frame by frame), you may want to switch to *Discrete* mode. Alternatively, if you want to keep the current play position when switching
 between discrete animations, there is a *Carry* mode. This mode can be changed in the *Blend* menu:
 
 .. image:: img/animtree_blendmode.png
@@ -327,7 +326,7 @@ BlendSpace1D works just like BlendSpace2D, but in one dimension (a line). Triang
 For better blending
 -------------------
 
-In Godot 4.0+, in order for the blending results to be deterministic (reproducible and always consistent),
+For the blending results to be deterministic (reproducible and always consistent),
 the blended property values must have a specific initial value.
 For example, in the case of two animations to be blended, if one animation has a property track and the other does not,
 the blended animation is calculated as if the latter animation had a property track with the initial value.
@@ -354,7 +353,7 @@ This problem can be solved by adding a Property track for Position as an initial
           It is assumed to have only one frame and is not expected to be played back using the timeline.
 
 Also keep in mind that the Rotation 3D tracks and the Property tracks for 2D rotation
-with Interpolation Type set to Linear Angle or Cubic Angle will prevent rotations greater than 180 degrees 
+with Interpolation Type set to Linear Angle or Cubic Angle will prevent rotations greater than 180 degrees
 from the initial value as blended animation.
 
 This can be useful for Skeleton3Ds to prevent the bones penetrating the body when blending animations.
@@ -447,5 +446,5 @@ Then you can set or read them:
 
     animationTree.Set("parameters/eye_blend/blend_amount", 1.0);
 
-.. note:: Advance Expressions from a StateMachine will not be found under the parameters. This is because they are held in another script rather than the 
+.. note:: Advance Expressions from a StateMachine will not be found under the parameters. This is because they are held in another script rather than the
          AnimationTree itself. Advance `Conditions` will be found under parameters.

tutorials/animation/playing_videos.rst

@@ -47,7 +47,7 @@ Setting up VideoStreamPlayer
 Handling resizing and different aspect ratios
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-By default in Godot 4.0, the VideoStreamPlayer will automatically be resized to match
+By default, the VideoStreamPlayer will automatically be resized to match
 the video's resolution. You can make it follow usual :ref:`class_Control` sizing
 by enabling **Expand** on the VideoStreamPlayer node.