Game maker studio 2 movement free#

Game maker studio 2 movement free#

To test this feature, a feature has been added to set additional walls onto free grid positions (left mouse button) and to remove those walls again (right mouse button). To make this work, the object representing the obstacle needs to be flagged as 'solid' in the object properties. The player object stops when the target grid position is already occupied by a solid object. The whole queue handling is implemented in 4 scripts (name keyb_buffer_*) which are called from the player object. This gives a pretty satisfying gaming experience for all keyboard artists. If a key was released, it is removed from its current position and the other (still pressed) keys will move up if required. To make this a bit smoother, a queue was introduced to hold the exact sequence in which the arrow keys have been pressed. If just the pressed keys are queried, then the game decides which direction has priority due to the sequence the keys are evaluated in the program. This is difficult in situations where more than one arrow key is pressed simultaneously.

During this time, a lot can happen and the player might panically push other keys to control the player object. The speed of the player input is set to 4 pixels / frame, so it takes 8 frames to complete the move.

This is intended, because we are in a grid-based game! While traveling from one grid position to the next, the player object is not reacting on any input. This project is not yet finished and is continuously improved. This computed input is considered to come from the motion planning module of this Game Make example project. This command can either be a keyboard input (arrow keys) or a computed input from the game. The moving object is either in the process of moving to the next position (is_moving = true) or is standing still and waiting for a command to move (is_moving = false). Only horizontal and vertical moves are allowed. The grid consists of squares (32 x 32 pixels). The grid-based approach I needed was an object (player or enemy) which moves from a grid position to the next. This is why I started this little exercise. I found them inconvenient to be used with a grid based approach. Grid-based Movement in Game Maker Studio 2ДЄlthough Game Maker provides a lot of motion planning (mp_*) functions, they do not seem to match all situations.