From 7119de123850ccb124cf1216100a438ad74bfb1d Mon Sep 17 00:00:00 2001 From: Gurpreet Singh Matharoo Date: Thu, 29 Jan 2026 12:48:33 +0530 Subject: [PATCH 001/108] docs(general): Document that async group names are also affected by target platform https://github.com/YoYoGames/GameMaker-Bugs/issues/13784 --- .../Buffers/buffer_async_group_begin.htm | 5 +++-- .../Note_directory_depends_on_platform.hts | 14 ++++++++++++++ 2 files changed, 17 insertions(+), 2 deletions(-) create mode 100644 Manual/contents/assets/snippets/Note_directory_depends_on_platform.hts diff --git a/Manual/contents/GameMaker_Language/GML_Reference/Buffers/buffer_async_group_begin.htm b/Manual/contents/GameMaker_Language/GML_Reference/Buffers/buffer_async_group_begin.htm index 4f9ff7c81..436de7b13 100644 --- a/Manual/contents/GameMaker_Language/GML_Reference/Buffers/buffer_async_group_begin.htm +++ b/Manual/contents/GameMaker_Language/GML_Reference/Buffers/buffer_async_group_begin.htm @@ -17,7 +17,8 @@

buffer_async_group_begin

This function is called when you want to begin the saving out of multiple buffers to multiple files (or loading multiple buffers).

The groupname is a string and will be used as the directory name for where the files are saved, and should be used as part of the file path when loading the files back from outside an async group (using any of the buffer_load functions). This function is only for use with the buffer_save_async and buffer_load_async functions and you must also end the async group by calling buffer_async_group_end function otherwise the files will not be saved/loaded.

-

 For the console platforms (like PS4 for example), the groupname will be used as the save slot description, and using this function can help you avoid having the UI show for every file that is being saved out.

+
+

 For some console platforms (e.g. PlayStation), the groupname will be used as the save slot description, and using this function can help you avoid having the UI show for every file that is being saved out.

 

Syntax:

buffer_async_group_begin(groupname)

@@ -56,7 +57,7 @@

Example:

Next: buffer_async_group_option
-
© Copyright YoYo Games Ltd. 2024 All Rights Reserved
+
© Copyright YoYo Games Ltd. 2026 All Rights Reserved

audio_emitter_free

-

With this function you can remove the given emitter from memory. This should always be done whenever the emitter is not going to be used further in the room or the game, ie: in the Destroy Event of the instance or in the Room End Event, otherwise you may end up with a memory leak that will slow down and eventually crash your game.

+

With this function you can remove the given emitter from memory. This should always be done whenever the emitter is not going to be used further in the room or the game, i.e.: in the Clean Up Event of the instance or in the Room End Event, otherwise you may end up with a memory leak that will slow down and eventually crash your game.

+

Sound instances currently being played on the emitter are force-stopped.

+

 

Syntax:

audio_emitter_free(emitter)

@@ -28,7 +30,7 @@

Syntax:

emitter - Audio Emitter ID + Audio Emitter ID The index of the emitter to free. @@ -38,12 +40,12 @@

Returns:

N/A

 

Example:

-

if (lives == 0)
+

if (lives == 0)
{
    audio_emitter_free(s_emit);
-     room_goto(rm_Menu);
+     room_goto(rm_menu);
}

-

The above code checks the value of the global variable "lives" and if it returns 0, it will destroy the emitter indexed in the variable "s_emit" and then go to the room indexed in the variable "rm_Menu".

+

The above code checks the value of the global variable "lives" and if it returns 0, it will destroy the emitter indexed in the variable "s_emit" and then go to the room indexed in the variable "rm_menu".

 

 

 

@@ -54,7 +56,7 @@

Example:

Next: audio_play_sound_on
-
© Copyright YoYo Games Ltd. 2022 All Rights Reserved
+
© Copyright YoYo Games Ltd. 2026 All Rights Reserved

cache_directory

-

This function returns the cache directory for your game. Use this directory to store cached data that is not permanently needed for your game.

+

This variable holds the path to the cache directory for your game. Use this directory to store cached data that is not permanently needed for your game.

On some consoles, certain options may need to be enabled for this to hold a valid path.

 

@@ -33,11 +33,11 @@

Example:

-
Back: File Directories
+
Back: File Directories
Next: directory_exists
-
© Copyright YoYo Games Ltd. 2024 All Rights Reserved
+
© Copyright YoYo Games Ltd. 2026 All Rights Reserved

program_directory

-

This function returns the directory where the game's runner (executable) is stored. However, this may not always be useful, particularly as some devices run the executable from a *.zip file, so this would return that location no matter where the extracted executable is actually running from.

+

This variable holds the path to the directory where the game's runner (executable) is stored. However, this may not always be useful, particularly as some devices run the executable from a *.zip file, so this would return that location no matter where the extracted executable is actually running from.

This is different from working_directory, which stores where the game's files are stored, however by default they are in the same location.

@@ -39,7 +39,7 @@

Example:

Next: cache_directory
-
© Copyright YoYo Games Ltd. 2024 All Rights Reserved
+
© Copyright YoYo Games Ltd. 2026 All Rights Reserved

temp_directory

-

This function returns the temporary directory created for your game each time it is run.

+

This variable holds the path to the temporary directory created for your game each time it is run.

This directory will hold files and can be accessed while the game is running, but it will be removed (along with all files that it contains) when the game is closed.

 

@@ -33,11 +33,11 @@

Example:

-
Back: File Directories
-
Next: working_directory
+
Back: File Directories
+
Next: working_directory
-
© Copyright YoYo Games Ltd. 2023 All Rights Reserved
+
© Copyright YoYo Games Ltd. 2026 All Rights Reserved

working_directory

-

This returns a path that points to where the game's files are stored.

-

In most cases, this is the same as the program_directory, which is the path to the game's runner (executable). However if the game's files happen to be in a different directory than the runner (say you use game_change to use a different working directory or use command line to run a runner in a different location), then this will point to where the game files are, not the runner.

+

This variable holds the path that points to where the game's files are stored.

+

In most cases, this is the same as the program_directory, which is the path to the game's runner (executable). However, if the game's files happen to be in a different directory than the runner (say you use game_change to use a different working directory or use command line to run a runner in a different location), then this will point to where the game files are, not the runner.

It may also be a different directory when testing your project through the IDE, as then the game files and the runner are in different locations as well.

When using this directory to write out a file, GameMaker will redirect it to the game_save_id location if the file system sandbox does not allow writing to the working directory (this is the default behaviour, which can be disabled in the Game Options for Desktop targets only).

@@ -37,11 +37,11 @@

Example:

-
Back: File Directories
-
Next: program_directory
+
Back: File Directories
+
Next: program_directory
-
© Copyright YoYo Games Ltd. 2023 All Rights Reserved
+
© Copyright YoYo Games Ltd. 2026 All Rights Reserved

Welcome to the GameMaker user manual! This document is divided into three parts with the aim of getting you introduced to the interface and basic workings of GameMaker and general programming, before going on to more advanced usage and the functions available through our proprietary programming language GML (GameMaker Language).

To ease you into things we have created a handy Quick Start Guide, and even if you are familiar with other game creation tools we recommend that you start there to get an overview of the way that GameMaker works. You'll find GameMaker to be easy and intuitive to use, and whatever your skill level, you will soon be making games you've always dreamt of.

-

 Due to the modular nature of GameMaker there are certain things that are not included in this user manual, in particular those aspects of setting up and connecting the different devices that can be supported. For up-to-date information and troubleshooting hints and tips related to the different target platforms, please see the GameMaker Wiki and GameMaker Help Center (for legacy information).

+

 Due to the modular nature of GameMaker there are certain things that are not included in this user manual, in particular those aspects of setting up and connecting the different devices that can be supported. For up-to-date information and troubleshooting hints and tips related to the different target platforms, please see the GameMaker Wiki and GameMaker Help Center (for legacy information and help articles).

 Returning to the manual? Here are some handy shortcuts:

-
© Copyright YoYo Games Ltd. 2025 All Rights Reserved
+
© Copyright YoYo Games Ltd. 2026 All Rights Reserved

working_directory

-

This variable holds the path that points to where the game's files are stored.

+

This variable holds the path to the directory where the game's files are stored.

In most cases, this is the same as the program_directory, which is the path to the game's runner (executable). However, if the game's files happen to be in a different directory than the runner (say you use game_change to use a different working directory or use command line to run a runner in a different location), then this will point to where the game files are, not the runner.

It may also be a different directory when testing your project through the IDE, as then the game files and the runner are in different locations as well.

When using this directory to write out a file, GameMaker will redirect it to the game_save_id location if the file system sandbox does not allow writing to the working directory (this is the default behaviour, which can be disabled in the Game Options for Desktop targets only).

From a0afa5b4bb71c2f38fee9c085ad3364188de4170 Mon Sep 17 00:00:00 2001 From: Gurpreet Singh Matharoo Date: Fri, 6 Feb 2026 11:17:54 +0530 Subject: [PATCH 017/108] docs(general): Document the implicit calls to method() https://github.com/YoYoGames/GameMaker-Bugs/issues/13544 --- .../GML_Reference/Variable_Functions/method.htm | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Manual/contents/GameMaker_Language/GML_Reference/Variable_Functions/method.htm b/Manual/contents/GameMaker_Language/GML_Reference/Variable_Functions/method.htm index 6aa0db717..72063b850 100644 --- a/Manual/contents/GameMaker_Language/GML_Reference/Variable_Functions/method.htm +++ b/Manual/contents/GameMaker_Language/GML_Reference/Variable_Functions/method.htm @@ -20,6 +20,7 @@

method

You supply the instance ID to use (an instance that is active in the room, and not an object index) or a struct reference, as well as the function ID (or method reference) that you want to bind. The function will return a new method which can be called from the variable it is assigned to (see the code example below).

The returned method will be "bound" to the given instance or struct, meaning it will always execute in the scope of that instance/struct.

You can bind built-in functions as well as user-defined functions/methods, and you can also supply undefined as the instance/struct argument meaning that the current self scope will be used for the binding.

+

 The method function is implicitly called when defining new Method Variables (to assign the new function to self) and when defining new struct and array literals. Due to this, you may see extra calls to the method function in The Debugger in addition to any explicit calls, which are made implicitly to define the aforementioned resources.

 

Syntax:

method(struct_ref_or_instance_id, func)

@@ -62,7 +63,7 @@

Example:

Next: method_get_self
-
© Copyright YoYo Games Ltd. 2024 All Rights Reserved
+
© Copyright YoYo Games Ltd. 2026 All Rights Reserved

Guide To Using Shaders

Shaders are often used to create beautiful graphical effects in games. They are also among the most advanced features offered by GameMaker, so it is necessary that you have a basic understanding of programming and how GameMaker works before getting started with them.

-

So, what is a shader? Initially they were created to provide shading for lighting (hence the name), but they are now used to produce a huge variety of effects. Shader code is similar to regular code, but it is (almost always) executed by the GPU, not the CPU. This difference comes with its own set of rules and limitations, but we’ll cover those later.

-

Each shader is made up of two separate components: a vertex shader and a fragment shader (also referred to as pixel shader). Let’s start with the vertex shader. Each sprite is formed by a rectangle, but computers like to draw triangles, so those rectangles are split into two triangles (sometimes called a quad). This leaves us with six vertices (corners) per sprite, but two of those are the same one, so we should only worry about four. Now, imagine we have a for loop that goes over every vertex and executes the code inside the vertex shader for each. This allows us to change the vertex position and color before passing it over to the fragment shader since the vertex shader is executed earlier.

-

Here’s how that would look:

-

Shader VerticesFor the fragment shader, you can imagine the same loop as before, but this time it goes over every single pixel in your sprite, giving you information such as location and color of that pixel. In your fragment shader code, you perform operations and calculations to determine the color of that pixel to get the effect you want. For example, if you want a shader to make your sprite be black and white, then you’d calculate which shade of grey each pixel needs to be to create the effect.

+

So, what is a shader? Initially they were created to provide shading for lighting (hence the name), but they are now used to produce a huge variety of effects. Shader code is similar to regular code, but it is (almost always) executed by the GPU, not the CPU. This difference comes with its own set of rules and limitations, but we'll cover those later.

+

Each shader is made up of two separate components: a vertex shader and a fragment shader (also referred to as pixel shader). Let's start with the vertex shader. Each sprite is formed by a rectangle, but computers like to draw triangles, so those rectangles are split into two triangles (sometimes called a quad). This leaves us with six vertices (corners) per sprite, but two of those are the same one, so we should only worry about four. Now, imagine we have a for loop that goes over every vertex and executes the code inside the vertex shader for each. This allows us to change the vertex position and color before passing it over to the fragment shader since the vertex shader is executed earlier.

+

Here's how that would look:

+

Shader VerticesFor the fragment shader, you can imagine the same loop as before, but this time it goes over every single pixel in your sprite, giving you information such as location and color of that pixel. In your fragment shader code, you perform operations and calculations to determine the color of that pixel to get the effect you want. For example, if you want a shader to make your sprite be black and white, then you'd calculate which shade of grey each pixel needs to be to create the effect.

It would look something like this:

-

Shader FragmentsThe reason shader code is usually executed by the GPU is that it is more efficient at it. Modern CPUs typically have between two to eight cores. Each core can perform one task at a time, so by taking advantage of multiple cores, we can perform that many tasks simultaneously. In contrast, modern GPUs can perform thousands, and even tens of thousands, of tasks running at the same time. This is helpful for shaders because we can execute the shader code of thousands of pixels concurrently. The limitation is that we only have access to the initial state of the sprite, so we don’t know about any modifications done to other pixels since we can’t know for sure the code has run on them yet.

-

 GameMaker allows users to write shaders in GLSL (OpenGL Shader Language), HLSL (High-level Shader Language, used when working with DirectX), and GLSL ES (a subset of GLSL which is common in mobile devices). Here we are using GLSL ES as the shader language since it’s the one that provides the best compatibility across target platforms. Generally this is the one you always want to use unless you have very specific needs and understand the limitation of the other shader languages. The math and techniques should be similar between all three languages however, save for a few syntax differences here and there.

-

The vertex shader is executed first, and as we explained above, it deals with vertices. It is used to calculate positions, normals, and texture coordinates. These shaders are not particularly useful in 2D, since every sprite is usually a square, but it can be used to do some skewing, scaling, etc... It becomes much more useful in 3D for lighting calculations and mesh deformations. Fragment shaders are much more interesting and are what will be covered mostly here, since the fragment shader is where we get information about our textures and can tweak the final color of each pixel in our image.

+

Shader FragmentsThe reason shader code is usually executed by the GPU is that it is more efficient at it. Modern CPUs typically have between two to eight cores. Each core can perform one task at a time, so by taking advantage of multiple cores, we can perform that many tasks simultaneously. In contrast, modern GPUs can perform thousands, and even tens of thousands, of tasks running at the same time. This is helpful for shaders because we can execute the shader code of thousands of pixels concurrently. The limitation is that we only have access to the initial state of the sprite, so we don't know about any modifications done to other pixels since we can't know for sure the code has run on them yet.

+

 GameMaker allows users to write shaders in GLSL (OpenGL Shader Language), HLSL (High-level Shader Language, used when working with DirectX), and GLSL ES (a subset of GLSL which is common in mobile devices). Here we are using GLSL ES as the shader language since it's the one that provides the best compatibility across target platforms. Generally, this is the one you always want to use unless you have very specific needs and understand the limitation of the other shader languages. The math and techniques should be similar between all three languages however, save for a few syntax differences here and there.

+

The vertex shader is executed first, and as we explained above, it deals with vertices. It is used to calculate positions, normals, and texture coordinates. These shaders are not particularly useful in 2D, since every sprite is usually a square, but it can be used to do some skewing, scaling, etc. It becomes much more useful in 3D for lighting calculations and mesh deformations. Fragment shaders are much more interesting and are what will be covered mostly here, since the fragment shader is where we get information about our textures and can tweak the final color of each pixel in our image.

 

Shader Variables

-

If you have created a shader in GameMaker, you might have noticed the following keywords in the default pass-through shader. These keywords help the shader understand the purpose and scope of each variable:

+

If you have created a shader in GameMaker, you might have noticed the following keywords in the default passthrough shader. These keywords help the shader understand the purpose and scope of each variable:

-

You'll also see the use of vec as a keyword. This is used to identify a vector variable in the shader and you'll soon see that vectors are very important when working with shaders. That is why they are implemented as a base type in GLSL. If you are unfamiliar with them, they are a mathematical term represented as a matrix with only one column. In programming, we usually represent them as an array where the number of components corresponds to the dimension. Two and three-dimensional vectors are often used for positions, texture coordinates, or colors without an alpha channel, while four-dimensional ones are used for colors with an alpha channel. We can also specify if they hold booleans, integers, or floating point values. The syntax to declare a vector is this:

+

You'll also see the use of vec as a keyword. This is used to identify a vector variable in the shader and you'll soon see that vectors are very important when working with shaders. That is why they are implemented as a base type in GLSL. If you are unfamiliar with them, they are a mathematical term represented as a matrix with only one column. In programming, we usually represent them as an array where the number of components corresponds to the dimension. Two and three-dimensional vectors are often used for positions, texture coordinates, or colors without an alpha channel, while four-dimensional ones are used for colors with an alpha channel. We can also specify if they hold booleans, integers, or floating point values. The syntax to declare a vector is this:

vec2 firstVec;  // Two-dimensional vector of floats
vec3 secondVec; // Three-dimensional vector of floats
vec4 thirdVec;  // Four-dimensional vector of floats
@@ -62,21 +62,21 @@

Shader Variables

vec4 myVec;
myVec.x = 0.0;
myVec.y = 1.0;

-

This uses the component names inside the vector to access them. You can use x, y, z, or w, to get the first, second, third, or fourth components, respectively. We refer to this method as swizzling because the following syntax is also valid:

+

This uses the component names inside the vector to access them. You can use x, y, z, or w, to get the first, second, third, or fourth components, respectively. We refer to this method as swizzling because the following syntax is also valid:

vec4 firstVec;
vec3 secondVec = firstVec.xyz;
vec2 thirdVec  = secondVec.zy;
vec4 fourthVec = thirdVec.yxxy;

-

As you can see, we can use any combination of up to four letters to create a vector of that length. We cannot attempt to access a component that would be out of bounds (for example, trying to access w in secondVec or thirdVec, since they don’t have a fourth component). Also, we can repeat letters and use them in any order, as long as the vector variable it’s being assigned to is the same size as the number of letters used.

-

For obvious reasons, when using swizzle to set component values, you can’t use the same component twice. For example, the below is not valid as you are trying to set the same component to two different values:

+

As you can see, we can use any combination of up to four letters to create a vector of that length. We cannot attempt to access a component that would be out of bounds (for example, trying to access w in secondVec or thirdVec, since they don't have a fourth component). Also, we can repeat letters and use them in any order, as long as the vector variable it's being assigned to is the same size as the number of letters used.

+

For obvious reasons, when using swizzle to set component values, you can't use the same component twice. For example, the below is not valid as you are trying to set the same component to two different values:

myVec.xx = vec2(2.0, 3.0);

-

Last, we have been using xyzw as our swizzle mask, which is usually the case when dealing with positions. There are two more sets of masks you can use: rgba (used for colors), or stpq (used for texture coordinates). Internally, there is no difference between these masks, and we only use them to make the code clearer as to what the vector represents in that instance. Also, we can’t combine swizzle masks in the same operation, so this is invalid:

+

Last, we have been using xyzw as our swizzle mask, which is usually the case when dealing with positions. There are two more sets of masks you can use: rgba (used for colors), or stpq (used for texture coordinates). Internally, there is no difference between these masks, and we only use them to make the code clearer as to what the vector represents in that instance. Also, we can't combine swizzle masks in the same operation, so this is invalid:

myVec = otherVec.ybp;

Those were a lot of definitions and information, but knowing these things is necessary to understand shaders themselves.

 

Creating A Shader

-

When you create a shader in GameMaker, it will open two files for you: a vertex shader (.vsh) and a fragment shader (.fsh). This is the most basic shader you can make, which takes a sprite, reads the texture, and colors each pixel with that color. If you specify vertex colors when drawing, those colors will blend with the texture.

-

Let’s go through the code for a newly created shader asset and analyze it, starting with the vertex shader.

+

When you create a shader in GameMaker, it will open two files for you: a vertex shader (.vsh) and a fragment shader (.fsh). This is the most basic shader you can make, which takes a sprite, reads the texture, and colors each pixel with that color. If you specify vertex colors when drawing, those colors will blend with the texture.

+

Let's go through the code for a newly created shader asset and analyze it, starting with the vertex shader.

// Passthrough Vertex Shader
attribute vec3 in_Position;                  // (x,y,z)
//attribute vec3 in_Normal;                  // (x,y,z)     unused in this shader.
@@ -95,14 +95,14 @@

Creating A Shader

    v_vTexcoord = in_TextureCoord;
}

-

Outside of the main function, we see some variable declarations and their qualifiers. The attributes are given to us by GameMaker. The varying ones are created by the user to pass that information over to the fragment shader. Inside the main function, we have the calculations to find the screen position of the vertex:

+

Outside of the main function, we see some variable declarations and their qualifiers. The attributes are given to us by GameMaker. The varying ones are created by the user to pass that information over to the fragment shader. Inside the main function, we have the calculations to find the screen position of the vertex:

This shader should be left alone if you are not planning to play with vertex positions and it will not be used in any of the examples given below because all the effects shown will be created using the fragment shader.

-

Let’s take a quick look at the fragment shader now:

+

Let's take a quick look at the fragment shader now:

// Passthrough Fragment Shader
varying vec2 v_vTexcoord;
varying vec4 v_vColour;
@@ -112,28 +112,28 @@

Creating A Shader

    gl_FragColor = v_vColour * texture2D( gm_BaseTexture, v_vTexcoord );
}

-

As explained before, the idea behind a fragment shader is to return the color of the current pixel. This is done by assigning the variable gl_FragColor the final color value. The texture2D function takes a texture and a vec2 with the UV coordinates you want to check in that texture, which returns a vec4 with the color. In the pass through shader, all we are doing is grabbing the color of the texture in the coordinate of this pixel and multiplying it by the color of the vertex associated with this pixel.

+

As explained before, the idea behind a fragment shader is to return the color of the current pixel. This is done by assigning the variable gl_FragColor the final color value. The texture2D function takes a texture and a vec2 with the UV coordinates you want to check in that texture, which returns a vec4 with the color. In the passthrough shader, all we are doing is grabbing the color of the texture at the coordinate of this pixel and multiplying it by the color of the vertex associated with this pixel.

Now that we have our first shader, all we have to do to test it is create an object and assign it a sprite, then in the Draw Event of the object you set the shader like this:

// Draw Event
shader_set(shdrColorOverlay);
draw_self();
shader_reset();

-

Every draw call we make between shader_set() and shader_reset() will have the shader applied to it. Here, we are drawing the object sprite with our passthrough shader:

-

Drawing Sprite Using Passthough ShaderAs you might have guessed, this does not visually changing anything, as this is a simple pass-through shader. However the sections below outline some simple steps you can take to modify this and change the way the sprite will be drawn. Each of the section shows a different shader that you can create and use in your projects, explaining the steps required to create them and why we are doing things the way we are.

+

Every draw call we make between shader_set and shader_reset will have the shader applied to it. Here, we are drawing the object sprite with our passthrough shader:

+

Drawing Sprite Using Passthough ShaderAs you might have guessed, this does not visually changing anything, as this is a simple passthrough shader. However, the sections below outline some simple steps you can take to modify this and change the way the sprite will be drawn. Each of the sections shows a different shader that you can create and use in your projects, explaining the steps required to create them and why we are doing things the way we are.

 

Colour Overlay Shader

-

We can edit the base shader now to do something different. We'll not be touching the vertex shader part, and only editing the fragment shader, and to start with we'll do a very simple operation, which is to make the shader draw the sprite using the colour red. We'll do this by simply changing the gl_FragColor to be red., like this:

+

We can edit the base shader now to do something different. We'll not be touching the vertex shader part, and only editing the fragment shader, and to start with we'll do a very simple operation, which is to make the shader draw the sprite using the colour red. We'll do this by simply changing the gl_FragColor to be red, like this:

// Color Overlay Fragment Shader
void main()
{
    gl_FragColor = vec4(1.0, 0.0, 0.0, 1.0);
}

This will give us the following result:

-

Initial Colour Overlay BlockNot exactly what we expected! What we need to remember is that every sprite is ultimately a rectangle, so unless we consider transparency - which we haven't - this is the result we’ll get.

-

 In the image above, the rectangle changes size because the base sprite has had the "empty" space around it cropped automatically when it was placed on the texture page by GameMaker, so each animation frame the triangles that make it up are different sizes to fit the cropped size of the frame. If you disable this option, then you'd simply have a motionless red square on the screen.

-

Above we mentioned the texture2D function, and we'll use that to grab the color at the pixel we are working on and get the transparency from it. The return value of is texture2D is a vec4, where the components are the red, green, blue, and alpha, in that order. We can access the alpha channel either by putting a period followed by an a or a w after the variable name. This corresponds to RGBA and XYZW, respectively.

-

Here’s the updated code:

+

Initial Colour Overlay BlockNot exactly what we expected! What we need to remember is that every sprite is ultimately a rectangle, so unless we consider transparency - which we haven't - this is the result we'll get.

+

 In the image above, the rectangle changes size because the base sprite has had the "empty" space around it cropped automatically when it was placed on the texture page by GameMaker, so each animation frame the triangles that make it up are different sizes to fit the cropped size of the frame. If you disable this option, then you'd simply have a motionless red square on the screen.

+

Above we mentioned the texture2D function, and we'll use that to grab the color at the pixel we are working on and get the transparency from it. The return value of texture2D is a vec4, where the components are the red, green, blue, and alpha, in that order. We can access the alpha channel either by putting a period followed by an a or a w after the variable name. This corresponds to RGBA and XYZW, respectively.

+

Here's the updated code:

// Color Overlay Fragment Shader
varying vec2 v_vTexcoord;

@@ -143,20 +143,20 @@

Creating A Shader

    gl_FragColor = vec4(1.0, 0.0, 0.0, texColor.a);
}

-

We are now assigning a new vec4 to gl_FragColor, where the red channel is maxed, the green, and blue channels are zero, and the alpha channel is the same as the original texture. The output looks like this:

-

Overlay Shader Making Sprite RedNow that’s what we were after! We have replaced the color of every pixel with red, but have kept the alpha channel intact.

-

Having to change the shader each time we want to use a different color isn’t a good idea, especially since we’d need to have a separate shader for each color we want. Instead, we will pass the color information to the shader using a uniform. To do this, we first need to get a pointer to the uniform. We will do this in the Create Event of our object that has the sprite by adding:

+

We are now assigning a new vec4 to gl_FragColor, where the red channel is maxed, the green and blue channels are zero, and the alpha channel is the same as the original texture. The output looks like this:

+

Overlay Shader Making Sprite RedNow that's what we were after! We have replaced the color of every pixel with red, but have kept the alpha channel intact.

+

Having to change the shader each time we want to use a different color isn't a good idea, especially since we'd need to have a separate shader for each color we want. Instead, we will pass the color information to the shader using a uniform. To do this, we first need to get a pointer to the uniform. We will do this in the Create Event of our object that has the sprite by adding:

// Create Event
_uniColor = shader_get_uniform(shdrColorOverlay, "u_colour");
_color    = [1.0, 1.0, 0.0, 1.0];

-

All we need to do is call shader_get_uniform() to get a pointer to the uniform. The parameters we need to pass are the shader asset name (without quotation because we want to pass the ID that GameMaker generates for us) and the name of the uniform variable inside of the shader, this time as a string. This name needs to match exactly the one inside the shader code for it to work. We have also added a colour variable so we can change it at runtime and have it remember our changes.

-

Now the code in our draw event will change slightly to pass the uniform variable.

+

All we need to do is call shader_get_uniform to get a pointer to the uniform. The parameters we need to pass are the shader asset name (without quotation because we want to pass the ID that GameMaker generates for us) and the name of the uniform variable inside of the shader, this time as a string. This name needs to match exactly the one inside the shader code for it to work. We have also added a colour variable so we can change it at runtime and have it remember our changes.

+

Now the code in our Draw event will change slightly to pass the uniform variable.

// Draw Event
shader_set(shdrColorOverlay);
shader_set_uniform_f_array(_uniColor, _color);
draw_self();
shader_reset();

-

It’s the same code as before, but before we draw anything, we need to pass all the uniform values to the shader. In this case, we are passing the color as an array of floats. As for the shader, we will change it to include the uniform and use it, so it becomes:

+

It's the same code as before, but before we draw anything, we need to pass all the uniform values to the shader. In this case, we are passing the color as an array of floats. As for the shader, we will change it to include the uniform and use it, so it becomes:

// Color Overlay Fragment Shader
varying vec2 v_vTexcoord;
uniform vec4 u_colour;
@@ -165,14 +165,14 @@

Creating A Shader

    vec4 texColor = texture2D(gm_BaseTexture, v_vTexcoord);
    gl_FragColor = vec4(u_colour.rgb, texColor.a);
}

-

We declare a variable with the same name as in the create shader (u_colour) and we pass it as the first three components of the gl_FragColor vector, taking advantage of swizzling. If we compile again, we should see this:

-

Overlay Shader Making Sprite YellowNow the shader is much more useful and reusable. It’s up to you to add more functionality if you need it to set the color (using the variable _color) during runtime.

+

We declare a variable with the same name as in the create shader (u_colour) and we pass it as the first three components of the gl_FragColor vector, taking advantage of swizzling. If we compile again, we should see this:

+

Overlay Shader Making Sprite YellowNow the shader is much more useful and reusable. It's up to you to add more functionality if you need it to set the color (using the variable _color) during runtime.

 

Black And White Shader

Making a black and white shader is a great way to learn more about how shaders work, and a lot of beginners start by trying to do this, since conceptually it's quite simple: get every pixel and assign it a shade of gray. But is it simple? Not quite...

-

When using RGB colour, if all three components are the same value, then we get a gray tone. The naïve approach to creating a shader to use this idea would be to add all three color channels (red, green, and blue) and then divide it by three. After that you'd assigned the value to all three channels, thus creating a gray tone. Here’s what that fragment shader looks like:

+

When using RGB colour, if all three components are the same value, then we get a gray tone. The naïve approach to creating a shader to use this idea would be to add all three color channels (red, green, and blue) and then divide it by three. After that you'd assigned the value to all three channels, thus creating a gray tone. Here's what that fragment shader looks like:

// Black and white fragment shader
varying vec2 v_vTexcoord;
varying vec4 v_vColour;
@@ -184,14 +184,14 @@

Creating A Shader

    gl_FragColor = v_vColour * vec4(gray, gray, gray, texColor.a);
}

-

One thing you might have noticed is that in the gl_FragColor code, we're multiplying the vec4 with something called v_vColour. This is a variable passed by the vertex shader which tells us the color of the vertex associated with this pixel. It’s always a good idea to multiply your final calculated color with the vertex color. In most cases, it won’t do anything, but if you changed the vertex color in GML, this will reflect that (by using functions such as draw_sprite_ext() or draw_sprite_general() to change the image_blend).

-

As for the draw event, it’s quite simple since we don’t have a uniform to pass in:

+

One thing you might have noticed is that in the gl_FragColor code, we're multiplying the vec4 with something called v_vColour. This is a variable passed by the vertex shader which tells us the color of the vertex associated with this pixel. It's always a good idea to multiply your final calculated color with the vertex color. In most cases, it won't do anything, but if you changed the vertex color in GML, this will reflect that (by using functions such as draw_sprite_ext or draw_sprite_general to change the image_blend).

+

As for the Draw event, it's quite simple since we don't have a uniform to pass in:

// Draw Event
shader_set(shdrBlackAndWhite);
draw_self();
shader_reset();

-

Let’s compile and see what we got.

-

Black And White ShaderThis looks great already, right? Well, yes and no... there is a solution that is more “correct”, since instead of adding the components and dividing by three, we multiply each component by the standard NTSC values for black and white. Here’s the modified fragment shader code:

+

Let's compile and see what we got.

+

Black And White ShaderThis looks great already, right? Well, yes and no... there is a solution that is more "correct", since instead of adding the components and dividing by three, we multiply each component by the standard NTSC values for black and white. Here's the modified fragment shader code:

// Black and white fragment shader
varying vec2 v_vTexcoord;

@@ -202,17 +202,17 @@

Creating A Shader

    gl_FragColor = vec4(gray, gray, gray, texColor.a);
}

-

We use the dot product as a shorthand for multiplying each component of texColor with the correct weights and then add them together. If you are unfamiliar with the dot product, this is essentially what’s happening:

+

We use the dot product as a shorthand for multiplying each component of texColor with the correct weights and then add them together. If you are unfamiliar with the dot product, this is essentially what's happening:

float gray = (texColor.r * 0.299) + (texColor.g * 0.587) + (texColor.b * 0.114);

-

In the end, it looks very similar, but it’s technically more correct.

+

In the end, it looks very similar, but it's technically more correct.

Corrected Black And White Shader

 

Rainbow Shader

Our final shader example is a fun one and can be used to add life to text and buttons and other things. We'll start simple and add functionality gradually since this shader is highly customizable. There's quite a lot to cover for this one, so if you feel a bit lost or confused, please go back and re-read some of the sections above.

-

The first thing we want to do is color pixels with every hue, depending on the pixel’s horizontal position. The way to do this is to set the x position to be the hue and then convert from HSV (hue, saturation, brightness) format to RGB (red, green, and blue) format. For this, we will need to write a helper function in our fragment shader that takes HSV values and returns an RGB vector. We will use a single function which does this without the need for any if statements, as using conditionals in shader code makes shaders very slow, and should be avoided.

-

Here’s what the shader looks like at this stage:

+

The first thing we want to do is color pixels with every hue, depending on the pixel's horizontal position. The way to do this is to set the x position to be the hue and then convert from HSV (hue, saturation, brightness) format to RGB (red, green, and blue) format. For this, we will need to write a helper function in our fragment shader that takes HSV values and returns an RGB vector. We will use a single function which does this without the need for any if statements, as using conditionals in shader code makes shaders very slow, and should be avoided.

+

Here's what the shader looks like at this stage:

// Fragment Shader
varying vec2 v_vTexcoord;
varying vec4 v_vColour;
@@ -231,25 +231,25 @@

Creating A Shader

    gl_FragColor = v_vColour * vec4(hsv2rgb(col), alpha);
}

-

There's a bit more going on here than in the previous examples, but most of it should be fairly obvious to you now. First, there’s our hsv2rgb function, which takes a vec3 with our HSV colour and returns another vec3 with our RGB conversion. In the main function, we start by creating our HSV colour, where the hue is our x position, and we’ll leave the saturation and brightness as 1.0 for now. Then, we get the alpha from the texture so it only colors our sprite character and not the entire sprite rectangle (as we did in the colour overlay example, above). Lastly, we set our Fragment color to be our HSV color converted to RGB with the alpha, multiplied by the vertex color (good practice to do this always).

+

There's a bit more going on here than in the previous examples, but most of it should be fairly obvious to you now. First, there's our hsv2rgb function, which takes a vec3 with our HSV colour and returns another vec3 with our RGB conversion. In the main function, we start by creating our HSV colour, where the hue is our x position, and we'll leave the saturation and brightness as 1.0 for now. Then, we get the alpha from the texture so it only colors our sprite character and not the entire sprite rectangle (as we did in the colour overlay example, above). Lastly, we set our Fragment color to be our HSV color converted to RGB with the alpha, multiplied by the vertex color (good practice to do this always).

As for our draw code, it is trivial at the moment:

// Draw Event
shader_set(shdrRainbow);
draw_self();
shader_reset();

-

Let’s check out what we got:

-

Initial Rainbow ShaderWe are close to what we want, but there’s an issue: we are not seeing all the colors at once in every frame of the animation, and the colors seem to change randomly. The reason is that we assumed that v_vTexcoord gave us the coordinates of the sprite, starting at the top-left corner (0,0) and ending in the bottom right corner (1,1), which is standard in shaders. However, for optimization, GameMaker stuffs as many textures together as it can fit in what is called a texture page, and because of that, this is how our texture actually looks:

-

As explained above, v_vTexcoord gives us the absolute coordinates of the sprite within this entire texture page, but what we want is a value from 0.0 to 1.0 that only covers our current sprite. This process is called normalizing (getting a value and translating it to a 0 to 1 range). To normalize our horizontal values, we need to know the values of x0 and x1 in the picture above. Luckily, GameMaker has a function that gives us the location of every corner in our sprite within the texture page. First, we need to go to the Create Event and create a uniform to pass this data over to the shader:

+

Let's check out what we got:

+

Initial Rainbow ShaderWe are close to what we want, but there's an issue: we are not seeing all the colors at once in every frame of the animation, and the colors seem to change randomly. The reason is that we assumed that v_vTexcoord gave us the coordinates of the sprite, starting at the top-left corner (0, 0) and ending in the bottom-right corner (1, 1), which is standard in shaders. However, for optimization, GameMaker stuffs as many textures together as it can fit in what is called a texture page, and because of that, this is how our texture actually looks:

+

As explained above, v_vTexcoord gives us the absolute coordinates of the sprite within this entire texture page, but what we want is a value from 0.0 to 1.0 that only covers our current sprite. This process is called normalizing (getting a value and translating it to a 0 to 1 range). To normalize our horizontal values, we need to know the values of x0 and x1 in the picture above. Luckily, GameMaker has a function that gives us the location of every corner in our sprite within the texture page. First, we need to go to the Create Event and create a uniform to pass this data over to the shader:

// Create Event
_uniUV = shader_get_uniform(shdrRainbow, "u_uv");

-

And we modify the draw event to get the values and then pass them to the shader:

+

And we modify the Draw event to get the values and then pass them to the shader:

// Draw Event
shader_set(shdrRainbow);
var uv = sprite_get_uvs(sprite_index, image_index);
shader_set_uniform_f(_uniUV, uv[0], uv[2]);
draw_self();
shader_reset();

-

The function sprite_get_uvs() takes a sprite and an index, and it returns an array with tons of information, such as the coordinates for each corner, how many pixels were cropped to optimize it, etc. We are interested in two of those values: the left and right coordinates of the sprite, which are stored in uv[0] and uv[2] respectively. In the fragment shader, we will use those values now to calculate the normalized horizontal position like this:

+

The function sprite_get_uvs takes a sprite and an index, and it returns an array with tons of information, such as the coordinates for each corner, how many pixels were cropped to optimize it, etc. We are interested in two of those values: the left and right coordinates of the sprite, which are stored in uv[0] and uv[2] respectively. In the fragment shader, we will use those values now to calculate the normalized horizontal position like this:

// Fragment Shader
varying vec2 v_vTexcoord;
varying vec4 v_vColour;
@@ -271,7 +271,7 @@

Creating A Shader

    gl_FragColor = v_vColour * vec4(hsv2rgb(col), alpha);
}

-

Here we add the uniform variable at the top of the file with the same name we used in the Create Event. Next, we calculate the normalized horizontal position by translating our current x coordinate to the origin ( v_vTexcoord.x - u_uv[0]) and then we divide it by the width of the sprite to make the range from 0 to 1 (u_uv[1] - u_uv[0]).

+

Here we add the uniform variable at the top of the file with the same name we used in the Create Event. Next, we calculate the normalized horizontal position by translating our current x coordinate to the origin ( v_vTexcoord.x - u_uv[0]) and then we divide it by the width of the sprite to make the range from 0 to 1 (u_uv[1] - u_uv[0]).

The result is:

Rainbow Overlay Shader ImprovedThere we go! This is exactly what we wanted. We can see every color of the spectrum inside our sprite.

You might be happy with that, but we can have some more fun with this shader. What if we added an offset to the colors based around time to produce movement? To do this, we will need two extra variables for speed and time. We will also need two more uniforms, one for each of the new variables, so the Create Event becomes:

@@ -284,7 +284,7 @@

Creating A Shader

We also need to increase the time every frame, so in the Step Event we add:

// Step Event
_time += 1 / game_get_speed(gamespeed_fps);

-

Let’s go to the draw event now to send these uniforms to the shader:

+

Let's go to the Draw event now to send these uniforms to the shader:

// Draw Event
shader_set(shdrRainbow);
var uv = sprite_get_uvs(sprite_index, image_index);
@@ -318,7 +318,7 @@

Creating A Shader

}

If you did everything correctly, you should be seeing something like this:

-

Rainbow Shader Overlay Moving With TimeTo finish this shader, we will add a few more uniforms to customize it even further. The first two are to control the saturation and brightness. The next one we'll call "section" and its function is to allow the user to pass a number between zero and one to determine what percentage of the entire spectrum we see at a time. Last, we will add a variable called "mix", which will specify how much we want to mix our shader color with the original texture color (1.0 is all rainbow, 0.0 is all texture). As always, let’s start by adding the variables to the Create Event:

+

Rainbow Shader Overlay Moving With TimeTo finish this shader, we will add a few more uniforms to customize it even further. The first two are to control the saturation and brightness. The next one we'll call "section" and its function is to allow the user to pass a number between zero and one to determine what percentage of the entire spectrum we see at a time. Last, we will add a variable called _mix, which will specify how much we want to mix our shader color with the original texture color (1.0 is all rainbow, 0.0 is all texture). As always, let's start by adding the variables to the Create Event:

// Create Event
_uniUV         = shader_get_uniform(shdrRainbow, "u_uv");
_uniTime       = shader_get_uniform(shdrRainbow, "u_time");
@@ -335,7 +335,7 @@

Creating A Shader

_brightness = 0.8;
_mix = 0.5;

-

Our draw event changes to include these uniforms like this:

+

Our Draw event changes to include these uniforms like this:

// Draw Event
shader_set(shdrRainbow);
var uv = sprite_get_uvs(sprite_index, image_index);
@@ -384,14 +384,14 @@

Creating A Shader

 

 

-

That's the end of this short guide and you should now have a better understanding of how shaders work and some of the uses they can be put to. You should take your time to play with the shaders you've created following this guide, and try to experiment with them do other things - how about creating a blur shader, or a shader that makes a gameboy-style monochrome screen? - since shaders are an incredibly powerful tool for adding visual complexity and style to your games.

+

That's the end of this short guide. You should now have a better understanding of how shaders work and some of the uses they can be put to. You should take your time to play with the shaders you've created following this guide, and try to experiment with them to do other things - how about creating a blur shader, or a shader that makes a Game Boy-style monochrome screen? - since shaders are an incredibly powerful tool for adding visual complexity and style to your games.

We would like to thank Alejandro Hitti and Amazon for permitting us to reproduce this guide. You can find the original version on the Amazon Developer Blog.

 

- - + +
© Copyright YoYo Games Ltd. 2026 All Rights Reserved
From 77df9ce6b5f9d667fa95d286913a652dcd5788db Mon Sep 17 00:00:00 2001 From: Gurpreet Singh Matharoo Date: Mon, 9 Feb 2026 12:54:42 +0530 Subject: [PATCH 026/108] docs(feature): Fix page titles for 'Debugging' pages and index keywords https://github.com/YoYoGames/GameMaker-Bugs/issues/13927 --- .../GML_Reference/Debugging/Debugging.htm | 8 ++++---- Manual/contents/Introduction/Debugging.htm | 6 +++--- .../IDE_Preferences/General/Debugging.htm | 4 ++-- Manual/toc/Default.toc | 2 +- 4 files changed, 10 insertions(+), 10 deletions(-) diff --git a/Manual/contents/GameMaker_Language/GML_Reference/Debugging/Debugging.htm b/Manual/contents/GameMaker_Language/GML_Reference/Debugging/Debugging.htm index b80dba7c4..43b68d358 100644 --- a/Manual/contents/GameMaker_Language/GML_Reference/Debugging/Debugging.htm +++ b/Manual/contents/GameMaker_Language/GML_Reference/Debugging/Debugging.htm @@ -3,18 +3,18 @@ - Debugging + Debugging Functions - + -

Debugging

+

Debugging Functions

While making a game, it is often very important that you know certain details of the game mechanics at specific points in time, or to be able to input certain key values for some functions to test out different methods and ideas for your game.

GameMaker provides the following functionality for this: 

-
© Copyright YoYo Games Ltd. 2024 All Rights Reserved
+
© Copyright YoYo Games Ltd. 2026 All Rights Reserved
-

Debugging

+

Debugging In GameMaker

When programming your game, whether using GML Code or GML Visual, it can be very easy to make mistakes - using the wrong variables, passing the wrong arguments, or using the wrong functions are just some of the most common errors we all make - and these mistakes are not always detected by the syntax checker that is included with the script/action editor. That means that these mistakes will only become apparent when you actually run or compile your game, and even then it can sometimes be difficult to know exactly what is going wrong. It can therefore be of vital importance to know how your game is performing on the chosen device, as well as see what instances are in the room, what global variables have been created and a whole host of other details. Checking these things is called "debugging your code", and any errors or issues you may find are called "bugs".

Now, you can check a lot of these things yourself by adding in so-called "debug code" to your games to display on the screen the information you require, or you can have it that it shows messages when there is an error, but this is often a lot of work and if you aren't sure where the problem is in the first place then it can be a time consuming case of trial and error to track down your bug. For that, GameMaker has a special test mode called Debug Mode which will start the Debugger, and there is also a comprehensive error reporting system which displays messages on Compiling to help you track down any problems with your game.

The sections below cover the different ways that you can debug your game:

@@ -61,7 +61,7 @@

Debugging

Next: The Output Window
-
© Copyright YoYo Games Ltd. 2025 All Rights Reserved
+
© Copyright YoYo Games Ltd. 2026 All Rights Reserved
-
Next: Introduction To GameMaker
+
Next: Introduction To GameMaker
+
Licenses
-
© Copyright YoYo Games Ltd. 2025 All Rights Reserved
+
© Copyright YoYo Games Ltd. 2026 All Rights Reserved
+ + + \ No newline at end of file diff --git a/Manual/toc/Default.toc b/Manual/toc/Default.toc index eb8fb2c0c..393e36ac1 100644 --- a/Manual/toc/Default.toc +++ b/Manual/toc/Default.toc @@ -3220,6 +3220,7 @@ + From 0948cce109bd88bb43c3401b5927a4107c3bbbdd Mon Sep 17 00:00:00 2001 From: Gurpreet Singh Matharoo Date: Tue, 17 Feb 2026 17:48:33 +0530 Subject: [PATCH 035/108] docs(feature): Update GMPM prefs https://github.com/YoYoGames/YoYoStudio/issues/12611 --- .../Package_Manager_Preferences.htm | 8 +++----- .../Preferences/PackageManager_Prefs.png | Bin 45970 -> 39151 bytes 2 files changed, 3 insertions(+), 5 deletions(-) diff --git a/Manual/contents/Setting_Up_And_Version_Information/IDE_Preferences/Package_Manager_Preferences.htm b/Manual/contents/Setting_Up_And_Version_Information/IDE_Preferences/Package_Manager_Preferences.htm index 180a180ad..0c055e27a 100644 --- a/Manual/contents/Setting_Up_And_Version_Information/IDE_Preferences/Package_Manager_Preferences.htm +++ b/Manual/contents/Setting_Up_And_Version_Information/IDE_Preferences/Package_Manager_Preferences.htm @@ -20,16 +20,14 @@

Package Manager PreferencesThis contains preferences for the Package Manager:

  • Packages Install Directory: The directory where packages are installed. The GMRT Preferences should be set to look in this directory.
    • -
  • Default Source URL: The default package source.
    • -
  • Remote Search Endpoint: This specifies the URL endpoint of the given registry domain for package searches. This differs between registries. For example: +
  • Default Source URL: This is the default package source URL to use when a new Package Source is added in the Package Manager
    • +
  • Remote Search Endpoint: This is the default "scopes" option used when a new Package Source is added. This differs between registries. For example:
    • -
  • NPM Path: Optional, if you want to use your own version of NPM.
    • -
  • Node Path: Optional, if you want to use your own version of Node.js.
  • Default Package Source: The package source that opens by default when you open the Package Manager.

 

@@ -42,7 +40,7 @@

Package Manager PreferencesNext: General Preferences -
© Copyright YoYo Games Ltd. 2025 All Rights Reserved
+
© Copyright YoYo Games Ltd. 2026 All Rights Reserved
@@ -72,7 +73,7 @@

Starting A New Project

-
© Copyright YoYo Games Ltd. 2025 All Rights Reserved
+
© Copyright YoYo Games Ltd. 2026 All Rights Reserved
@@ -49,7 +50,7 @@

GameMaker IDE

-
© Copyright YoYo Games Ltd. 2024 All Rights Reserved
+
© Copyright YoYo Games Ltd. 2026 All Rights Reserved
diff --git a/Manual/contents/GameMaker_Language/GML_Reference/Debugging/dbg_colour.htm b/Manual/contents/GameMaker_Language/GML_Reference/Debugging/dbg_colour.htm index a6ef53008..f0904d000 100644 --- a/Manual/contents/GameMaker_Language/GML_Reference/Debugging/dbg_colour.htm +++ b/Manual/contents/GameMaker_Language/GML_Reference/Debugging/dbg_colour.htm @@ -6,25 +6,12 @@ dbg_colour - + diff --git a/Manual/contents/GameMaker_Language/GML_Reference/Drawing/Particles/Particle_Systems/part_system_colour.htm b/Manual/contents/GameMaker_Language/GML_Reference/Drawing/Particles/Particle_Systems/part_system_colour.htm index 6f8196a9f..c9b3c2740 100644 --- a/Manual/contents/GameMaker_Language/GML_Reference/Drawing/Particles/Particle_Systems/part_system_colour.htm +++ b/Manual/contents/GameMaker_Language/GML_Reference/Drawing/Particles/Particle_Systems/part_system_colour.htm @@ -7,23 +7,11 @@ diff --git a/Manual/contents/GameMaker_Language/GML_Reference/Drawing/Surfaces/surface_reset_target.htm b/Manual/contents/GameMaker_Language/GML_Reference/Drawing/Surfaces/surface_reset_target.htm index 8661a112e..921a9b426 100644 --- a/Manual/contents/GameMaker_Language/GML_Reference/Drawing/Surfaces/surface_reset_target.htm +++ b/Manual/contents/GameMaker_Language/GML_Reference/Drawing/Surfaces/surface_reset_target.htm @@ -7,20 +7,10 @@ diff --git a/Manual/contents/GameMaker_Language/GML_Reference/Variable_Functions/array_foreach.htm b/Manual/contents/GameMaker_Language/GML_Reference/Variable_Functions/array_foreach.htm index 09e27440b..5d37721d3 100644 --- a/Manual/contents/GameMaker_Language/GML_Reference/Variable_Functions/array_foreach.htm +++ b/Manual/contents/GameMaker_Language/GML_Reference/Variable_Functions/array_foreach.htm @@ -7,23 +7,11 @@ diff --git a/Manual/contents/GameMaker_Language/GML_Reference/Variable_Functions/ref_create.htm b/Manual/contents/GameMaker_Language/GML_Reference/Variable_Functions/ref_create.htm index bc7326898..238e8026e 100644 --- a/Manual/contents/GameMaker_Language/GML_Reference/Variable_Functions/ref_create.htm +++ b/Manual/contents/GameMaker_Language/GML_Reference/Variable_Functions/ref_create.htm @@ -7,23 +7,11 @@ @@ -103,7 +91,7 @@

Example 4: Complex Array Reference

Next: int64
-
© Copyright YoYo Games Ltd. 2025 All Rights Reserved
+
© Copyright YoYo Games Ltd. 2026 All Rights Reserved
-

ds_grid_add_grid_region

-

This function can be used to add all the values of all the cells found within the source area of a grid to the values within the destination grid, as illustrated below:

-

DS grid add grid region

-

NOTE You can also use this function on the same grid to add values from one region of the grid to those stored in another (see code example below).

-

-

Syntax:

-

ds_grid_add_grid_region(index, source, x1, y1, x2, y2, xpos, ypos)

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ArgumentTypeDescription
indexThe handle of the destination grid.
sourceThe handle of the source grid.
x1The left position of the region of cells to copy from the source grid.
y1The top position of the region of cells to copy from the source grid.
x2The right position of the region of cells to copy from the source grid.
y2The bottom position of the region of cells to copy from the source grid.
xposThe x position on the destination grid to add the source region to.
yposThe y position on the destination grid to add the source region to.
-

-

Returns:

-

-

-

Example:

-

ds_grid_add_grid_region(grid, grid, 0, 0, 1, 5, 2, 0)

-

The above code would copy the region of cells from (0,0) to (1,5) of the DS grid indexed in the variable "grid" and add them to the cells from position (2,0) of the same DS grid .

-

-

-

-
-
-
-
Back: DS Grids
- -
+ + + ds_grid_add_grid_region + + + + + + + + + + +

ds_grid_add_grid_region

+

This function can be used to add all the values of all the cells found within the source area of a grid to the values within the destination grid, as illustrated below:

+

DS grid add grid region

+

 You can also use this function on the same grid to add values from one region of the grid to those stored in another (see code example below).

+

 

+

Syntax:

+

ds_grid_add_grid_region(index, source, x1, y1, x2, y2, xpos, ypos)

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ArgumentTypeDescription
indexDS GridThe handle of the destination grid.
sourceDS GridThe handle of the source grid.
x1RealThe left position of the region of cells to copy from the source grid.
y1RealThe top position of the region of cells to copy from the source grid.
x2RealThe right position of the region of cells to copy from the source grid.
y2RealThe bottom position of the region of cells to copy from the source grid.
xposRealThe x position on the destination grid to add the source region to.
yposRealThe y position on the destination grid to add the source region to.
+

 

+

Returns:

+

N/A

+

 

+

Example:

+

ds_grid_add_grid_region(grid, grid, 0, 0, 1, 5, 2, 0);

+

The above code would copy the region of cells from (0, 0) to (1, 5) of the DS grid indexed in the variable grid and add them to the cells from position (2, 0) of the same DS grid .

+

 

+

 

+
+
+
+
Back: DS Grids
+
-
© Copyright YoYo Games Ltd. 2021 All Rights Reserved
- + +--> + \ No newline at end of file diff --git a/Manual/contents/assets/Images/Scripting_Reference/GML/Reference/Data_Structures/ds_grid_add_grid_region.png b/Manual/contents/assets/Images/Scripting_Reference/GML/Reference/Data_Structures/ds_grid_add_grid_region.png index 8177f59612d76eff73520677e19ceb710175807c..1594c8001c03a4185dbea05cd13e99836a0759a3 100644 GIT binary patch literal 16203 zcmb`u1yq#X+c#+?%4O<*S>ynU3Z|eqBI^38P2t9*YIRzBvr3nyODG4 z+V#7)F~MJ660dNAU)XjsI*!+_-66XAxqdA^k>uJnkqcQ#F?F}ZomspJT#IDU-$q77 z_Yj)Cw|gXI%J#k)m(dz)2Y!sQyWJ9QrgO>F(rK(6Iw?!yA82O6Ps>csz{7L5r-Y8z zK7d(bQIdv^kVhs!QrrZ_fLe7pM0=*FSJpb89lD^9BRwcb#gqnv*{YPh-BTA~jR7^K zm+3<}_XxlT`trjD=_4BOaWKJ%3IHFWPsHk1-}mopDhGn^ood=*Ppg80g-u= z4PtbJDz2Jl;|*14O(nul`XjXl<+dsvUS{kN$v_T>Bvp?dH`%C>Sf#jbn>*W#t=)OZ z1}?`ZQdJ##8m+=<*U&}|;o%X^e-6Iv)9Yu-!3dp)Kc%TG@DO5s!+QgVe_PhD)c33~ zK>x>X(n9|&q*NpcQfhe)wz6{DN`tB5P%<;k*+@?^Z!HIxrm;EsO<;gNVK|b;p*`Lf z;cOlRrG51UO1lq%?>pQ&#C$hUws5pFjZXAK(cxt7&eow@acrO2#vSzpO49U_tHj6h z(l|nc9UD}o9EOBc=BHZd(pxumbaHjO&cWksn8E|jBdTD}_vT(d_qeBG;w+izAD}Mr zo|bf5Q>sz)yah&(6$Yi{jI6>{qWQ9lWWE&7SGr5^M02=X_Bj*R`fDn-)T2Sl(v7ip z;xr3*z%OvZ$s<~+z_1*8$-^7>AC#ia z=K~J%tT0fRTjpWJYZTjjL#Z7u5wv#aFVjcB(9z3%adl6bawOd+7Yc0;M@w%qhO)=# z40jjkwGvp`J`McU0q(~Dfxca2NI#f)jq%Vz;DO%o_Pyz!mBr2Wqd3KmC8ldn9@Om7 zy$S`hrUc(k5_i5I1%j$RPq0Wv%_`}=F+$kTd8UZ2dX=~Mx?-frYDlLjH267U={i#m z^jEzHYGQ7>3i7aVAcH!(g8^yOf`h2iRL-wGVw9td33a?XY>es)e7HG?97HADLz>@0 zKG;U^K3?sMftpgQ)3mhMjr_PlRv9mu=n<7Q=BPn&ld{fFPIANe&&)eqH0X%oaft3d z!+fnnFkh?r`c8qjfR_FO%a0q(p{oRE(Hrv}%LG)qSS=L=y?QcGOG@0~vaw!Hh>NHO zl~`YtL7hvNsV*z?la`(J*)FNPd@XZRlRx!hmRdS~h&4-|x@&!h9lmY^FNX zUj`HM+{vsHvMsk5h%VHt%4=j$OnmBfb`&C9^>&y(PSmI2w9aB6c|T$9oPOcVdZI+k z(EG%U-+u9ej}B*tFvnGG#a30YLv&ul zi%j7a%Y`%jsTU@BbOq{1-6GZ#?2|ui5)O7}1$W=M?#_^&oi%;9`K!!KuF};{kDlqy z5uJ@o9KP^@vNhYYy_87k;90rYTGD@!RwgkOiM3QS>VZyeVs)noWg(OVuz+kqF4 zUJE35Y!OaY+na79a@D@)?I-orne{{`Mn&Z#XoJfslB(jzoMx=FfBq~QP*-O43p zANo)#;dqxgo`R8j_d``Cr?M!4h?PLBKBf%mFijsHWFIf5S@(Ts{MgX72%U2C5S)AQ zFUYtpA2Deasi##W3A(acn5}G{b($nr$J_hr%@V-H^NSTVwi<#=@wp<&6;=y{R#~2` zvfSy_gZ3uCVWqzDS>L{Wo0xMUl1$IO?P2C9;CWo~g<8~5FKkoZ)@WHV8$9G6h;&H!OB&LgRPo7v*6)0)^4amQ>a_1 zYO%?pQzm)%+5RX^R;$is$HZqzSeZT^N1j;;R?armMVY5nTqIz>M8!@yz~Cn=L@p3a z+ZuSuFkR+w==G-4_E(ADCOn}cL15c{F|U=sj-%qgpX8r@SRF_5CCwRJyaHBBxPrU~ z=q6JC>Ycg9#u>xM{@yYVj{>$iOMj*H>WBD6ckNdjD>>~gwrxUS9T7?*x&9qZ^%u!* zB9l~1M+eqnqLxWB$y2zp}thayD2O&$qN0OHRl*2js0WysQak&;ffp zp!X3xdRhjjz$4ywWAei7)m9|%H2bA?V#DAxE_Pd;i_^nVJN$K8-`A<-JpJoE74nf7 zu5(^hjA|$_5bGbo583h>Q`{D@D_w6_cbGOIk4S9y9=#_~y!qkfJ-sSh7RR;zsI%R= z;u*LR>pz><)lo_;F@dWhZHAq``DzqdpP)TAkS>(SY*9$K<$bM~JeUlfZ+W>bVfgBV z*hGWZ*{=flS4NDbB;yI}7sn2xbmBFm^&YMjd!D9v+F$enom=K6+Un_O)`m1>Bri>7 zQ>wD3>zYVz*8~R4fU}Q$cwsVWt+11u$OpK+dY1d>!t|4mTHa^hb@Kl4 zIU&H}`1b-dmMeW80K|bY{3%gEs=K^^m(8H$hX#J>P>R5i1kG}Dh0(|EP4BP&D%9h} zb9}Yz1MpO&m)y*kSe<%vFwL))07Ive%i>Fv!BmOyHe@wKhI%!`T1YnN{{g4!q_xBD zaf>N!ZQ9znzLqYer%|Nm+r`5>Q%JYjel$Ia+Rt3NgQURx& zgUwMn1J{~r5-qii)G3f3zmRfC890)mI#aNF$&t~|D4w;sFZpMDKNhMFnC4w&F#@}^ zJc2=~d#duC+3CT?CL>w3QN4TRHUNk%&(~RPm0v)*EUcUXH_E@3X3dN~KS6?w$TB4k zGw&mttoNv52D_?HdbZZtY$*MuZZ|y_`EiVqw+_8xVh&Ga^<1@m1_htpi!D!fNUxsR zNS;Q1vx;iLFkjwOmfS;~Qj?dTR(&F>y-eZzfy5(1Ey;+^aN3okx?R;U`>+nnvLOu7 z2TScC5ymb4fwmwzqXAUO4QDHiE=9BG<*^qVH5$sD9Pdd!!T4FISr~tcYxgn47n>ZL z;$_Xn(e$Y4%o0ba!+JA}12U7>q$;xs_(0P2|c6=U>Q{^5^QUq9aRI|ldE~tjz#VHh()*JDeq3G;OA)T8|xkJ`*368d5H+tX&I$S#|hShdr z&wt{Qa!PtkWwi2dA4Cm-xYhZm`F{ z+fc=V71!EM%bJOLQ9OSH(lm?fM5~hSf@M>wX-6hxu0gklQq&u^sT|tB+!Mn#J|!L0 zd4IKU?srX^660y|VzgzV`ab3=OVw4>2sm%b=;-Lwyag~}?6)HIelT~se!TFG_cp;Q z#+?Tw&rRxfCT(@|91upyXs051ifCucEtGb&#D6w*?cP1J^nE*9TRC>}NO%hH zvd{R`th{((h=wy;>^rL=P76n1=@>MXkp&>&t>#SxTdRE*K0O>cU~js%VY%OwoE2#N z0uzrcvwy!eETG;s%sh6X<@39ghuw`>RBkWudVQ8V2@Xk6BtaO%E$^YUN&m#O!Z~y- zRqSSEnS26|0;LONBqyA#bAm~M`^0}m#C2DHrs=ivp=ZmJc{>e!?kHmsb}4!hpW?gI z;*+^r#mT2b?N88G2-<$T^~FVh=?%XxP-Nqq3oK{P&vEltBmOSKP1d)IM-xu|@>b*J zx|0K#km;CJ>)n7G*&e7}OP@~e1lGA=5X+L_liZBM_(ucd0J#G` z%g+i@3Be!2zmpWFUhO%0h4}j(p8LzPfP#KGSRazeR!U)QYipBQ3wtU9w2~M2q1IB4 zVbP-pQ>fvS!e=ku9zxFW`7Y(RcjHA}p_GDePWD%_EyAC&|L5>OB-CT9K*wQsrsm@S zk&4UT|AqOv?=8N3en}cHewSLLAe;F9{Z5bvm-knCINc8{hs$N|ll%ia;bCE^;vn6b zfdpULVKY^sGJNkfO*hLwu+#aSctk3Mtn2Gzi8n{vlcjHy1e}8m4AQ+XPIY2b)Ya)g z4${<;Yr3d)-fE5POW=LiXm!(@LOO&jtNV(6OnHoB_gMQ}@`=r7go*spZSXLJxsQHH zUACG2VYBJcKALJ5cD_*oL3^LHa1C@uC<#B2i(!q5Fp90Qd&c-k8==6V(XcT`&W62s zR0y_q*_*C!k;Q`E=ha^fD`fU}K;~v#Q%mvEH1xS}&ef|bifw{nlmt>!Z^l1=*R8NM zR;c%hUF$)AyndZap@8W=$nxL7kh=kTWdcn3Rcb0dv@ua?T4ui_RcN+5*JuPZ6CIaD zeJr|AlEV(S^0wQ9SqF9+fS-e`>xp4 z!`8@5#Gn{C4QVv65dt}!0Zd2?Nb|26yxe}LZbP?NNO`Pdxoc0%Yuq-z!Bo}h01^M@ zez+OP$|p!3C+Kxr@q@Eo`Raj-v8Rskq8isyd<>7Gqn>yf=;*}3_S(t6K>*QDqY!pi z_dd)w>Z+RaW`fioMqjD6kZ-9($OnV8Ie`8vGpQLHr%fd!3PH;%tVUl6kJmcC(+KZ6 z3YY{_rr~xSg~4_+kFQeI~Z~&v%%Rr-xgWkzv#WAWP>t zEMzCxs{S0RkFnT9qT)T*@WvzBRc@&(f~#y>FZME6->2T4)zeT+Q{0*Qb;uwZPU&-5 zzV2K8!~O>kV;6la^V|UI+Nyfi;_-)e6ruk=%YiR)oGSh>NN~4W!VtPbJhXru5DmM~o{r~!OVbfXNn`*Z zH;;!!FWwQoFx#G`*U@=J#$*${?D&HUwK4varIYqJ8>XQ4O}Ki;?H^aP7^ ztT3T4BZfz4?8NI~EzcJ-u%RcBYn8U#^1HX=Si$5d#IDaYTr50nl+oFcY*e!xO8>O( zvJ}Fb_nZP#V{QDom25jD!V*S%uaxo+90*aRK^W8dxBvz&U<>H;U?maA} zZy7``)Vqrei4Ei-1@bYFeN_7$-&!v@4gSirq;$E5{-eLJm%7pqF&m%f);?M$Lq3=n z$q`%KMg?S3u{DJ=t52OC?c`?(9Y{2fs&3O-TJB3ToRxTAMj8P+5I%0`p>P=EHz0!6 z4`F<@eW(lXmwtv@qg&(eT&@(K`vlo9Hu9f|Zadvyn z>E~L&D_xMDO(hc7eGvm*zPP8UQ!V#CEg(_fJl6_=JSmkEnEHJT7WM(WAmWX8~V)81P>>u@E6A!xap4E7sR9U1%$P{RBE1H63byApNfP?^M+vxkOmVhZ>-)iLcmsZ#(YVIPbP6Un(v5P!-+MUUyg z3;mSD-s1|Va+|;ItV)Ktjy1E?%@bSHGKbor)vL0JfCLAxywZuI5OI(^YCwk0%w+{f z@3-_{r3AaPXd`^5oxC3me16nk?u1w~uCAk(&k|PgM2z^_xg^s+pX|Wu>M1h46f7N9JTd%9#^gECmXK zCEJ8F1wK#`+LIhJoB!p|-_sM9?b!CyY)-xf4vRTj_q(UhwzktDdRbZ<_iOL7s5&nj zdwtOc>)aiXfCxu+^lJN#1WuFFzgcOiE11G>jJ1X>+_S65Fz<`sETx2Rj^^j*a~&Y& z=6+KUVqhVqGVy`;yoAH}di}Ahg+1<3Fb7`X)2hD|Kua05JIlmn-usl-28jJKknT;9 zlK0jBg?%NaoCF@5Z$R7h@XmQ6FK~5kdM>HjtY4!z5P2Xe0Q}`sV4I5+r7n_f97S1p zAC;$c0S1u?)c7X9d~tnB>Ag3iHr3-C4RQCn<8dN3|9xlr zBQ}w^LBq!3tka3%8<=mO}lKOiOv^9g*pA2(WVV8u6)wNVbG7XB-DelSI=W{bLpc zcmVMHrh?KPxdJ09)3hUWB^feal=Pv728aGXM_gW<<-fbXfL=0rf66y1=|F{?dohkW9n|?E67!e|-jy{070F`VP$i zrP%1o6}1EgL7~=BwcUd6!PYq2uA@K^#U2ocbTF!lA|_V~0Vf$l_l+kfV6HL&nY%JT zpuc}&y^I+*@-YCuF5`El6io#i@VwE>+EsFiU z5@Xa&={obc@wkocOJta_I@}YfaPr;fl;Q0}Nm_gg`g{PbKCqFKxrh`6h-;;p4|wP) zfliG>7Prk5w~HprilH`gH901PoY#tlC@KON8$I8i$c;!jv;`5DSq{;}0hadT!^U`# z0Tb~2wN9F2Q@}2X0Cs~WpIE?oN>v!#UG4~W7+w3j$q3+@=ULms{Z}gC2eo@rxuXR- z@E#xAnQEM2#YDa|#vTFiJj6ltm!SHQS5Nk_vsEfDB)h)LP5E)fX911{pUX9$H=SP} z=Q-dg#B+y-(@N9V-+Ilu&~by|S*imL9vQc?G^w3r)IM!5)KQZ}SvHx|ENIN3w6r;p zS9>mBBR{+0CdKS8Xe-Id57$dO;P~qX`o>i8!rdgO{;c0JqhBGHq;?PFw0+sCW4 zWfNR9L=anbj`I@ZN;2o^Q~~}!)zc17?7~~sGV*%T$GzP}zdrz`QWaRV4#R`EAF{P6 zLn-)Gjmg@nBwzYpji#JMzgpS(c~dxU65#a=yt7Vf+xBnY=8o;7cBUCXoHO#`ZT-Bm zRGdYcTi?J%(C3adhmgzc8E$R_HSfXMX*W}`<&H=@Y(?v7{P7Sh-$TOqY&k+{d8@cF z`g@AE?jcs&J=$XqF|N$J>!`rhyZY#w%uGq!`a@0U3kzI(lkPY!i{;e>$e8LFsMV;K z-|0_pGh{t|n-*w<3NK{Gc7$(dkPYT*v2kDvegJW&#X=(Bde2Tri9zT`v8>Y1Zao@{ z=g&(8H41e#La9Yrf$M#bD7NaFrm~9tiw=`Sz9l$OCvn6=Tev_$37-nKmwL&bGAqan1r60XU~5k}=OXd8h)bsdaN^>4cfcuS#uvtzaW@^f> zQN_kgX+0tgy!q ztLNBTigB`H1LR}5S2XcdhvB6cbp7j?NUS38NQwlGfA3VyS+ONR?^t4tVp}{)SHiO8 z%Uy+_k07H%jR50sZN|6p`JMk>Xld{6un2CDs09@@1xka{4J98&3=H>L(TsODk8D-= zD^bVx;@7?9o3+K9P2j#m2yRk+L!vE#F(@T@?_XEx5DQSwZQt0cy4^Y@uSU5TmI$Cl zyFgN>_X4veJcdmyao(PglL)}^dVcC9sIaNGTr+mN<#hbAk)tk!rXAIcN6piI)Es`V z5pxoo>0Un%HwN)b?wjkZM54V{g`rOo+57b>0prrrC_84upRg7D+Wv{94cfEC2Xc(U|!5PmFAfr+)(Wk)*h{Vb^mgw<^ zbzkZgJaV2+FVw6StBk<5^q9g|)!>?5VM zkUaf)-k@kV8kOLr8I+VFst9cCHbZaRyz}FwFgXz4KmBR#b5f^Us*O)d8}O+`^yN;p zzbjvFks`DU%b$7ePJ$r}@tOM`W&)7xVR|XI5D>B zJ+)X8yRrDp#(Ix0Eq>1Hg&t}_mx3QHt2Nwizh65qVq$*o2=BQn%?|inI@)M)oYpm- z2|kbIRD|=n?j~A!yB!Qkk9w~EK1UAZH^`D4b+l$_5~y?Ur6XZp&-m08fy>2Y+zP`W zj}O!;)XidC?i7rszUjIpV0`o9TB&{esCCKZBgoUa**Lu_}=ZQxo)10ZwexO;InR{z-i7uLyNjY^M*P<`aM*BX_ zUF^D=#BU7D<;U_0JNaNvST365^s9D+G>2Cm&DQ27$nLR1^X>o*hhvpKC}50FMA?OI zcW%R>>BjvJp*#)F@@2YK)4@xZ-usuGiTqQ4=nVXydOF%VbM*7*e=7f+auvgb{22dl6%qF4rO%D)s8st2Z;%_KdLiXB?*OIU8=t z0S zIJWdhCjb7|^OiGk_f(bd`S7rNZBLX=tpz^K`40!IbK0OmuJ%O$YWM1Jb9A)gD)#_= z16-{qziJ#U{x@GP;rRMOTS&k@XyN$Z*_Qt1{iU`nt{2Q~7}Dy{e`ol8{4w&XNK@vt zp?U&#Nfxl^I4uVsUDarQ><0%0Eq{7w`1Pu#ApdjfIbcaaxdSGnc^bOKIEU@zkWK)B ztf27ujr#KU=UPrds7)+#XLas3k^SS$A8W zA2E_g+q9(jg6`W%#{tK^$7J%Dw4Rdzr0FvY>l0^U|Vvu=e%2G}}D@f@YOGY$n+4DJ?jougP zpW5j3Ij|KPH1gEL*-hXe^zPVR>0Hs%b=sXuFYdanTHg+!4l)7xUddkISQUHdQM?cL zKoCbXoUD?cAkdeP=a{Lo0*yY!*zWKv7ea%yNrj@oVtp$_6E{iuEjxchRy_>Zo`exs z?H*TVCfObC0>BMT;l2sHOT;4#$!_A$(Tlom>n$p}y74H^A!$=kElqC${v^|OUn-lq ztZd+z_xCX2quAJwwADVxEz~3Du`|P?7Z)B1gGhf`X+Ep4)t8BM?|%*sB}uJe-=q&q zpSYMGY_%c_O&8wpq$M=()w={B(wDFokqP|S?D$)DG%D%k2#3iqEDuucT)TADLH@I( zO`&%pRO(;tTi{1N7vnx%VLs=kw8W$AUTEV!a#rfMD1=l>H36+u&ZTj7*v!^8mR5!o zUItQCQ!{()IXAyQDe{4SuikCO97H`Td5n#~!)^UVQGOUE>$}emNh=E+*;tixZ#i#s zGUlz9XVm#xEuNv`Q`ZVhO4wbR{qek(fpyO;wie}W_kQTrU{u$vD5o_DS`)aqve+o8 zVS#dsKi=@^6O)xTLl*yQr3)NKdCmvIl^w#)Eu>)r9pcVbgQ*|LLg{ele6-_EVc}d9 zlR3bctbzXY=UyLt*iZGD1MU_mfc3E>ZWP#VzcdXeI3TASkjFWxo5zGIq~g+tp!TiF zx5PeI^6NFCT}P~K$z!*M0b$0F_kOb=(M0Ci!2r-e#@1w~X>j+g!t~%S#N4~)uT?-m z$)t#QnGCbvg#edBD4{pB9 zx)0F%75`1jH=wo~5o72soAeVBHtessf-ib*_Y|DWaRFUoHd)5Yu(*agFztfyaxwwxYj1k4qR-h&zF{Yj3gt2sQ|Pcr@uCNaq1nQ<5TH-*beAOY_A3AINk7A^ zmy(KXTi-1XU-T%V)&Ap|LQDIgLi?9&r$-dbkiOBK%%?zaUeY(G^60gHN;?vT{|7^8{;o zBSQ31woj9`h>wsH*M(QP=PHZ5yw4nS3KTgbt9n(NlT`d$n=A2sb@l!KzIb<>?Q7-! zg)g1`Ux!9WTdW><8}jko&yJ1(C~}(jl57lRe3nlUF$f9{4(X>>`T8HzidFB2{L$`g z{-p@0#(yE_RRoHK4ru%cusb?|TcR*Pqw@MchXWkoIzj;mTb`+L#7-$LxB|?I&& zVna>{Tqwh%Fo72`<~@oz+yklgoL=dPG5bCLlhE9_Ght&NwLM9jAr+#^j{sG-0^Q12 z?@kPL=M>K2P;6whPp_UG(j4Y{RTIb%OG@sfoqWa%~ybknM63FZ7mNV6*Q+LWL-wsPDv{1?Z7z1txsFtb! z%mqypxa2(YAQ98o8e=2_(?vdx^X0pmKX-di&%<4qW{u+lmyc-#Fn#5f09!>}*mklk zYs#+Bs8K|Ht1fp=kPYC~XXqUlcwT(+hkt99paM9O8&R7A48DcT)2W;#uox{hTg*~EhD*VqhXrBFnY56=dm&d()0jVTLGLU4b0>P9EyjGHtN+Y zL7Jc6wt`&}f*h59Z&m*V*PZxlGomB{r=PB!uE)NyI#GxTqb}`F5`4!poZtMFw>T0Z ze6)P>i0d?FnSZb!Ge&8`U;q|-aa|qD%P;r)2+1X0^K-SAU|)`0Cyw*F~39Q z=RM#xw8uYoLfsLwQ{b#TH+(8;=@B(~+Z_&5Z5RfJnE_->)BbZ=;(sq&oH~}HA_2;m z(MJns-DIG-qBd=A02ql^U5LLx2h7kY+pV6r-vU=qswel)VbEO9Y0!8$B1Jc3K}BbH zT93q8RbX3X(f-1_x8+~2eGA({)4$XxpnnBra&o^2G5zMm%*;O2hoiQ7nigfXG-l{bJZj_-R^o|jeLMcN1lz&*MRY^MdHwDSBBiomg_M+tlHtURh+r z?DUMspuwx`_G%jF9Vxx^H=h4AS69MO532Fh02@~eo38Pzus`A}4va#*O`F`cN(d z5yk!&HG4dRV*GhxT^x{Ja*WJCbeu(U__uF_&QCDwOu59rEb#JJPoySG$Cl#}*czq@ z^8JZ(MPu|3js#pjI&5H24p!3OVN4}&4BroiB3FfOWe1}Fh?2*Z3D}@~!2~*G*ib?Q zW`Cu@9?+cFkN(jlyh&OgAK?i6MFeSOd$SN<-{bNR8^8q~6;YBDYx}R98q`1X-^r1Y z$@egS0hQgq$;oyR>*GUSnr_j5FZx~jPd|S^;{Vyt-$vx6d~svE+U#V3C8hcBe@(xR zph@+kmc^s}e@6xjP&mKJzW-^J_#e~p|JwuZcj8#7OBMxoj#AW9t0=#8JfH$?>{bB9 z8uz0?VZuB|Ua}}aM)oc|>}h9_PFyJ@4(PeR-RZfhCIkC|1T~R9M9{|JwXTfbVvmvn2gA9{s+{;|`?MeQt0EpM6b5I?yiTMH4QgL6FNz zQ~5G8Ie@!jcPl_ffuKfA@^`$|*qoaU-WLCiZH4V<;o6--J>vWueMB{#1Bn;oMY;-~ zj=XZ6C5DYl!CMERzg|lt5(CcLYDFOmjn)@NBjGie;9-Dx2X7$|>lJGu)SgRoSt5*s z4pA?eGDi#9rxps0KUGE(AJvX|vAlD~+j4gE(qL*0r|6{(e<-eRK3itvz+CRDZ+>wN ztT*V9lDzEIY-wC2^ooUH@WamOw)$$IDAKrIz zYUvAmS%_;4iGb49UiIl)z`MIf3DoNbern|VT44>;yXsgAL$Df}ru-^UG&>j-KKI#u zW?JYPgWFH04Lf$~71!qa?dtp}oa?E`ga6p!YRPF-Inl~^TBlB!$mjaAK$0R#X-@6@aoNo@G5Py=UT)g z>WQDdlRUm^=_kF-7q}5T&faui-G#4MyYIsszr*XbW~#E5xFo03Bk=Gm;NeAj68drS zgok&z8eSE~xqe0ky(3fk%IEkRWy55DYqDni?V1$l#OtZ6mrB6;BKD)5F-C>uHRx1} zHHL#z(bUUx^q$Sx{ z5Y}ejtk;Lbc5|DhDp1Chfd2{T1X_gF_VY7;PWnW+g*$Je712408&BC1U8P^(SfdY7 zFnd3VYYVRq{jO!3jWlaCyzw=7S|}QkxU8UsF$$&6oIN05gB>|}JTeU>T4Om(A6oYc zmsvi%rG+PVC}glEw7DoWrMit%TIUDNOXF{juIesww2@raBsdYm+OlDt%P))Vn_mst za@!r><2l;eYdTE{9ozS!yBuu4IVWp~j79+Cg;~b+yN+OL|8LD;$1J=?8+N~KG)?$z z%>t!DrWe)3g1bw?O5^+kcN+*9TKiYOGGX_-d_g4}_vo38*E9x6We9^Up+dG**^kO& zHs`8_E(s)`InUGxz2YX@F%>?N6S?gEbF=JnUn_+1lxgRrN3>bdZ%t<>D%27tR~)tO z=S3U7`)FI=4HJcOqos3nSOiQY3FXb(=E-lgbvb9URrbaw5b4uTeOpK=@TFR!y0I&x ztIJcip4Wb)Bd{lWYnK9kxO`~DwE3KA?{4z(y_uq=+~|(3%P&v5 zIG^Z7ze$mRflmJ&rROXubAb%|*>!<)R26)L76r_8Mxm63U@^DId!1&PXsRSLhCUp9 zl%Xs8rJJ^>&_Ol(Vhdq2rdBmEOjs|{hiX3%4qWXy(M6#JR&$#@1V0`=RWNg0pct9B zTi~G`+Re?6$pS%TYp-#3#hlu^u68BWQNXmit+^7Wj-NpEI~*HB84Qx$klUX97qE9z zKkiSX9MBP~7D={~ZO~Iip$Oh2X=U2bd(#7x*NZmEf?C+59Xa>Lhb*16=?G8oJ;b@m zE_~b)Eo%=;T8F-8wn9^ueSSd^EMQRH1~3PTmG7sbYzKaO0&9lZj!MJ){^=eF&RJRk zv0lAj&P9ZzcE!_ALdWS&Q$S2*()FQU#h%#8+&&*p!2R4Y1NZXwPw_-$P~K&8eq}V>@V%)YD7{y`pv#KsaHx7 zdV`+E=D9aRa+jV6Q;tf9+3Yur>ZbUvfDE-7YM$sg)z1~Q;hl{OVqo5)E~-p1Y7$ck zgEsK#q5T&VBA!Ln-5*ee<7R519t}(N$*PX#Ew+nxhM4^|78`f%xZgm7tGuK17>EkC zc2t*Hhvr`Ha?YT`I^NnoB{ZuOC+#)QLAE;!Rc*PEtIw!0E6t!nk^CJ@!xuW4Q=xU= zv(yw5xTAjxQ%`z=0VV`8$<_!)*P))yUby)#Dl#2A?p;HHl?}R>5E!}m=nN5cQLNH> zg>q~QG~9BBw5hDh=|t1+qJxp{uloA^xE}Ur6RcIJOFJeaNLyhV+FC@*Su?fCQoD3N z=h||+WjKWmr55Xz?Bj=H`|OrM0tXgs`t-wv9TT(B4!QzIeeGsD0pr5L5F3@8CfxS^4w_cH4Qae3^TOwnH_k^W+ zdR2gvgOInhq+y?(JHz-zev~Id5}65hC<9p2f?J5F^?ITxvAvhWw;l7wKe0f%#`tsJ zG$ca5(M<+v`PW&y@+?Iq<$aNi(~RwF`ga&^#d1IJ6b|@1^yt4=Prn;4t6t+69#HIX zU5tZmrIk4mw=o9834D7AYoSJyi9_ctF)R+uK@|tsjHVp*!sX$Tm zfNnA=A?uK}QE{E`EBLUqr1yP`)9LHS_K)_t%p-hR*SD(cJ;ijW3LOl^vg|b0Yc9Xa zdJic5h;6jHb9Soq^YWsEtwZV$lfoAID`;u|k1o{zkvXY97rrS;Z=VXh1m?TLGLfSH z>!r+#GZOQ@==V#Mp?+y77WL$93oS1SJ4G6A)}J%Z4m?U4uPG)D%xN7u76(dt6vYVp$NQ;=`41; z71dc#1=bO_W9aLn-_4w6g7{V~Dc@I~qTn@&O8B0;*%QQ-i4FayLc|?QG;H-$Rrk?y z%W^>f8?4!i_n0}RAkmA@hqF#ayDDPdM-V6hNE#fN49+klHNu+N^(YKcI z4iIH?tH?u1?=~F9AylG5=3b;nzdc>XQyoYB#I=#3yC~Bw8JSNGztoN4zubzybPvJg z?M1ibqd7)}_~y9a=N4t>fvfyFHM?bMeM)9+sd2v_>G2U?=K9W1!#+9 zDfgJ%OxezPot}{&RWIe9SLRTuvOmrFL@+%rc;MsskMEiC5YdYgH8FLazZTv7*yQV1 nF9Ohj*ChViSIArCE=2=bJ7UX5;Mm~p_-nE+6(x(rU;F-FPs#_hSZP?9S$aA3Sczg`iDoHCOKN#e zZ=~I>QCUjw$~a10pudO+ZC_$8?#Y;ctm{OXN70dO6d!1o=*_JgMiKv{J~$=ix3!)w zVQgHFC67^{2AQoh>pGh{Tdb=BYwtnpfRoTbb87)i^~@eQ=YlwzI-5P)(_hyI2j98# zjpacP@z!Pk+|p8|E8r!ujz5TIV~$vl)Gq)3cfcmS{P6GL|N5){<>HZo%woY{X@=7m zlud`jXqx+>SG1CrxD3ntoJv1!3{hi2vAaoOadCOvtpS9hslohnjR_5Fk%K3}6hswl z5sixRO}~zf3__lfz^-HpzM)^^T)?$Umuk?JF?LvgxIBLMJ0AT{dF9<~rk{|Ut!6jZ zQ0mJQKd)m>Y;TMTuJaocsETyUE|(2NVRdWgGV9a0EoX1Jj-`DrpQ%;Z$9;pq8Zsm! z91|^h%qjqvt!PD`(kbx0`QeI0oU_EgR&39E!o@-yk|~I_kNe9T_N7LPb%B=zx41g+ z2G&jy#5OPU7BUO#C6ioE=6VF{(%2ZmqrRO7u>$YlS^(Qd;K zTF_WLc$HOVue~hgBa?TSQ#ln`KEzvdb>4ZIv|vP6)+TWK?{HW9&HCc4MkHz>sRa~| zZbcJ%A40O0xH^d(7z)OYUh!mOUW$kjCbKb!ck3$$PWY*Co?3mjdFIu`yuedGIVyb?t~qt@ z=Ec{%?kp4Oa~oG~fjJE*tmo~Z7~2?yc^~Z#f?0(Qh+A;IXOT;9&1XVDIJ3wa?BbZ# z&dL^2;jTX{Ty`Jw4^ywcMaY}(lS#mMa7n*PSyD!d#7oEoj~mza60bM;9GpMva{PT2 z#0*|Cf-U^4Q{pDi7d=fv2|byw2OQr*CBis6Zak-9KHuohLf1iUquY9M zxp7l*#`%U#u?Y;ydiKS3l=Gw7Jx%A?@o|QMJvc>GoWQyXFr_5qLi3#Lf!4{%iR~FFduftV6n{f+vDq|s zdr22jg>f~9n~>pl7Sj20lv#rNWIiynOr4n7CXbRL&4OZhLaX6@N#65Zg;;a6`#`Gj zTJ5CCXohaNQBmZ*C;6RGbQO;se-?_1pYM;do_ujxRuOnLQM&80qnUnRJ&>K1RUN#_ zM8Iq7KgI96BJfsWM~G4LL_tV8nQ>R-y#ui&qlUxjR|m-XO7jl+tJPtP{^ z&W&wti>Sn)uCl0JEvVMBueHWk>pBek?<3&1%*ge&J{}lfgMs%AL<~_w2@(-(TDW_U zcuE2-*`8G2z9*vPFx#kour>SS52PM4XM*;cYw<0%g2y+yKj2F1V-QfFo*DE;!s?sj z?}kM^J(ZvJzc^ou(=}1|J>Bn-_xw3ls;}9f$Rjn0w?wHq(k=`iUbWMo>=>_k?||%7|5d0T*a*M#?;Q<=_5;baAJ4wI2@oWxYX09x>yxU2wThblA~d3&kF3PgYHL8$tP-X@ z)GQ!L*ONc$EmY6hUxu`t$SS9c>eJzT;hJMHA1~H6kQl)k`D`Xt>vQ7F`8-9lK*g%B zLMcx!S!gn(gjA|QfM!09%BF?smk(SMdDiRcef5Q;+W+=hk*RP`**oeK80 z0eh8OG(wr35!3~dv|nQjIrwDbqdoSB9k~w^O^n7^wyZ%XMB;aL~KPYVq>v z$zp8jaa_^9e5_sZyb86zy*9V7`mgFuHQ1Drn1@_0P(ZmL;TRjkyGRF>bkU+Hn}O7j z6T?+#^tY*z+Shyif(bUFMFL{rR&l#~sFOX?$dHE|9DOf6=Xw0ms9ndqHaB(4S)}GA zJE!oB8(oL7zor?}C+)LquBzX-@}&M<$=2%+w{~<~LIn3`BmR44TMp)#BOru#2Sn+>O#HGgwW6hLLfOEST9_5-JzhyqYXWRsWPieJa1o-L@cWZQ4ukktG{J1tqGd zxt!r=cAk%U^^BxxkmA}0;E^%R?g_G4Qhfu{mM!0xgd+#0BJTW+K`^PD-O%q6Weo3d zZ?aV+$pV6(SNy|S@mz$I0Hb4S!PxdN;poGCOu7X8@Kcd0?TQ-W2i48HNp96DD$n!mSkse z@FUC5b$u&}ld3z44F?m3wHf)}7i1@_pLidZqEX!sqE@D}=;egT7rni2*6RghSqa~~ zQ;JvVwmxBZxG}Xh@B~?^b_Rcsd6(ySLh~Yx#_uPn|Cxr4ZWu4{CgX}1b(~s2&{*5U!@WmaWG5!YO}UMdu}$Xpk@~4dLX`Ojejy9B$48A%;?rMaE5sq-D7u3-YvU z6%)AZrmC!TT`x3Svg$L}Zek0-<@-I_gYT@x8#)dzJAZOnt>XF6%+VQnuO#r+Jv&hp z0XdgeEVHtPa?0cJWlqDoF>{k9_p&<|OG~V>p?LM5KdW`Ut@$kZDCXHS19ivd9a zIpGAITOb^qze$iTw{IaJKN~8Mgj&5I9lTBczA;t397^RhQ|B-aAl_z!GG8ev8*J*l zbAkSkOo}z0sr(RxQQD)Lh`gF?W8Z`ErDY~2Cd*!|J@gr}gpAWbtHFI#S+MA~IEo0C zRi7$7KUOh&_6f{$%3b=44d=z~JH~r%49g<|<{Hu()q4cQht~bclt)K>Nqmh2*4w|n zS@ykQ@LErPRbKR3c|f^N1i)ZCYwj!4-EvnXW?nw8V&)}P%v)z^d0DrCS$U_UqoXtZ zo9aAio&8icE+NH>vB8tQw_4L~np+PEQtl(B3UsvT3Z zB^jMrR{>o0tFKLzl{{BeWH*X+`9k}c@h1a4<=AGqTgo$&Lxw+Idw*htvE|c5+{TvR z376+YB8Cjh?^~!oab1x(2}C?A5^OxK4tEuoFY8TTvYD*1q<8z#&OS>ta{h}}%aLl8 zi%%f?i);RjhIO@=?(%U6uB`|9e*(tQC%?)WQ|La#H^msq*)G`VxnKKdSb z^MMO)bQ7}0kh||F)Y};`+oTE71!ID5|YFw(ZcTw0fLMg<*m22jzc8=fq>1iIPAv#UeOQYh> zLxO`RllXvW^$#*qiN9pH$vQWbVjBD@E>3$BH>O*A_+9h4)lg6Wu(W<3J1+fWz`+vG z%aH8yZs(5p*uknBM_&q`+;c0)-r}Cvsd1Y{2jwDZ)GfLqwa<=_x(VE-I$-B(0w7|F!@5*VUnK;( z09L`p#R11y8!OUuYQ2uR1&|m~%j=ndLhDrcGaKK(ev9UKz-|Dp$*xnXwmg`jn+ z@b4aYcUlq|#~Yk1Y5`@~-FxgXz4D6T1r|_7D>t#Q#~)6bc$ZO$dVWq8cCkLGRY?VTO0khXafP38&=K8qHTe;8V(YYV0p)*&SVa#!YgCv9H>?f5ZuWFlkzXGn^1l z!8H;}w10d=Jv9N6VAq%;H!PPKNEr;48+!uKloJ4WTVVoeKFG5|1_3L#I>;T zF!|Nkl*{rMeE4d!ZiPuP*iN1E`qnmKeA+6^+=d8u&V6>~+#6yN#>-~FVW52%#t@mk_ z83-7sr1IN-1n3%v#!Sd`bP@iD`D62TJWdnINaq%du3HO~o`C$=?JoAno&&m;6{*?N z9MIgr$X8+9G!cBUyGz4o9e$|W08p;>wbJBnbEto7j03F4Z)7BtzOxAMDGzriYZBJG z$n{x6>VjvpB5qof87OIovjw_{j>^92_^D}gM(?)?Xz%lu8z~5-cu0Y2hR)vdpzaaE z8=~>ReW^FDaY<;V`^@^+*SFI`q>EFJk#kXqtJ#8shH5}|6}|GQjAjxk?gb(3x*kGe z+ryLghG7FtTO74relTg!NV3~}`;7-^#R!v5BjFhGnp{PS`8kNCAq3fafhLuD=-9Z* ze6S1WroJ(^oZ)YRuBx*g$qf_DIOq8VCf&3Rr#FFa{I-Mt$cDScm|k#cvpwEu5q6ChTrrTJ}5yjLX<~s zlZ?zZUDc{B6jff;%}eK~9`a4g$jF|t^su1|pWB;sL=&_*b$e<#V_h4Eo(4(1jl0~SIoeq?1T?8w zx-PR~&ufMXW|r*wKH_68G_W1klGCaWS(cr}W{w?x=DatIzaB$5!Q6TM2Ct+G)i8pq(-|?%BMP5ZsZ8* zoA*Sxo?AZI*y>}?j!O#6pA3nu%oy0o7zv&JZ1!EPqctIMEG66*jIe?&JS^7bs6Ef# z*)ZtV^pre%F)KD@v;W+C1&B#JL`4TZcfrcUg5h0!`bmXf)Kg@uqOLthr63w<;HGa41C8Q z0s^j{qrV_q&V~%JwmT@aD2F((Q{@2d?c#W@c>owapEG3jIqhTnM3XR;PKn+Lm#XN> zRpapHXKlV~W32bCJ1W&M^tPeyiMS5o7LD2GSznZxo)`O=+2X|`EbE!|g$&)JM7(x$ zRs0pag_9-7{#=;BrYu z%Ns6xZ`e};@})v>@TOKJdbvNPfJLJlYCib%tQ5`BEgdFD>y_K<*FE7pu({OSY1tX$ zFxM<=x93+p98{ahpI1+JaojcSCDSznnT%|QcyoA&_Sg&X{}+yYe2-wDcXD;_WZj!{Fwv#uS2= zCN4D=ZZY`=0%oY3@f6lp`+vvGsYNh&=gvGCL~YoJU($%QCms`XJ#I-mc>mpmN+$k&G-o45)FpIzt`!xG z0V^pSGKous`;VtpR{__2blMno!7%RM%OP*U8ApiZfgGL>!w}j zDqt5Fuwea1i3q2R<;fl)n!TzKckYw<>FWV`w{=Wse(_GiYF}rhFlJ{N#jxhLbG(q= zF-pGZu}@aD>wr4m$vUJ1bk5}M#%K$eveaM>Zd1mOUPl8d%d2pU^dPiH@F~&_b^Wc; z$V@D4!O{A06yjNKz1Ju1m7CbL3^VnRs59eQyYaC!4}^li)k|sphUoVRV^NM=)Y<|8 zcXOs=!|%Y|L7+~w$+=DT$7#2)zTCoSbs(@=Um%q^;1Ji%X>EV>_V?TH>rvvsUCkxF z6!YMOKhci2K%{YAD#(m_hnakgk0eef>KUzd^*;ti1H|iO7f2&<1bT-L{f>VJ9W0|z zJ{mVJ-v*0N%jGAq_?9vNeJc}j-_ZMg2DEm}^Z!;QImiD34UICNx}`!P=$L9Z+gOYC z0p3)}4HD+)e`mc9zA7&Io{*ycdW2#^Fo!+izgUX>R|!E$OD10R20~uIc~L&+iFc~7 zi|oPrB=;W=X7|YBKPiy;t?LeU%aP}2MBcKE9SDVl|02p?_j4lT1vlBJf z;FJSJpDe=<9>4x2aWEux`+hLin(~i&-=^tCw-OQG(;7SX^Mf_?by~H_I$Mi&q&fjv zd$S2Av3i)_i6REesqd1K7E$t9uSoOvWJv{$-ShaFWj&a_snF1h+EsMJXkt^;JbC&t zH@vX<?}Bi)y<4m?>+i<$T2AQCr)yG~AI!D|}lXGT)gvapB%C z9A($Ojm}U*nzObpsa>1)q;WwbdXdF$hVEiT!DtNNPXcGYj+_L>a<%UL#M)>G!nm&U zJbpSg0q2jdsc&8~WnoX}LdL~OhIW}jEt^rSBi?GLz_%_sf1eHkeQz~FN-%-uXw(U` z@NJD{qGf-wz#2%LT;klUtUPNMfbnUS=#+u$e6|tZ$ot_~Ynyw6;<}R;2d26{t#St* zKXQ)N;oPnEuE!KmI9Jxne8QITD9(rej0=>_0fwp)NCf53K9$ z@PNeF<-eCpEab6eH2co1Du8|lDiY)3tqKLHWZr2+jocf@B0p2&-cujFgOy=y7>+a~ zox0FmsQasVlF&l=4NH9P4t7qrk7iccAH&sS+B6B7ze#7Y8lxC~v|gOG>Vhbl>?}5Z z1GUO+IX|3PI@7SB?$PDl8WVPs?Y!=`I>Pkn10@vRa>2W$h0n$vLuN#I=HT%pc^-H} zx*L&PtS)+mG^klT$8Vw;h6gswF&Vz{M`&Fb|Zl_z5_R*77tm+OLUO`@pX$G zZi^a_1xvazfGMaHrAVsoJ=^vH5s)Vc7+h?%r^S7Owy;>*cS(FUYbLRub$W*k52Hm7 zz^WGeP2?7GA0Y)ra7TNdAe(cj>A)}z_sNKS#yhzAh^&-?gp#!O1pW5}8xJY~s=l4B z*0YYL6MFrX?}EwEY9rc~%e1A`Fu@P(nc`+qzV8`UFW-$hb_mtJLh)uvm@u31s|_2v z8>%-`cqHRZnP~1dE_#vRSkE@PY1`V`en33{{BZ+R^y+_l6{yU00HqCBa1pg*gXDql zuPeTe#5{yc_mCf)LJ?Q(Gtuay)=4;4&n_PCFWt_F8@wv&6Gy}>F`Tcw6%^%(@Kt&w zcxQ&#+toffVvYLshMj;2g_)0N)e(Hqvv5`7?wTjZ3_XkQu(80g(F3{FBU0+_m#{DJ zmSTBC@qXM@YT+YiraSxb#?$Vb#c2^W*}c$7<{11!I%c`-`Ztt?Bjdj}wtmz(q?qjM zka^U{IFSMQKVF*)OwwhoYjBf3-r!l`QB~Z>DF(O;z~q@E`H=f+&bH=!J4l?L?E0>T zNxfrQBcH*HJATi#s(`nBrLI(q3@^MP8=v1Is^mnm$8w$6eka`LP)X})(DS}HvIi~| zi$l2Zc>;!L-h|<(L0+L3#9dWCx%7|zqmCiN%f}nlgRUp@9cQ>OtJ{MKNgrh#t$YS5 z{0`W~9Hq!o-9mN6bI0#(jQ@x)rYCv4kr3rT({nrsG%59tX=AkI>P<>ImTn3)+a;cH z7-w~HhSwiTm`kie&JW59UNf2SyH8M6g}dKxi_`R8C4u2k+lG)}&zf{9w{f5N0y|t5 zl_1K5n|Sx5yBTZK&u%wNz@HoQD;Z`F8t;zl&cTp#UUHj$XAW)&zjqRNCnm>wAFcG$ zq}OKxdHwW{8zr29^S1d5h50B-zD~VrFJ?;qm(l4B_rty`!mWVT8XNRSyI3?)oNvyd z%S@E?nIWknZqGf$MYq3Vp9(8&V``n13RN3X)Fg&wp=xe3sl$XQcbqxT8+=AM%ANqV?D2>1m*^=#OVk~Gn(zptse)y&J#rE)IS>jws7Pf6rI4m!r4WrHB|>!HFWpVAC2pKW&UbNy0a(& z4Trp#DRy3VQ{?I<4Htkhnu5kxkp>GhDaOsFf#Z672r#n70tV$(2dHj zLfO9zk%&PwgYjS=xJdK!<^q5OVZ04M(IzIBy#F67iz4VY-Gp3``tyDbA+KG_6Edg6 zBP>jd1GR+Ewhy5lSoj)w;Ifscr2yXXAA@?22P_DT*x21Q7Y{U|mx(MunjC$ZkC5c>BvKi2MIOhKOy z1%_$8P^TgeBDl`$|0o-7sBx2fQAZegiR#l6Y2dI)+@ujwyGhC0o_Ikm=%|I!T^JsP z5R*pvuVe*@hJ}%`>rl*+u0;qU)G$m-#A7S95u^|83-q}*sFX;>qRqaqA3ufe7bc7Q zw@g>tM47nk{tlv>@EYL97=oBeI>@rS9Gt)a%mu@@>cb1QiSBt%?{yvPvJQtmZjMC2 z>@Yf^Gn}#*FqyTXEGfIw{ngVaBn)IbGz1cxyyD&ssvm z{E4q?upZ!toLw?3KAmsPR&X**T7Q74lMJO?+|;tkwQkCYgTM5_|reb|l(LGUM&03W*SYII(UcV^Goy-DE|ksm*PEInhj z;K!7G7=3I8(_z_H|ghd~V&jDPW9iUE=6UmO#725%E%J?B;{bompOH z$K&naP@lv}&ZDVL;alY(`qQ5(f+mfDS0hUle;*@kpV@M@)g()zZs*DS=I0p2&8Z0$ zl-ud08|5jm#eavvl1Iy`FVYr!JnV7|hCnvs;<212obzdvacH=&%QGg=iq=Z0B zusLCm!~v+BneZ$;nvu_snT{Bhh{Ggz&UL>oJ_%*2f~wq4;e)n-%by5P20_mcCaD#% zxj_KDmxN#n4xn*_wUv2&yAHJZ)Y!gi{CwBaIXc(>$7LUcc6xKBO*SwUSGjH%=|g$` zsJ~}lkmz_=8=*O+-OIW{KMIP{2lHXvYm}&f(oyDjy+}}!QUjN7i?mpgRjw%O3=&y> zv!hH9u>bLhxQpH&y_XTOPYeo+xZlQ8mN^THHnceut>pueQ`I)pM+x8N3sllVSt&?r zX;ufwT9%*p}rD>Etg{TuKnw=g{&WNO#~q?j%p0hd2YFwxkW?!0$BIPVtj z52kLp*pQ5Z3Zp#fGLE18h0%k_1LoN^F{dj~z^FPCZ+G zfcqV8gTBZctu<6&{ZZ(@r2W!vck4vmHA!8m47L8th5SX8LZ@E z-+uf~asY=u4^Z7=5%Z!V|bB2b4i>>lGJ#IrQc(#+m>PdA~dn0c?s~9lj0Cq6d2!7tJVCCpCnzxyI$SInB4fkP>+9KwOMCEVX`z5iGPPQhPws?$5?v^34Ab$R;*Yyina{8zmf&a zru@**Q2BpT^GL0~(z1uR*89lu{G>bP0mf*s19@_7cL{C>;@xg_B=3J%G(TE=y-$`| zGJG^ZshDl+DDKiK17j}+g&RB2H5OpoUkWQ>u4o8nxANb{TBIn7A{LE>`jf7=}&HK!?)ytklv{Q5?H&u}y}r&OLFz z=I2MIwRUmSUt9_dYF@^WX#o9+>7Nt5v5v7ZP7l^2PFLNI&xtQ~M^bq#WaIWU%Sl`@ zj|Ew(w)NwrrO|KDO*amn5J8^o*Nrr3Mqa|^w{PUJxgZOazLEq9zh-zcS5`wCI2&b{ z^3?}TJ-tGJNyT-Jvuh!5`MnSA1pr~nK|}BPiMO}9Rw_&;AK&~okur(qHfm5)PUcqt zMNF*>P;Ag3Hv&G?O>MuUHQ&qKKyVAkMEomgtt-L3O>6Yq0BqiUCt%DKOTNR^ZoEhq zc*T~Q@adB$@c^bP0H{sdD@pC^+h_OD1)#UV)BubbN^bK=VE5wyvrFc`YpmXwz^Iup4^_iiqsz#-JvD@R25| z*bL(gEzJ_;fA0Da{2JC?vVHdL;&c5x;0k^_b3LF%a_r3&>}N4^=esSJolBtIFbNE> z7}Whc%aSZZofbN6Sr+`P2U3dwZOQ@M@#FYs;jRzzLa_F*?Xw<#ycPs1aSqddND$-c zM9YZU|9hjQr&%*=T6UETj7j>o**dHBPWPF=BjqmMqO3zlMl{5l^qFH8mzS?UEu-|n zGz&oCjOjI*`AsUi`SovODL*mes>6Q}If3G3DCKn%2Z#+D%I`qj{=E#uZ`TxGkyRqM zNz+;==t^tL-{_zyY>_70igTOVuzGlH^=kBv_!P4VE>DtIGhr(oDrkG9pZi3aIjoy+ ze{-hZr`e2R`}^OBCZmC!G=`bRue=0ZiE&#zz^@aVkmIeSx6sO^egTwQR(HEekod+< zhT=6zh{@Tdqt@||Q<&owE?7*-rJY=yaobr%+}IE9z~C*j5q-YbYNcZp7BX`t#1d3q0e7JCz)*m7uTm92Wegn1Oh?i#)L?AvodpktQnWJdYIY+|}0h zEYk=k{=b;cB#N9D_c{LjG*o`mF(8&jwHOdGonzX6aCsfT<@1C$!LBE}OVeL?zC5@l zF(i43v*g>&INI(L-SDt;3TNNGM4tZvEz#e`Fv1Tw@me6-h9)unDj2}B!LAAt`HP{y z+sM~5Lp?jL{QWmt?ou}VZNI|$cUZiNBQ3esOMP;@2tvMfs~fi>%WZ&h4rNrg&Nh(L~hISbZ_1pIR{hxyNU^WeCzc1@tR8P zQ!E7>qvW?&HTT^ES1?W5SB4F77_6+cn^YNzS%Ycqq>a-GOX%DpN-aPqIjP%tj*6e= zOW*jpiJBG?kGLf}y*b@#qZTU(z8C^$%H?ALC-Qq;#Bha4Gxf1F-MQKkc^RbE*m;LY zdR=)&JzDqAkdf5o+g;79XIMWveTqW~m1qjIH5{_xjG6e{{xYmSpJ`$`{>Qq0*Yw0e z@&po}b2u#c!QvIX;9x~g-Epoi4aM%f34*@`0;5So9A2|b5gS1f9HW)j?)@WV6%^Iv zG&)C22{?{niB!zjWWHM6x}PBYo(3LQbd25a0E^S7Vw1g$7%V8f;jNu``0Pi6d7|_t zcYRA=2*K0AVo6z}_=a!v& zyUyWe9Hv*>5mr2(Ipw36IL;}lt2-C9P}wB9akixS{rwwrkC0D=$ga(HVkZtBQ}^H& z!pjoOo0YPkdYq5;KM&-a+T0u=YYMt(4@uRDuB~@?NO!C=? zLmEE3dUB+9t-!P7OZ%&+!K}a=k`-pt3w4`$LO&VYqvjO&8)z;KIxr(YJRYX@5jvqwY!k4M(2W?gjyHd{_0ocJ5RNI z>#^UbFm&zQ9gfqYR#9${+1R*M+4SsZ^}S)krM;h~GNvnH*(Y8W_$SkgupwsXgD4yE zs3+g|jLqZY4k`y+Wa#|lV@ucibKlxcKHAgjzzJ0}p667XyG?sL`7N~Rw44;@k z;$o~nxiKenaiI_}SKy5F_$ZpNSHE@fyz`?&51M$ve}KH*^s}TU@#|&<(!)&W(B=AWt32UF61$$;);`Elq1*(ThI zhQ%y>5q7?AX}+8Yq-Jxy(HtrAOKPjz#pI6C^89%e*;tL+Z=_F;TYVyUmIuEMy= z5D&&4m(`V$?jjz!7M&aX@msKucGM2pg1ep*d!B9E?W``^p;j9cj7v?Sna?9d7{du8x0cLMxhUa%L>GUtwXbh`?l$pVl;IQRh?;(jc#nU;iHj*OI_D4 z6qXPv3t|c9O?qe{lv6l)BcvinLoP=fkMzw z?+VXTgH|1h2^m=Nga)DA z!KZ#|UPLT%#-B|XFRZP43r}N#PwveIo=M!#_Cl)h)EqXHkpU(Vw{B9T7=Je%- z@sfHIG+34iOHR&oFnV!Wo2W{9unjC{Tlz6J&?-J4Cs|>f5~!iP1!9~prAzaMs(RIS zNAO@ay3X&{wsFQMT71#FAP7UaGxfT}jVHL3 z)11tt1#x%mefOPptMK$=*~fMWGyure_h-j*hq9h9&VtJ9xlT(0b@~7ui-KTWsn4Ku z^06%B&XG=@c1P{FttgKyO_w}=D*-+%r#yB6wOQ!R)W4o))TPVjh4dV>Bv`9_Y4DVC z*<@$y-r#L{E`+DK%3;&zRj}1H+O*ONcj*yP2yvjG)DhGK< zGDPk5b75QmcTyx`V){vw@( z_{#0>i?3%7Mi*nGF%;z&3x4obyGK|n*WaLS|6+M5dD&k1x33Zuz%i%%f3{pIedE<6 zveR3k!eS$Ui(aw3ZE*RMzOTAN0r*68Bxes<_8!CzMz5IUqjnUVPnl?#7w+}vA3ZsG zx^n|b86s_dZZd@iU96SlPb8=?*JRMi5X9M*KP$L8(xFSbyr086XVc5AiME`s=zS`M ze}RlGd#!im$3QC1=3Sx1=UF#DSL4zyRmHEk>~ShsS3O@FweCS0K1$KbebjY&6Dt>w zvk(iht5fqUdF!RaeI>Lfu7jQ>D-G#ZTF)}!3zO&dyh+1z`a8DNdxs~Tu72EHJ^oif zM?U@iEv`oCxxAU#Wt3^D<5$ZIP21zVCK8fab}6(alafN?bIqFzhPFTXe(%i~SKD^l zG%tIze|X)hJ?_oaT}|4yk;s_%nV^yQcgav$+CzKWT!(C%nh2M;b}Z!skAZ!EhSLld zjsDhEG%ZGleK|`luN|soBsG#i{6LVR_KIM?T2qGKRyy=J+=^0VpH)cpy`wzB!WK- zU)I&$mCN?-3aOAD+|!{tDz;A?U29R{+2Z|J=NgL*=;`}37NaiwviFA#ym4)M;;UQL z=soFDPe0cNB*UIPaShUP2Rx}VMak34M!$t%9tqz>-G4z4J!-UD4T^O z-pXrg;mg%sUioQ|c~=V?ku;SAxF&NKd5OSmuYM65#h&2xU-&k2v-8(__G zS3h7htm=k|sx$|%{PEy=&<6XYGLn}?e4J;FVnG~O&aq~^XGQSJD147zOfo+g&lex) zQDEh=joZ~w;E6YWZsnD4xw_FjDI4dLR1~p`R=sN-q;jgo>!X`%%VwLhLc5dBqko!r z*5rDw`l*YCb4_)70td{N{G^0(5X*=|TDY!W{&si|3d$hm6r*Vt>JioZRFea{6B#H& zx?ADU*Tp;S)5K|$-?+(6{pUFf9U>jbi_tcgjc-)P*eEL8YOB0+S@zg9KbVw%C{hi~ zU`3pNZ>|^1efi6#EfeP-jBK-dNnifz_n*G`claxgB$83BSlC!s2JXJS{<3`y13L;b LD$?c8UIhFfNe0_s From c5b09717898b9b027fc2062f79cf53b73897dd83 Mon Sep 17 00:00:00 2001 From: gurpreetsinghmatharoo Date: Tue, 3 Mar 2026 12:52:38 +0530 Subject: [PATCH 057/108] docs(general): ref_create metadata fix --- .../GML_Reference/Variable_Functions/ref_create.htm | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/Manual/contents/GameMaker_Language/GML_Reference/Variable_Functions/ref_create.htm b/Manual/contents/GameMaker_Language/GML_Reference/Variable_Functions/ref_create.htm index 238e8026e..a3d977859 100644 --- a/Manual/contents/GameMaker_Language/GML_Reference/Variable_Functions/ref_create.htm +++ b/Manual/contents/GameMaker_Language/GML_Reference/Variable_Functions/ref_create.htm @@ -7,11 +7,11 @@ From 68415a370134897da1371647900c2f4722eff718 Mon Sep 17 00:00:00 2001 From: gurpreetsinghmatharoo Date: Tue, 3 Mar 2026 12:55:16 +0530 Subject: [PATCH 058/108] docs(general): Document that Game Options are affected by configurations --- Manual/contents/Settings/Configurations.htm | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/Manual/contents/Settings/Configurations.htm b/Manual/contents/Settings/Configurations.htm index 77045547e..66168c8eb 100644 --- a/Manual/contents/Settings/Configurations.htm +++ b/Manual/contents/Settings/Configurations.htm @@ -18,14 +18,16 @@

Configurations

Due to the demands of cross-platform development and the need for one product to be available and customised for different clients or devices or platforms, GameMaker includes configurations to make things simpler. Using this system, you can quickly switch between different splash screens, icons and included files and test or export only those that are relevant to the target platform or client at any time, all from the same base code.

To be able to deal with the different demands from clients and platforms you can use the Configuration Editor which is accessible from the Extras menu on The Asset Browser:

Open The Configuration EditorAll games made in GameMaker start with a "Default" configuration, which is listed in the editor when you first open it:

-

The Configuration EditorTo set up your configurations it is recommended that you first prepare this "Default" config by incorporating all the configurable assets for the project into it. To do this, simply go through the following list of options and set them to what is required by default:

+

The Configuration EditorTo set up your configurations it is recommended that you first prepare this "Default" config by incorporating all the configurable assets for the project into it. These are the settings that will be saved separately for each configuration that you make.

+

To do this, simply go through the following list of options and set them to what is required by default:

    +
  • Game Options: Set the default Game Options for each platform that requires it. 
  • Extension Options: Set the various "Copy to..." fields to the required platforms for the configuration. Any "Proxy" files created here will have their "Target" platform linked to the configuration too.
  • Sprite Editor: Set the texture group that you want the sprites to be added to.
  • Tileset Editor: Set the texture group that you want the tilesets to be added to.
  • Font Editor: Set the texture group that you want the fonts to be added to.
  • Texture Group Manager: Here you can set any of the properties on a per-configuration basis, including the parent group that a texture group belongs to.
    • -
  • Audio Group Manager: The sounds that are assigned to the different audio groups is configurable here..
    • +
  • Audio Group Manager: The sounds that are assigned to the different audio groups is configurable here.
  • Included Files: Set the "Copy to..." field to the required platforms for the configuration.

Once you have set up the default configuration, you can then add a new one to the Configuration Editor by right clicking RMB Icon on the configurations folder and selecting Add Config, or by clicking the "Create" button at the bottom of the window. The new configuration will be shown as a "child" of the default config - all user defined configurations are children of the default - and you can give it an appropriate name.

@@ -40,11 +42,11 @@

Configurations

- +
-
© Copyright YoYo Games Ltd. 2024 All Rights Reserved
+
© Copyright YoYo Games Ltd. 2026 All Rights Reserved
-

Physics Joint Constants

+

Physics Joint Constants

There are a great number of constants included within the GameMaker GML that are specific to joints between fixtures in the physics world. These can be used in conjunction with many of the different joint functions to set or get information from them in real time while the physics simulation is running. You should be aware, however, that complex calculations are done when you call these, so they should be used with care and only when necessary and note that many are unique to a specific type of joint. Also note that while you can get all these values with the appropriate function, you can only set those that are marked as not being read-only.

In general these constants would be used in conjunction with the following functions:

-

 

-

+

General

The following constants can be applied to any of the available joint types:

@@ -32,7 +31,7 @@

- + @@ -76,14 +75,12 @@

Physics Joint ConstantPhysics Joint Constant
Constant
-


- -

+

Motors

These constants are for those joints that have a motor attached to them (revolute, prismatic, wheel):

- + @@ -117,9 +114,7 @@


Physics Joint ConstantPhysics Joint Constant
Constant
-


- -

+

Revolute Joints

For a revolute joint you can use the following constant (as well as the motor constants if one has been added):

@@ -129,7 +124,7 @@


- + @@ -144,7 +139,7 @@


- + @@ -159,14 +154,12 @@


Physics Joint ConstantPhysics Joint Constant
Constant
phy_joint_angle_limitsEnable or disable angle limiting for the joint. Set the value to true to enable or false to disable.Enable or disable angle limiting for the joint. Set the value to true to enable or false to disable. No
-


- -

+

Prismatic Joints

For a prismatic joint you can use the following constant:

- + @@ -175,7 +168,7 @@


- + @@ -185,9 +178,7 @@


Physics Joint ConstantPhysics Joint Constant
Constant
phy_joint_translationGets the distance between the anchor x/y coordinates and the local x/y coordinates.The distance between the anchor x/y coordinates and the local x/y coordinates. Yes
-


- -

+

Distance Joints, Weld Joints and Wheel Joints

For a distance, weld, and wheel joints you can use the following constants (as well as those for pulley joints):

@@ -197,7 +188,7 @@


- + @@ -211,7 +202,7 @@


- + @@ -226,14 +217,12 @@


Physics Joint ConstantPhysics Joint Constant
Constant
phy_joint_frequencyThis will return (or set) the oscillation frequency for the joint, in hertz, and typically the frequency should be less than a half the frequency of the time step, as set by the function physics_world_update_speed().This will return (or set) the oscillation frequency for the joint, in hertz, and typically the frequency should be less than a half the frequency of the time step, as set by the function physics_world_update_speed. No
-


- -

+

Friction Joints

For a friction joint you can use the following constants:

- + @@ -252,14 +241,12 @@


Physics Joint ConstantPhysics Joint Constant
Constant
-


- -

+

Rope Joints

For a rope joint you can use the following constant:

- + @@ -282,7 +269,7 @@


Back: Joints
-

© Copyright YoYo Games Ltd. 2022 All Rights Reserved
+
© Copyright YoYo Games Ltd. 2026 All Rights Reserved

UI Element Properties

The Element List displays all UI layers and all parts of a UI layer, including Flex Panels and assets:

-

You can select a UI layer, Flex Panel or Asset Element in the Element List and its properties will be shown in The Inspector.

-

Besides being able to change the Element name and associated asset (if any), there are other properties which are described below for each type of Element.

+

You can select a UI layer, Flex Panel or Asset Element in the Element List and its properties will be shown in The Inspector. Besides being able to change the Element name and associated asset (if any), there are other properties which are described below for each type of Element.

These properties are represented at runtime by the Flex Panel Struct Members.

UI Layer Properties

A UI layer contains the following main properties:

@@ -114,7 +113,7 @@

Extra Options

-
© Copyright YoYo Games Ltd. 2025 All Rights Reserved
+
© Copyright YoYo Games Ltd. 2026 All Rights Reserved

physics_remove_fixture

-

This function removes (or "un-binds") a fixture from an instance or instances.

+

This function removes (or "un-binds") a bound fixture from an instance or instances.

It requires the unique "ID" of the bound fixture (as returned by the function physics_fixture_bind) and it will remove all the currently defined physics properties for the instance, permitting you to redefine a new fixture and bind that to the instance. In this way you can change the instance's physical properties without having to destroy and re-create it.

 

Syntax:

@@ -34,8 +34,8 @@

Syntax:

- - + +
Physics Joint ConstantPhysics Joint Constant
Constant
fixturePhysics Fixture IDThe ID of the fixture that is to be removed from the instanceRealThe ID of the bound fixture that is to be removed from the instance
@@ -44,18 +44,18 @@

Returns:

N/A

 

Example:

-

physics_remove_fixture(id, my_fix);

-

The code above will remove the fixture with the ID stored in the variable my_fix from the instance.

+

physics_remove_fixture(id, my_bound_fix);

+

The code above will remove the fixture with the ID stored in the variable my_bound_fix from the instance.

 

 

-
Back: Fixtures
- +
Back: Fixtures
+
-
© Copyright YoYo Games Ltd. 2025 All Rights Reserved
+
© Copyright YoYo Games Ltd. 2026 All Rights Reserved
-

Joints

+

Joints

In the GameMaker physics world, joints are used to constrain instances to the world or to each other. Typical examples in games include ragdolls, teeters, and pulleys, but joints can be combined in many different ways to create interesting motions or add realism to your game world.

-

NOTE: A joint does not need to be deleted when you destroy an instance joined to another instance, nor does it need to be deleted at the end of a room. Except in very specific cases (see the gear joint) as this is dealt with automatically by GameMaker.

+

 A joint does not need to be deleted when you destroy an instance joined to another instance, nor does it need to be deleted at the end of a room. Except in very specific cases (see the gear joint) as this is dealt with automatically by GameMaker.

The following pages explain the available joints and how they can be created:

 

Once a joint has been created, it can often be necessary to know its properties in order to change them at specific times in your game. The following functions (with their corresponding internal constants) are available to test and change joint values:

 

Additionally, you can use a number of constants from within GameMaker functions to get (or set) different properties of certain joints. These constants can all be found in the following section:

 

 

-

 

-
Back: Physics
- +
Back: Physics
+
-
© Copyright YoYo Games Ltd. 2022 All Rights Reserved
+
© Copyright YoYo Games Ltd. 2026 All Rights Reserved

physics_joint_distance_create

This function creates a distance joint between two physics instances.

-

One of the simplest joints is a distance joint which says that the distance between two points on two instances must be constant. When you specify a distance joint the two instances should already be created and have a fixture assigned, then you define the two anchor points in room coordinates. The first anchor point is connected to instance 1, the second anchor point is connected to instance 2 and the distance between these points imply the length of the distance constrain. The image below shows how this works:

-

Distance joint illustrationAs you can see, the anchor points are specified as room coordinates so care must be taken when defining them, especially if the instances are being created at the same time as the joints rather than being placed in the room through the room editor. You should also realise that the joints are created independently of the size of the sprite of the instances or the fixtures they have attached. So, if you create a distance joint somewhere other than the origin of the instance, it is still valid and will constrain the two instances relative to the position at which it was created. If you set the "col" value to true then the two instances can interact and collide with each other but only if they have collision events, however if it is set to false, they will not collide no matter what.

+

One of the simplest joints is a distance joint which says that the distance between two points on two instances must be constant. When you specify a distance joint the two instances should already be created and have a fixture assigned, then you define the two anchor points in room coordinates. The first anchor point is connected to instance 1, the second anchor point is connected to instance 2 and the distance between these points implies the length of the distance constraint. The image below shows how this works:

+

Distance joint illustrationAs you can see, the anchor points are specified as room coordinates so care must be taken when defining them, especially if the instances are being created at the same time as the joints rather than being placed in the room through the Room Editor. You should also realise that the joints are created independently of the size of the sprite of the instances or the fixtures they have attached. So, if you create a distance joint somewhere other than the origin of the instance, it is still valid and will constrain the two instances relative to the position at which it was created. If you set the col value to true then the two instances can interact and collide with each other but only if they have collision events. If it is set to false, however, they will not collide no matter what.

 

Syntax:

physics_joint_distance_create(inst1, inst2, w_anchor1_x, w_anchor1_y, w_anchor2_x, w_anchor2_y, col)

@@ -57,12 +57,12 @@

Syntax:

w_anchor2_y Real - the second y coordinate for the joint, within the game world + The second y coordinate for the joint, within the game world col Boolean - Whether the two instances can collide (true) or not (false) + Whether the two instances can collide (true) or not (false) @@ -82,15 +82,14 @@

Example:

The above code creates and defines a new fixture and then creates an instance of "obj_Rudder". The fixture is then assigned to the instance that is running the code as well as the newly created one and a joint is created between them. Finally the fixture is deleted as it is no longer needed.

 

 

-

 

-
Back: Joints
- +
Back: Joints
+
-
© Copyright YoYo Games Ltd. 2025 All Rights Reserved
+
© Copyright YoYo Games Ltd. 2026 All Rights Reserved

physics_joint_enable_motor

This function sets whether to enable or disable the motor on a physics joint that has a motor.

-

When you have a joint with a motor (prismatic or revolute), you may want to be able to switch the motor on or off depending on variables and conditions within the game. For this, you need to have stored the index of the joint previously in a variable and then you can switch the motor on or off by using this function and setting the "motor" argument to true or false.

+

When you have a joint with a motor (prismatic or revolute), you may want to be able to switch the motor on or off depending on variables and conditions within the game. For this, you need to have stored the index of the joint previously in a variable and then you can switch the motor on or off by using this function and setting the "motor" argument to true or false.

 

Syntax:

physics_joint_enable_motor(joint, motor)

@@ -35,7 +35,7 @@

Syntax:

motor Boolean - Whether you wish to turn the motor on (true) or off (false) + Whether you wish to turn the motor on (true) or off (false) @@ -58,15 +58,14 @@

Example:

The above code creates and defines a new fixture and then creates an instance of "obj_Door", binding the created fixture to the two instances. They are then joined by a revolute joint with no motor and the angles limited to a +/- 90 degree swing, and we store the joint index in the variable "perma_joint". We then switch the motor on using this variable, before finally deleting the fixture from memory as it is no longer needed.

 

 

-

 

-
Back: Joints
- +
Back: Joints
+
-
© Copyright YoYo Games Ltd. 2025 All Rights Reserved
+
© Copyright YoYo Games Ltd. 2026 All Rights Reserved

physics_joint_get_value

This function returns the value of the joint property corresponding to the given joint constant.

-

By using a series of predefined constants, you can ask GameMaker to tell you a number of things about the state of any given joint. This is very useful as it gives you the ability to delete joints or change an instances behaviour depending on whatever your needs are at the time. There are a number of constants that can be used in this function and they can be found here: Physics Joint Constants, but be aware that complex calculations are done when you call these, so they should be used with care and only when necessary and note that many are unique to a specific type of joint.

+

By using a series of predefined constants, you can ask GameMaker to tell you a number of things about the state of any given joint. This is very useful as it gives you the ability to delete joints or change an instance's behaviour depending on whatever your needs are at the time. There are a number of constants that can be used in this function and they can be found here: Physics Joint Constants, but be aware that complex calculations are done when you call these, so they should be used with care and only when necessary. Also note that many are unique to a specific type of joint.

If the property does not exist (if, for example, you check a pulley joint for prismatic translation) then 0 will be the return value.

 

Syntax:

@@ -60,15 +60,14 @@

Example:

The above code checks to see if the variable "shipJoint" holds a joint index and if it does, it then calculates the force being applied to that joint using the two constants. Finally, if the total force is greater than 2, the joint is deleted.

 

 

-

 

-
Back: Joints
- +
Back: Joints
+
-
© Copyright YoYo Games Ltd. 2025 All Rights Reserved
+
© Copyright YoYo Games Ltd. 2026 All Rights Reserved

physics_joint_pulley_create

This function creates a pulley joint between two physics instances.

-

The pulley joint is used to connect two instances within the physics world in such a way that moving one will directly influence the movement of the other. These joints are first anchored in the world space at two points, each one connected to an instance at its center of mass. This can be changed by setting the local anchor x/y coordinates relative to the origin of the instance, meaning that the actual connection from the instance to the physics world anchor point can be offset somewhere other than its origin. The following image illustrates this:

-

Pulley joint illustrationIf you look at inst2 you can see that its local anchor point has been offset 20 pixels to the "left" of its origin (Remember! The world anchor points are defined using the room coordinates, while the local anchor points are defined relative to the origin of the instance). You can also specify a ratio for the pulley joint, which tells one side or the other to move faster, with a value below 1 making the first instance move faster (E.G. 0.5 will make it move twice as fast) and a value above 1 making the second instance move faster (E.G. 2 will make it move twice as fast).

-

As with all the joints, if you set the "col" value to true then the two instances can interact and collide with each other but only if they have collision events, however if it is set to false, they will not collide no matter what.

+

The pulley joint is used to connect two instances within the physics world in such a way that moving one will directly influence the movement of the other. These joints are first anchored in the world space at two points, each one connected to an instance at its centre of mass. This can be changed by setting the local anchor x/y coordinates relative to the origin of the instance, meaning that the actual connection from the instance to the physics world anchor point can be offset somewhere other than its origin. The following image illustrates this:

+

Pulley joint illustrationIf you look at inst2 you can see that its local anchor point has been offset 20 pixels to the "left" of its origin (Remember! The world anchor points are defined using the room coordinates, while the local anchor points are defined relative to the origin of the instance). You can also specify a ratio for the pulley joint, which tells one side or the other to move faster, with a value below 1 making the first instance move faster (e.g. 0.5 will make it move twice as fast) and a value above 1 making the second instance move faster (e.g. 2 will make it move twice as fast).

+

As with all the joints, if you set the col value to true then the two instances can interact and collide with each other but only if they have collision events. If it is set to false, however, they will not collide no matter what.

 

Syntax:

physics_joint_pulley_create(inst1, inst2, w_anchor1_x, w_anchor1_y, w_anchor2_x, w_anchor2_y, l_anchor1_x, l_anchor1_y, l_anchor2_x, l_anchor2_y, ratio, col)

@@ -88,7 +88,7 @@

Syntax:

col Boolean - Whether the two instances can collide (true) or not (false) + Whether the two instances can collide (true) or not (false) @@ -100,24 +100,23 @@

Example:

var t_fix, inst1, inst2;
t_fix = physics_fixture_create();
physics_fixture_set_circle_shape(t_fix, 20);
- inst1 = instance_create_layer(150, room_height - 90, "Instances", obj_Block);
+ inst1 = instance_create_layer(150, room_height - 90, "Instances", obj_block);
inst2 = instance_create_layer(300, room_height - 90, "Instances", obj_block);
physics_fixture_bind(t_fix, inst1);
physics_fixture_bind(t_fix, inst2);
physics_joint_pulley_create(inst1, inst2, 150, room_height - 140, 300, room_height - 140, 0, 0, 0, 0, 2, 0);
physics_fixture_delete(t_fix);

-

The above code creates and defines a new fixture, creates two instances of "obj_Block", and then binds this fixture two them. It then goes on to define a pulley joint between these instance, with no offset for the joints, a ratio of 2:1 (meaning that inst2 will move faster). No collisions occur between the two instances in the pulley.

-

 

+

The above code creates and defines a new fixture, creates two instances of "obj_block", and then binds this fixture two them. It then goes on to define a pulley joint between these instance, with no offset for the joints, a ratio of 2:1 (meaning that inst2 will move faster). No collisions occur between the two instances in the pulley.

 

 

-
Back: Joints
- +
Back: Joints
+
-
© Copyright YoYo Games Ltd. 2025 All Rights Reserved
+
© Copyright YoYo Games Ltd. 2026 All Rights Reserved

physics_joint_rope_create

This function creates a rope joint between two physics instances.

-

A rope joint is one which is used to join two instances that you want to keep a constant distance apart, no matter what other forces are acting on it. With a distance joint, you can get "joint stretching" where the two fixtures will separate and behave strangely should too much stress be put on the joint, however the rope joint does not do this and will not stretch any further than the maximum defined length. When you create a rope joint the two instances should already be created and have a fixture assigned, then you define the two anchor points in room coordinates. The first anchor point is connected to instance 1, the second anchor point is connected to instance 2 and the distance and the maxlength argument sets the maximum length constraint on the joint. The image below shows how this works:

-

Rope joint illustrationAs you can see, the anchor points are specified as room coordinates so care must be taken when defining them, especially if the instances are being created at the same time as the joints rather than being placed in the room through the room editor. You should also realise that the joints are created independently of the size of the sprite of the instances or the fixtures they have attached. So, if you create a rope joint somewhere other than the origin of the instance, it is still valid and will constrain the two instances relative to the position at which it was created. If you set the "col" value to true then the two instances can interact and collide with each other but only if they have collision events, however if it is set to false, they will not collide no matter what.

+

A rope joint is one which is used to join two instances that you want to keep a constant distance apart, no matter what other forces are acting on it. With a distance joint, you can get "joint stretching" where the two fixtures will separate and behave strangely should too much stress be put on the joint. The rope joint, however, does not do this and will not stretch any further than the maximum defined length. When you create a rope joint the two instances should already be created and have a fixture assigned, then you define the two anchor points in room coordinates. The first anchor point is connected to instance 1, the second anchor point is connected to instance 2 and the distance and the maxlength argument sets the maximum length constraint on the joint. The image below shows how this works:

+

Rope joint illustrationAs you can see, the anchor points are specified as room coordinates so care must be taken when defining them, especially if the instances are being created at the same time as the joints rather than being placed in the room through the Room Editor. You should also realise that the joints are created independently of the size of the sprite of the instances or the fixtures they have attached. So, if you create a rope joint somewhere other than the origin of the instance, it is still valid and will constrain the two instances relative to the position at which it was created. If you set the col value to true then the two instances can interact and collide with each other but only if they have collision events. If it is set to false, however, they will not collide no matter what.

 

Syntax:

physics_joint_rope_create(inst1, inst2, w_anchor1_x, w_anchor1_y, w_anchor2_x, w_anchor2_y, maxlength, col)

@@ -67,7 +67,7 @@

Syntax:

col Boolean - Whether the two instances can collide (true) or not (false) + Whether the two instances can collide (true) or not (false) @@ -87,15 +87,14 @@

Example:

The above code creates and defines a new fixture and then creates an instance of "obj_Rudder". The fixture is then assigned to the instance that is running the code as well as the newly created one and a rope joint is created between them. Finally the fixture is deleted as it is no longer needed.

 

 

-

 

-
Back: Joints
- +
Back: Joints
+
-
© Copyright YoYo Games Ltd. 2025 All Rights Reserved
+
© Copyright YoYo Games Ltd. 2026 All Rights Reserved

physics_joint_set_value

This function sets the value of the joint property corresponding to the given joint constant to the given value.

-

Certain joint properties can be changed and set even after the creation of the joint. There are a number of constants that can be used in this function and they can be found here: Physics Joint Constants.

+

Certain joint properties can be changed and set even after the creation of the joint. There are a number of constants that can be used in this function and they can be found here: Physics Joint Constants.

 

Syntax:

physics_joint_set_value(joint, field, value)

@@ -56,15 +56,14 @@

Example:

The above code checks to see if the joints maximum motor torque is set to less than 2 and if it is it then sets it to 2.

 

 

-

 

-
Back: Joints
- +
Back: Joints
+
-
© Copyright YoYo Games Ltd. 2025 All Rights Reserved
+
© Copyright YoYo Games Ltd. 2026 All Rights Reserved

physics_fixture_bind

This function binds the given fixture to the given target object or instance and returns the ID of the bound fixture.

-

Once we have defined our fixture it has to be bound to an instance. This means that its properties are transferred to the selected instance, not the actual fixture itself, so that one fixture can be bound to multiple instances if all are to have the same properties. You can specify an object index for the target and all instances of that object present in the room at the time will receive that fixture's properties (but not any new instances of the object created later), or you can use the special keywords other and all. You can even specify a parent object and all children instances with that parent will also receive the fixture. Once the fixture has been bound to all the instances that you need, it can be deleted if no longer necessary and the instances with that fixture's properties will not be affected and maintain those properties.

+

Once we have defined our fixture it has to be bound to an instance. This means that its properties are transferred to the selected instance, not the actual fixture itself, so that one fixture can be bound to multiple instances if all are to have the same properties. You can specify an object index for the target and all instances of that object present in the room at the time will receive that fixture's properties (but not any new instances of the object created later), or you can use the special keywords other and all. You can even specify a parent object and all instances that are instances of children of that parent object will also receive the fixture. Once the fixture has been bound to all the instances that you need, it can be deleted if no longer necessary and the instances with that fixture's properties will not be affected and maintain those properties.

The fixture will be bound to the instance with the centre of mass being positioned at the origin of the instance, and polygon fixtures are bound based on the position of the points relative to the origin. If you require your fixture to be bound to a point other than the origin then you should be using physics_fixture_bind_ext.

-

Physics fixture binding exampleThe function will also return a unique "id" value for the bound fixture (not the fixture itself) which can then be used to remove ("un-bind") the physics properties from the instance using the function physics_remove_fixture. This permits you to add and remove physical properties from an instance without destroying and re-creating objects.

+

Physics fixture binding exampleThe function will also return a unique "id" value for the bound fixture (not the fixture itself) which can then be used to remove ("un-bind") the physics properties from the instance using the function physics_remove_fixture. This permits you to add and remove physical properties from an instance without destroying and re-creating instances.

 Fixtures should be deleted when no longer needed as failure to do so may cause a memory leak which will slow down and eventually crash your game.

 

Syntax:

@@ -47,14 +47,17 @@

Returns:

Physics Bound Fixture ID

 

Example:

-

var _fix, _inst;
- _fix = physics_fixture_create();
+

Create Event

+

var _fix = physics_fixture_create();
physics_fixture_set_circle_shape(_fix, 16);
physics_fixture_set_density(_fix, 1.0);
- inst = instance_create_layer(x, y, "Instances", genericBodyObject);
- my_fix = physics_fixture_bind(_fix, inst);
+ my_bound_fix = physics_fixture_bind(_fix, id);
physics_fixture_delete(_fix);

-

The code above will create a fixture and assign its index to the temporary variable _fix. It then defines the shape and density of the fixture before binding it to the instance that was created with the index for the bound fixture stored in the variable my_fix. Finally, the fixture is deleted to prevent memory leaks as it is no longer needed.

+

Clean Up Event

+

physics_remove_fixture(id, my_bound_fix);

+

The code above shows how to bind a physics fixture to the instance executing the code and remove it afterwards.

+

In the Create event, a fixture is created and its index is assigned to a temporary variable _fix. The shape and density of the fixture are then defined and the fixture is bound to the calling instance with the index for the bound fixture stored in the instance variable my_bound_fix. Finally, the fixture is deleted to prevent memory leaks as it is no longer needed.

+

In the Clean Up event, the bound fixture is removed.

 

 

@@ -64,7 +67,7 @@

Example:

-
© Copyright YoYo Games Ltd. 2025 All Rights Reserved
+
© Copyright YoYo Games Ltd. 2026 All Rights Reserved
\ No newline at end of file From 263381ae179c6d18a5105eae65605be896a60ab3 Mon Sep 17 00:00:00 2001 From: Gurpreet Singh Matharoo Date: Tue, 17 Mar 2026 17:04:26 +0530 Subject: [PATCH 088/108] docs(feature): asset_get_index can take an asset handle https://github.com/YoYoGames/GameMaker-Bugs/issues/14277 --- .../Asset_Management/Assets_And_Tags/asset_get_index.htm | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/Manual/contents/GameMaker_Language/GML_Reference/Asset_Management/Assets_And_Tags/asset_get_index.htm b/Manual/contents/GameMaker_Language/GML_Reference/Asset_Management/Assets_And_Tags/asset_get_index.htm index f9f9e3d44..a6662dc52 100644 --- a/Manual/contents/GameMaker_Language/GML_Reference/Asset_Management/Assets_And_Tags/asset_get_index.htm +++ b/Manual/contents/GameMaker_Language/GML_Reference/Asset_Management/Assets_And_Tags/asset_get_index.htm @@ -16,8 +16,9 @@

asset_get_index

-

This function gets the handle for a game asset from its name.

-

If the asset is not found, the function will return a value of -1, otherwise it will return the handle for the asset being checked. This handle can then be used in other functions as you would any other handle, like sprite_index or path_index, for example.

+

This function gets the handle for an Asset from its name.

+

 If an Asset handle is passed, its index number is returned (similar to passing a handle into real). 

+

If the asset is not found, the function will return a value of -1. This handle can then be used in other functions as you would any other handle, like sprite_index or path_index, for example.

Usage Notes

  • Although this function can be used to reference assets from strings (see the first example below), you should always make sure that the asset exists before using it. Otherwise, you may get errors that will crash your game.
    • @@ -35,7 +36,7 @@

    Syntax:

    name - String + String or Asset The name of the game asset to get the handle of (a string). @@ -73,7 +74,7 @@

    Example 2: "MarkTagAsUsed" pragma

-
© Copyright YoYo Games Ltd. 2025 All Rights Reserved
+
© Copyright YoYo Games Ltd. 2026 All Rights Reserved
@@ -30,7 +29,7 @@

Guide To Using ParticlesCreate Particle System

 The layer name supplied must be a valid layer in the room where the system will be used, otherwise no particles will be visible. Also note that we set the persistent flag (both in GML Code and in GML Visual) to false. A persistent particle system is one that will "persist" across rooms without the need to destroy and re-create it for each room. However, to keep things simple for this guide, we'll not be using persistence.

So that's the system created, but what about the particles? We have to define them too or the system is useless and does nothing.

-

If you already have a Particle System Asset, you can create it using the above function/action by passing the asset into the partsys/"System" argument.

+

If you already have a Particle System Asset, you can create it using the above function/action by passing the asset into the partsys/"System" argument.

 

Defining A Particle Type

@@ -161,7 +160,7 @@

Guide To Using ParticlesNext: Guide To Using Shaders -
© Copyright YoYo Games Ltd. 2025 All Rights Reserved
+
© Copyright YoYo Games Ltd. 2026 All Rights Reserved

window_set_max_height

-

This function can be used to set a maximum window height for your game. If you enable the window resize option in the Game Options for the target platform, then the player can resize the game window to any size they wish, however by using this function you can limit the maximum height to the size you specify. If you wish to go back to the default behaviour (ie: no minimum), then use a value of -1.

+

This function can be used to set a maximum window height for your game. If you enable the window resize option in the Game Options for the target platform, then the player can resize the game window to any size they wish, however by using this function you can limit the maximum height to the size you specify. If you wish to go back to the default behaviour (i.e.: no minimum), then use a value of -1.

 

Syntax:

@@ -55,7 +55,7 @@

Example:

-
© Copyright YoYo Games Ltd. 2024 All Rights Reserved
+
© Copyright YoYo Games Ltd. 2026 All Rights Reserved
diff --git a/Manual/contents/GameMaker_Language/GML_Reference/Variable_Functions/array_foreach.htm b/Manual/contents/GameMaker_Language/GML_Reference/Variable_Functions/array_foreach.htm index 5d37721d3..0d0a0900e 100644 --- a/Manual/contents/GameMaker_Language/GML_Reference/Variable_Functions/array_foreach.htm +++ b/Manual/contents/GameMaker_Language/GML_Reference/Variable_Functions/array_foreach.htm @@ -6,15 +6,12 @@ array_foreach - - + + + + +

array_foreach

diff --git a/Manual/contents/GameMaker_Language/GML_Reference/Variable_Functions/ref_create.htm b/Manual/contents/GameMaker_Language/GML_Reference/Variable_Functions/ref_create.htm index a3d977859..f5e21566f 100644 --- a/Manual/contents/GameMaker_Language/GML_Reference/Variable_Functions/ref_create.htm +++ b/Manual/contents/GameMaker_Language/GML_Reference/Variable_Functions/ref_create.htm @@ -6,13 +6,12 @@ ref_create - - From 3816fcb108adee9a59f80f1f391f09a08c8084ab Mon Sep 17 00:00:00 2001 From: YYBartT Date: Fri, 20 Mar 2026 13:58:46 +0100 Subject: [PATCH 102/108] docs(general): manually add some missing tags & keywords YoYoGames/GameMaker-Manual#372 --- .../GML_Reference/Debugging/dbg_colour.htm | 8 +++++--- .../Drawing/Colour_And_Alpha/make_colour_rgb.htm | 3 ++- 2 files changed, 7 insertions(+), 4 deletions(-) diff --git a/Manual/contents/GameMaker_Language/GML_Reference/Debugging/dbg_colour.htm b/Manual/contents/GameMaker_Language/GML_Reference/Debugging/dbg_colour.htm index 5cd1b745b..e597f6a36 100644 --- a/Manual/contents/GameMaker_Language/GML_Reference/Debugging/dbg_colour.htm +++ b/Manual/contents/GameMaker_Language/GML_Reference/Debugging/dbg_colour.htm @@ -9,8 +9,8 @@ - - + + @@ -71,12 +71,14 @@

Example:

-
© Copyright YoYo Games Ltd. 2025 All Rights Reserved
+
© Copyright YoYo Games Ltd. 2026 All Rights Reserved
diff --git a/Manual/contents/GameMaker_Language/GML_Reference/Drawing/Colour_And_Alpha/make_colour_rgb.htm b/Manual/contents/GameMaker_Language/GML_Reference/Drawing/Colour_And_Alpha/make_colour_rgb.htm index e494ee493..2dae07765 100644 --- a/Manual/contents/GameMaker_Language/GML_Reference/Drawing/Colour_And_Alpha/make_colour_rgb.htm +++ b/Manual/contents/GameMaker_Language/GML_Reference/Drawing/Colour_And_Alpha/make_colour_rgb.htm @@ -62,7 +62,7 @@

Example:

-
© Copyright YoYo Games Ltd. 2025 All Rights Reserved
+
© Copyright YoYo Games Ltd. 2026 All Rights Reserved
\ No newline at end of file From cc16bd378c83a1c612c72b84db24e20730a2e2a2 Mon Sep 17 00:00:00 2001 From: YYBartT Date: Tue, 24 Mar 2026 16:20:44 +0100 Subject: [PATCH 103/108] docs(general): clarify that DS grid cells can store values of any data type YoYoGames/GameMaker-Bugs#14358 --- .../GML_Reference/Data_Structures/DS_Grids/DS_Grids.htm | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Manual/contents/GameMaker_Language/GML_Reference/Data_Structures/DS_Grids/DS_Grids.htm b/Manual/contents/GameMaker_Language/GML_Reference/Data_Structures/DS_Grids/DS_Grids.htm index 62872e484..1fb67b958 100644 --- a/Manual/contents/GameMaker_Language/GML_Reference/Data_Structures/DS_Grids/DS_Grids.htm +++ b/Manual/contents/GameMaker_Language/GML_Reference/Data_Structures/DS_Grids/DS_Grids.htm @@ -15,7 +15,7 @@

DS Grids

-

A DS grid is a data structure that stores information across 2 dimensions. You define the grid by setting its integer width and height, which sets the total number of "cells" within the grid (the width and height multiplied). These cells are then used to hold different data values (real numbers or strings).

+

A DS grid is a data structure that stores information across 2 dimensions. You define the grid by setting its integer width and height, which sets the total number of "cells" within the grid (the width and height multiplied). These cells are then used to hold values which can be of any data type (e.g., real numbers or strings).

DS Grid ExampleThis type of structure allows you to set and retrieve the value of cells in the grid by giving the x and y index of it (which starts with 0 for both the x and the y axis and goes up to the width - 1 and the height -1). But you can also set the value in specific grid regions, add single values, and retrieve the sum, maximum, minimum, and mean value over a given region, making this data structure the most versatile of all those available to you.

When accessing DS grid data structures, you should always try to use integer values for the cell position, and all non-integer indices will be floored by GameMaker if you do not. If that is not what you require, then you will need to do the rounding yourself previously before passing the index that you wish to check.

@@ -82,7 +82,7 @@

MP Grid

Next: DS Lists
-
© Copyright YoYo Games Ltd. 2024 All Rights Reserved
+
© Copyright YoYo Games Ltd. 2026 All Rights Reserved
+ \ No newline at end of file From cbb035751405b370a65a974486523c7ea67bf4a8 Mon Sep 17 00:00:00 2001 From: YYBartT Date: Wed, 25 Mar 2026 22:44:39 +0100 Subject: [PATCH 105/108] docs(general): add missing index and search keywords in batch using script YoYoGames/GameMaker-Manual#372 * Added the function name to content tags that had an empty string as the value --- .../Audio/Audio_Groups/audio_group_get_assets.htm | 4 ++-- .../Audio/Audio_Groups/audio_sound_get_audio_group.htm | 4 ++-- .../Asset_Management/Audio/audio_system_is_initialised.htm | 4 ++-- .../GML_Reference/Debugging/dbg_text_separator.htm | 4 ++-- .../Particles/Particle_Emitters/part_emitter_enable.htm | 4 ++-- .../Particles/Particle_Emitters/part_emitter_relative.htm | 4 ++-- .../Drawing/Primitives/vertex_format_get_info.htm | 4 ++-- .../Drawing/Primitives/vertex_update_buffer_from_vertex.htm | 4 ++-- .../Drawing/Surfaces/surface_get_texture_depth.htm | 4 ++-- .../GML_Reference/Variable_Functions/instanceof.htm | 2 +- 10 files changed, 19 insertions(+), 19 deletions(-) diff --git a/Manual/contents/GameMaker_Language/GML_Reference/Asset_Management/Audio/Audio_Groups/audio_group_get_assets.htm b/Manual/contents/GameMaker_Language/GML_Reference/Asset_Management/Audio/Audio_Groups/audio_group_get_assets.htm index 5a384fd35..7b0eb90a7 100644 --- a/Manual/contents/GameMaker_Language/GML_Reference/Asset_Management/Audio/Audio_Groups/audio_group_get_assets.htm +++ b/Manual/contents/GameMaker_Language/GML_Reference/Asset_Management/Audio/Audio_Groups/audio_group_get_assets.htm @@ -9,8 +9,8 @@ - - + + diff --git a/Manual/contents/GameMaker_Language/GML_Reference/Asset_Management/Audio/Audio_Groups/audio_sound_get_audio_group.htm b/Manual/contents/GameMaker_Language/GML_Reference/Asset_Management/Audio/Audio_Groups/audio_sound_get_audio_group.htm index 704a86aef..02770aac2 100644 --- a/Manual/contents/GameMaker_Language/GML_Reference/Asset_Management/Audio/Audio_Groups/audio_sound_get_audio_group.htm +++ b/Manual/contents/GameMaker_Language/GML_Reference/Asset_Management/Audio/Audio_Groups/audio_sound_get_audio_group.htm @@ -9,8 +9,8 @@ - - + + diff --git a/Manual/contents/GameMaker_Language/GML_Reference/Asset_Management/Audio/audio_system_is_initialised.htm b/Manual/contents/GameMaker_Language/GML_Reference/Asset_Management/Audio/audio_system_is_initialised.htm index 9b0461e81..c747c38bb 100644 --- a/Manual/contents/GameMaker_Language/GML_Reference/Asset_Management/Audio/audio_system_is_initialised.htm +++ b/Manual/contents/GameMaker_Language/GML_Reference/Asset_Management/Audio/audio_system_is_initialised.htm @@ -9,8 +9,8 @@ - - + + diff --git a/Manual/contents/GameMaker_Language/GML_Reference/Debugging/dbg_text_separator.htm b/Manual/contents/GameMaker_Language/GML_Reference/Debugging/dbg_text_separator.htm index c6bb7345f..036d7d055 100644 --- a/Manual/contents/GameMaker_Language/GML_Reference/Debugging/dbg_text_separator.htm +++ b/Manual/contents/GameMaker_Language/GML_Reference/Debugging/dbg_text_separator.htm @@ -9,8 +9,8 @@ - - + + diff --git a/Manual/contents/GameMaker_Language/GML_Reference/Drawing/Particles/Particle_Emitters/part_emitter_enable.htm b/Manual/contents/GameMaker_Language/GML_Reference/Drawing/Particles/Particle_Emitters/part_emitter_enable.htm index cb0ae4456..4d9484c9b 100644 --- a/Manual/contents/GameMaker_Language/GML_Reference/Drawing/Particles/Particle_Emitters/part_emitter_enable.htm +++ b/Manual/contents/GameMaker_Language/GML_Reference/Drawing/Particles/Particle_Emitters/part_emitter_enable.htm @@ -9,8 +9,8 @@ - - + + diff --git a/Manual/contents/GameMaker_Language/GML_Reference/Drawing/Particles/Particle_Emitters/part_emitter_relative.htm b/Manual/contents/GameMaker_Language/GML_Reference/Drawing/Particles/Particle_Emitters/part_emitter_relative.htm index 5c69596ea..a71c46296 100644 --- a/Manual/contents/GameMaker_Language/GML_Reference/Drawing/Particles/Particle_Emitters/part_emitter_relative.htm +++ b/Manual/contents/GameMaker_Language/GML_Reference/Drawing/Particles/Particle_Emitters/part_emitter_relative.htm @@ -9,8 +9,8 @@ - - + + diff --git a/Manual/contents/GameMaker_Language/GML_Reference/Drawing/Primitives/vertex_format_get_info.htm b/Manual/contents/GameMaker_Language/GML_Reference/Drawing/Primitives/vertex_format_get_info.htm index 13762cdfe..d93ea6911 100644 --- a/Manual/contents/GameMaker_Language/GML_Reference/Drawing/Primitives/vertex_format_get_info.htm +++ b/Manual/contents/GameMaker_Language/GML_Reference/Drawing/Primitives/vertex_format_get_info.htm @@ -9,8 +9,8 @@ - - + + diff --git a/Manual/contents/GameMaker_Language/GML_Reference/Drawing/Primitives/vertex_update_buffer_from_vertex.htm b/Manual/contents/GameMaker_Language/GML_Reference/Drawing/Primitives/vertex_update_buffer_from_vertex.htm index 8ef4a82c8..4c18621a4 100644 --- a/Manual/contents/GameMaker_Language/GML_Reference/Drawing/Primitives/vertex_update_buffer_from_vertex.htm +++ b/Manual/contents/GameMaker_Language/GML_Reference/Drawing/Primitives/vertex_update_buffer_from_vertex.htm @@ -9,8 +9,8 @@ - - + + diff --git a/Manual/contents/GameMaker_Language/GML_Reference/Drawing/Surfaces/surface_get_texture_depth.htm b/Manual/contents/GameMaker_Language/GML_Reference/Drawing/Surfaces/surface_get_texture_depth.htm index 36a3362ad..6f74a4676 100644 --- a/Manual/contents/GameMaker_Language/GML_Reference/Drawing/Surfaces/surface_get_texture_depth.htm +++ b/Manual/contents/GameMaker_Language/GML_Reference/Drawing/Surfaces/surface_get_texture_depth.htm @@ -9,8 +9,8 @@ - - + + diff --git a/Manual/contents/GameMaker_Language/GML_Reference/Variable_Functions/instanceof.htm b/Manual/contents/GameMaker_Language/GML_Reference/Variable_Functions/instanceof.htm index 97dbf9337..c88431530 100644 --- a/Manual/contents/GameMaker_Language/GML_Reference/Variable_Functions/instanceof.htm +++ b/Manual/contents/GameMaker_Language/GML_Reference/Variable_Functions/instanceof.htm @@ -10,7 +10,7 @@ - + From 34409d540960d223d47fe781f0cf77311309452a Mon Sep 17 00:00:00 2001 From: YYBartT Date: Wed, 25 Mar 2026 22:52:18 +0100 Subject: [PATCH 106/108] docs(general): fix keywords on DnD page YoYoGames/GameMaker-Manual#372 --- .../Instance/Change_Object_Instance.htm | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Manual/contents/Drag_And_Drop/Drag_And_Drop_Reference/Instance/Change_Object_Instance.htm b/Manual/contents/Drag_And_Drop/Drag_And_Drop_Reference/Instance/Change_Object_Instance.htm index d0db44bd4..93b565251 100644 --- a/Manual/contents/Drag_And_Drop/Drag_And_Drop_Reference/Instance/Change_Object_Instance.htm +++ b/Manual/contents/Drag_And_Drop/Drag_And_Drop_Reference/Instance/Change_Object_Instance.htm @@ -9,8 +9,8 @@ - - + + From e07f4846fd6208312e3a85acdd3cf2cd252a16ae Mon Sep 17 00:00:00 2001 From: YYBartT Date: Wed, 25 Mar 2026 23:04:25 +0100 Subject: [PATCH 107/108] docs(general): fix a few missing items in table of contents YoYoGames/GameMaker-Manual#372 --- .../Drawing/GPU_Control/gpu_get_stencil_read_mask.htm | 4 ++-- Manual/toc/Default.toc | 3 +++ 2 files changed, 5 insertions(+), 2 deletions(-) diff --git a/Manual/contents/GameMaker_Language/GML_Reference/Drawing/GPU_Control/gpu_get_stencil_read_mask.htm b/Manual/contents/GameMaker_Language/GML_Reference/Drawing/GPU_Control/gpu_get_stencil_read_mask.htm index 38c08227e..c4035f40e 100644 --- a/Manual/contents/GameMaker_Language/GML_Reference/Drawing/GPU_Control/gpu_get_stencil_read_mask.htm +++ b/Manual/contents/GameMaker_Language/GML_Reference/Drawing/GPU_Control/gpu_get_stencil_read_mask.htm @@ -34,11 +34,11 @@

Example:

- +
-
© Copyright YoYo Games Ltd. 2024 All Rights Reserved
+
© Copyright YoYo Games Ltd. 2026 All Rights Reserved