Test3

.github/workflows/markdownlint.yml

@@ -2,6 +2,7 @@ name: Lint Markdown
 
 on:
   pull_request_target:
+    types: [opened, synchronize, reopened, edited]
 
 permissions:
   contents: write

.markdownlint.json

@@ -0,0 +1,17 @@
+{
+  "default": true,
+  "MD001": false,
+  "MD004": false,
+  "MD007": { "indent": 4, "start_indent": 2, "start_indented": true },
+  "MD010": { "ignore_code_languages": ["text"] },
+  "MD013": false,
+  "MD024": false,
+  "MD025": false,
+  "MD026": false,
+  "MD033": false,
+  "MD036": false,
+  "MD038": false,
+  "MD045": false,
+  "MD046": false,
+  "MD047": false
+}

CONTRIBUTE.md

@@ -38,7 +38,7 @@ mkdocs serve
 mkdocs serve --dirtyreload
 ```
 
-This will run the documentation on http://localhost:8000.
+This will run the documentation on <http://localhost:8000>.
 
 ### Build
 

SYNTAX.md

@@ -21,7 +21,7 @@ For example, to display:
 
 You shall write:
 
-```
+```md
 - Getting started
     - First step
     - Second step
@@ -41,7 +41,7 @@ List of objects:
 
 will be rendered as:
 
-```
+```md
 List of objects: - Sprite - Text
 ```
 
@@ -67,7 +67,7 @@ For example, to display:
 
 You shall write:
 
-```
+```md
 1. First item
     1. First nested item
     1. Second nested item
@@ -84,9 +84,9 @@ Use this syntax:
 
 ```md
 <div class="video-container">
-<video controls>
-  <source src="/gdevelop5/objects/ParticleEmitterWishforgeVideo.mp4">
-</video>
+  <video controls>
+    <source src="/gdevelop5/objects/ParticleEmitterWishforgeVideo.mp4">
+  </video>
 </div>
 ```
 

docs/es/gdevelop5/objects/sprite.md

@@ -71,9 +71,9 @@ Para agregar el objeto sprite a nuestra escena, simplemente selecciónelo y haga
 Tu nuevo sprite ahora está completo, pero aún debes agregarlo a la escena de tu juego. Haga clic en el nuevo sprite en la lista de objetos. A continuación, haga clic en la escena donde desea agregar el sprite. Ahora verás tu sprite agregado a la escena. Puedes agregar múltiples "instancias" de tu sprite a tu pantalla de juego. Simplemente repita el proceso para agregar el primer sprite.
 
 <div class="video-container">
-<video controls>
-  <source src="/gdevelop5/objects/addspritetoscenecompressed.mp4">
-</video>
+  <video controls>
+    <source src="/gdevelop5/objects/addspritetoscenecompressed.mp4">
+  </video>
 </div>
 
 ### Más información sobre animaciones múltiples mientras usas eventos.

docs/gdevelop5/all-features/admob/index.md

@@ -9,11 +9,11 @@ Follow the [Google official documentation](https://support.google.com/admob/answ
 
 Ads can be loaded and displayed in your game at any time. They can be displayed as:
 
- * **App open** that opens while your app starts
- * **Banners** at the top or bottom of the screen
- * **Interstitials** that cover the entire screen.
- * **Rewarded videos** that show a video to the user rewarding them something at the end.
- * **Rewarded interstitials** that are similar to videos, but that the user can skip
+  * **App open** that opens while your app starts
+  * **Banners** at the top or bottom of the screen
+  * **Interstitials** that cover the entire screen.
+  * **Rewarded videos** that show a video to the user rewarding them something at the end.
+  * **Rewarded interstitials** that are similar to videos, but that the user can skip
 
 Banner ads are usually displayed during gameplay. Interstitial screens and reward videos are displayed after the completion of a level or an objective.
 

docs/gdevelop5/all-features/advanced-conditions/index.md

@@ -4,15 +4,16 @@ title: Advanced conditions
 # Advanced conditions
 
 ## And logical operation
+
 ![](and.png)
 
 If the "**And**" condition is used in an event, the actions are performed if and only if all the sub-conditions are true. If one or more than one sub-conditions are false, the action is not performed.
 !!! note
 
     The "**And**" condition is usually meant to be used within an "**Or**" condition. This is because having two conditions in the same event box is the same as using the "**And**" condition.
 
-
 ## OR logical operation
+
 ![](or-condition.png)
 
 If the "**OR**" condition is used in an event, the actions are performed when one or several sub-conditions are true. If none of the sub-conditions are true, the action is not performed.
@@ -22,11 +23,13 @@ If the "**OR**" condition is used in an event, the actions are performed when on
     The OR condition has a special behavior regarding the [object filtering logic of GDevelop](http://wiki.compilgames.net/doku.php/gdevelop5/tutorials/basic-game-making-concepts#events_and_how_objects_are_selected_by_these_events). The objects listed under it are _unselected_ by GDevelop if their condition is not met, so actions specific to these objects may not work. In some cases, using "Pick all instances" on the action side will fix things. In other cases, replacing the OR will be necessary.
 
 ## Not logical operation
+
 ![](not-condition.png)
 
 If the "**Not**" condition is used in an event, it returns the contrary of the sub-conditions. If a sub-condition is true, it returns false and if a sub-condition is false, it returns true.
 
 ## Trigger once
+
 ![](trigger-once-condition.png)
 
 Whenever the "**Trigger once while true**" condition is used, the actions for the event are triggered only once, for each time the conditions have been met.
@@ -36,18 +39,21 @@ Whenever the "**Trigger once while true**" condition is used, the actions for th
     This condition applies to objects, not instances. If you need to trigger once for each instance, use an instance variable instead.
 
 ## Compare two numbers
+
 ![](compare-two-numbers-condition.png)
 
 When you use the "**Compare two numbers**" condition, it will compare the two numbers/expression based on the Sign of the test. If the numbers satisfy the test, the condition returns true and the corresponding actions are performed.
 
 For example, suppose if the first value is entered as 5, the sign of the test is set to < (less than)" and the second value is equal to 7. In such a case, the test returns true because 5 is less than 7.
 
 ## Compare two strings
+
 ![](compare-two-strings-condition.png)
 
 When you use the "**Compare two strings**" condition, it will compare the two strings/expression based on the Sign of the test. If the numbers satisfy the test, the condition returns true and the corresponding actions are performed.
 
 ## Always true/false
+
 ![](always-condition.png)
 
 If you want a condition to always return true and the corresponding actions to be performed, you can use the "**Always**" condition. If the condition is inverted, it will always return false,_i.e. the corresponding actions will never be performed._

docs/gdevelop5/all-features/audio/index.md

@@ -73,7 +73,7 @@ The condition "A sound is being played" (on this channel) is then true, while "A
 
 The sound will be stopped when:
 
-* It reaches its **end** and is not configured to loop. * There is **an error during the loading** (in which case it will be considered as playing for a few milliseconds, then will be deemed to be stopped as it was unable to load). * Or you used **the action** to stop a sound or music on the channel.
+  * It reaches its **end** and is not configured to loop. *There is **an error during the loading** (in which case it will be considered as playing for a few milliseconds, then will be deemed to be stopped as it was unable to load).* Or you used **the action** to stop a sound or music on the channel.
 
 ## Reference
 

docs/gdevelop5/all-features/collisions/index.md

@@ -8,6 +8,7 @@ Most games need to detect and handle collisions between objects. Detecting and h
 GDevelop provides several different ways to handle collisions. You can detect collisions using Event Editor conditions and actions, or you can use Object behaviors.
 
 ## Make objects solids: use the "Separate objects" action (good for top-down games, RPG...)
+
 ![](/gdevelop5/all-features/separate-condition.png)
 
 You can use the "**Separate objects**" action to move objects manually. The "Separate objects" action can also move objects with "forces" or set the object's position.
@@ -44,7 +45,6 @@ You can find usage of these conditions and actions in the examples:
 
 [![](/gdevelop5/all-features/checkccollisionbetweenobjectsnew.png)](https://editor.gdevelop.io?project=example://bomb-the-crate)
 
-
 ## Platformer games: use the Platformer character and Platform behaviors
 
 If you're making a platformer game, it's a good idea to use the ["Platformer character" behavior](/gdevelop5/behaviors/platformer). It's a ready-made platform game engine that is highly customizable. The "Platformer character" behavior handles the gravity and the collisions with the platforms.
@@ -53,8 +53,8 @@ If you're making a platformer game, it's a good idea to use the ["Platformer cha
 
 In a platformer game with the "Platformer character" behavior, collisions with platforms are handled for you.
 
-* You can still use the **Collision condition** to check for collisions between an object and other objects (for example, between the player and enemies) and react accordingly.
-* You can use the "Is on Floor" condition to check if an object is on a platform.
+  * You can still use the **Collision condition** to check for collisions between an object and other objects (for example, between the player and enemies) and react accordingly.
+  * You can use the "Is on Floor" condition to check if an object is on a platform.
 
 ![](/gdevelop5/all-features/playerisonfloorevents.png)
 

docs/gdevelop5/all-features/device-vibration/index.md

@@ -9,13 +9,13 @@ Vibration is supported on these devices:
 
 HTML web games:
 
-- Android: Yes
-- Apple iOS: **No**
+  - Android: Yes
+  - Apple iOS: **No**
 
 Native mobile apps:
 
-- Android: Yes
-- Apple iOS: Yes
+  - Android: Yes
+  - Apple iOS: Yes
 
 !!! note