[Auto] [Improve] Enhanced variables docs with bject variable guidance, and physics2 fixes (#454)

Author: github-actions[bot]

automated_updates_data.json

@@ -28,6 +28,10 @@
     {
       "date": "2026-02-16",
       "summary": "Improved bitmap text and shape painter documentation: added alignment properties, wrapping width, and comprehensive list of all shape types"
+    },
+    {
+      "date": "2026-02-18",
+      "summary": "Improved variables documentation: added array/structure manipulation operations, object variable use-case guidance, and fixed physics2 typos"
     }
   ]
 }

docs/gdevelop5/all-features/variables/object-variables.md

@@ -31,3 +31,17 @@ In the editor, choose "Add a variable", then enter a name, choose a data type an
 ## Using object variables in expressions
 
 You can use object variables in [expressions](/gdevelop5/all-features/expressions). Just write the name of the object, followed by a dot then the name of the variable to use it in a formula. For example: `Player.RemainingPoints`.
+
+## When to use object variables
+
+Object variables are the right choice when the data is **specific to one instance**. For example:
+
+- An enemy's current health — each enemy on the screen needs its own value. While a variable can work, the [Health behavior](/gdevelop5/extensions/health/) is usually a better choice for managing health.
+- A projectile's damage — each projectile may carry a different power level depending on the weapon that fired it.
+- A collectible's point value — each coin or gem can hold a different reward.
+
+If every instance always shares the same value, a [scene variable](/gdevelop5/all-features/variables/scene-variables) or a [global variable](/gdevelop5/all-features/variables/global-variables) is usually simpler.
+
+!!! tip
+
+    Object variables can also hold structures or arrays, which lets you store complex per-instance data (for example, an inventory attached to a character object) without needing any additional variables.

docs/gdevelop5/behaviors/physics2/index.md

@@ -30,7 +30,7 @@ The world has three properties:
 
   * **Gravity**. It consists of two components (X and Y) and works like our gravity adding a force to every object, pushing them in the given direction. Objects support a gravity scale factor too, more on this in the bodies section.
   * **Timescale**. It defines the scale of time the simulation will use. With a timescale of `0.5`, the simulation will run at half the speed; with a timescale of `2`, the simulation will be twice as fast. If timescale is `0`, the simulation will pause. Super useful for bullet time effects!
-  * **Scale**. GDevelop distances and sizes are defined in pixels, but the physics engine uses meters internally. A scale factor must is set (with two components, scale on X axis and on Y axis) to make the conversion. The scale numbers mean how many pixels a meter is; for example, a scale of 50 means that a distance of 50 pixels in GDevelop is converted to 1 meter in the physics world.
+  * **Scale**. GDevelop distances and sizes are defined in pixels, but the physics engine uses meters internally. A scale factor must be set (with two components, scale on X axis and on Y axis) to make the conversion. The scale numbers mean how many pixels a meter is; for example, a scale of 50 means that a distance of 50 pixels in GDevelop is converted to 1 meter in the physics world.
 
 !!! note
 
@@ -42,7 +42,7 @@ Bodies are the life of the Physics extension; they define how your object will m
 
 When you add the Physics behavior to an object, you can set the body configuration right from the IDE.
 There are many options to play with. They have been categorized below.
-.
+
 ### Body Type
 
 GDevelop supports three basic body types: