4 replies to this topic

[wimlore]

• Title: RW's Top-Down Movement Example
• Description: This example is intended to provide you with a method of allowing arrow-key events to override each other equally.
• GM Version: :GM8:
• Registered: no
• File Type: .gmk
• File Size: 0.01 MB
• File Link: rw_td_movement_example from Host-A.net
• Required Extensions: N/A
• Required DLLs: N/A

Summary:
Thank you for your interest in my example!
Please read the Help File included in the example to have a complete understanding of how this movement method works.

The Issue: Did you ever notice how the events for the right arrow key override the left arrow key? This is due to the event order. Just like a stack of 'if statements', where the one on top will always execute first. I have tried many ways to work around this, and so far this is the best alternative I could come up with.

Mechanics: The object has five variables declared within it's create event. Four of the variables are to represent the four directions: up, down, left, and right. The fifth variable represents the direction the object will eventually go.

Each of these variables will increment in value while the corresponding keys are being pressed.

In the 'Key-Press Event' of an arrow key, the values of the other directions gets reset to zero.

In the 'Key-Release Event' of an arrow key, the value of that direction gets reset to zero.

In the Step Event, the variable 'max_value' uses the function 'max()' on all four directional values. Then, a switch statement compares the max_value variable with the four directional values to determine which direction the object will go, using the 'motion_set()' function.

The Results: Each Arrow Key Event has the capability of overriding each other. Thus, allowing the user to button mash arrow keys with more consistent movement.

Object's Information(Incase you do not want to download the example)

Spoiler

Information about object: obj_ball_advanced

Sprite: spr_ball_advanced
Solid: false
Visible: true
Depth: 0
Persistent: false
Parent: <no parent>
Mask: <same as sprite>

Create Event:
execute code:

left_val = 0;
right_val = 0;
up_val = 0;
down_val = 0;
max_val = 0;


Step Event:
execute code:

max_val = max(left_val, right_val, up_val, down_val);
if max_val == 0
{
speed = 0;
exit;
}
switch max_val
{
case left_val: motion_set(180,2); break;
case right_val: motion_set(0, 2); break;
case up_val: motion_set(90, 2); break;
case down_val: motion_set(270,2); break;
}


Keyboard Event for <Left> Key:
execute code:

left_val += 1;


Keyboard Event for <Up> Key:
execute code:

up_val += 1;


Keyboard Event for <Right> Key:
execute code:

right_val += 1;


Keyboard Event for <Down> Key:
execute code:

down_val += 1;


Key Press Event for <Left> Key:
execute code:

left_val += 1;
right_val = 0;
up_val = 0;
down_val = 0;


Key Press Event for <Up> Key:
execute code:

left_val = 0;
right_val = 0;
up_val += 1;
down_val = 0;


Key Press Event for <Right> Key:
execute code:

left_val = 0;
right_val += 1;
up_val = 0;
down_val = 0;


Key Press Event for <Down> Key:
execute code:

left_val = 0;
right_val = 0;
up_val = 0;
down_val += 1;


Key Release Event for <Left> Key:
execute code:

left_val = 0;


Key Release Event for <Up> Key:
execute code:

up_val = 0;


Key Release Event for <Right> Key:
execute code:

right_val = 0;


Key Release Event for <Down> Key:
execute code:

down_val = 0;

GMC Search Tags
GMCTUTORIAL GMCTOPDOWN GMCMOVEMENT

[GMkizzle]

Okay almost solid, but there is a problem.
If you hold 'up' and press the 'left' and 'right' keys, the player will only move left and right, and in no way north/up.

Nice work so far

[wimlore]

Hello Firstly, I want to say thanks for sharing my interest in this endeavor!

What you described is exactly what I wanted to happen!

If I were to 'Hold' UP and 'Press' LEFT and/or RIGHT the user should only go left or right, depending on which key was pressed last.
Since the last pressed key is always the direction the user will go.
The same works if you were to 'Hold' LEFT and 'Press' UP and/or DOWN.

Sorry maybe I should have mentioned this is 4-Directions only, and no diagonal?

[Thagrahn]

So, this is just to get around GameMaker checking the keys in a set order.

The code seems a little over the top, but is similar to what I have seen done to make sure the player isn't holding the left and right movement keys at the same time.

Wouldn't be to hard to edit this so the diagonals can be used as well, but otherwise looks like it does what it was designed for.

[wimlore]

You're right, Thagrahn. The code is a bit over the top. Also, it is actually really easy to adjust this example to work for diagonal movement. Which is probebly why no one has asked how. But for kicks, I rewrote some code and got a decent method. Hope this doesn't scare away all the drag & droppers. After all, it's just a little copy and paste

Here is the modified obj_ball_advanced's information

Spoiler

Information about object: obj_ball_advanced

Sprite: spr_ball_advanced
Solid: false
Visible: true
Depth: 0
Persistent: false
Parent: <no parent>
Mask: <same as sprite>

Create Event:
execute code:

left_val = 0;
right_val = 0;
up_val = 0;
down_val = 0;


Step Event:
execute code:

//Input
if keyboard_check(vk_left) left_val += 1;
if keyboard_check(vk_right) right_val += 1;
if keyboard_check(vk_up) up_val += 1;
if keyboard_check(vk_down) down_val += 1;
if keyboard_check_released(vk_left) left_val = 0;
if keyboard_check_released(vk_right) right_val = 0;
if keyboard_check_released(vk_up) up_val = 0;
if keyboard_check_released(vk_down) down_val = 0;

//Movement
if (left_val == 0 and right_val == 0) hspeed = 0;
if (up_val == 0 and down_val == 0) vspeed = 0;
if (left_val > 0 and left_val > right_val) hspeed = -2;
if (right_val > 0 and right_val > left_val) hspeed = 2;
if (up_val > 0 and up_val > down_val) vspeed = -2;
if (down_val > 0 and down_val > up_val) vspeed = 2;

First what I did was I got rid of all the key-press events, since resetting the directional values every key-press would prevent me from being able to move diagonally.
Then I got rid of max_val, since I would want to be moving in more than 1 direction at a time.
Finally I changed the movement style to hspeed and vspeed instead of using motion_set(), and compressed everything into the step event.