Retro RPG Movement (Grid)

[hellii]

I've been working on something involving grid-movement, I found an example where it in essence used 4 flags (up, down, left and right) and it uses a counter going to 32 (adding 1 every 22 milliseconds; so it moves 32 pixels at a time, and shows the movement so you can see the animations). The thing is, sometimes it would get off the 'grid'. I tried increasing the time to 1.5 seconds, and it never got off the 'grid'... so I think sometimes the thread "skips a beat".

If I'm right, using the timer for movement is not optimal, as I never want the player to get off the 'grid'. Is there a better way to do a grid-based movement of 4 directions, and still showing the animation from one tile to the other (so it's not moved the 32 pixels in the direction right away; that is easy :P)

Thanks in advance. I'd appreciate it if I could get a pointer without showing any of my code, as it's quite lengthy.

[Asholay]

This is an old file of mine which does grid movement.

Grid.mfa

Does that help?

[nivram]

I also have a four direction fast loop grid movement on my website. Use number 2.

Link:
http://castles-of-britain.com/mmfexamples-e.htm

Marv

[SpringUp]

Hello.

The best choice for engine displacement player character rpg card is the four directions box by box.

Examples (6 lines):
http://files.getwebb.org/download.php?id=cre63eaj

Bye.

[hellii]

Even after literally copying everything from Nivram and Springup into my own project to try it out, it sometimes goes off grid and gets stuck in the obstacles. It works fine when I run it in your own files.
This makes no sense at all; considering I've actually copied the exact same thing.

[nivram]

Even after literally copying everything from Nivram and Springup into my own project to try it out, it sometimes goes off grid and gets stuck in the obstacles. It works fine when I run it in your own files.
This makes no sense at all; considering I've actually copied the exact same thing.

If it is not too late, build your engine around one of the examples instead of trying to add the example to your game.

Marv

[hellii]

Could be last resort, but it would be awesome if I knew what was wrong..

[hellii]

I've just tried to put the whole of my project into the example. Then I took the objects from the example and put it into the first frame I got of my game... and it does the same thing: sometimes snaps to the obstacles. It makes no sense at all, it's as if something in my own code collides with the example code, but it's separate. It's really frustrating when something that SHOULD work just doesn't. And it pains me not to know what the problem is.

Springup's example was what I used, and I actually get the same problem when I tried navrim's example. It works fine in the example file, but when I put the whole thing into my own, it collides and gets stuck with the obstacles on the map.

[Caesar]

helliii, I'm not sure if this is what you want, but if you want your player to move 32 pixels before coming to a stop, you need to do something like this:

Repeat while "player" moved left
+Alterable value a of "player" = 0
- set direction left
- set Alterable value a to 32

"player" is facing a direction left
+ Alterable value a>0
- set x position to x position("player")-1
- sub 1 from Alterable value a

The above will make the player move left 1 pixel 32 times. To prevent the player overlapping obstacles, add a sensor 32 pixels to the left of the player. And add the following to the first line of code:

X(negate) "left sensor" is overlapping a backdrop

When done, your code should look something like this:

Repeat while "player" moved left
+ Alterable value a of "player" = 0
+ X(negate) "left sensor" is overlapping a backdrop
- set direction left
- set Alterable value a to 32

"player" is facing a direction left
+ Alterable value a>0
- set x position to x position("player")-1
- sub 1 from Alterable value a

For the sensor:

Always
- Set position at (-32,0) from "player"


Do the same for the other directions and place each new sensor on the correct side of the player.

[Asholay]

helliii, I'm not sure if this is what you want, but if you want your player to move 32 pixels before coming to a stop, you need to do something like this:

That's the method I use in the above posted example file - works fine, no need for fast loops or any resource hungry coding - and perfectly reliable.