Graal Forums - Movement Sliding

Graal Forums (https://forums.graalonline.com/forums/index.php)

- NPC Scripting (https://forums.graalonline.com/forums/forumdisplay.php?f=8)

- - Movement Sliding (https://forums.graalonline.com/forums/showthread.php?t=64247)

projectigi

02-20-2006 11:17 PM

Movement Sliding

Hi,

well u all know that the classic movement "slides" around edges...

whats the best way to put this into a scripted movement?
Only thing i could think of is testing coordinates at a slightly offset place and if theres no wall move the char towards this place =/

Any better solutions?

ApothiX

02-21-2006 03:12 PM

I was also wondering how this would be accomplished :x

Polo	02-21-2006 04:42 PM

To do it, theres a few certain rules to consider.

1) We only need to do the sliding when only one direction is being pressed. If the player is trying to walk on a diagonal, the sliding should not be done. (It's fairly easy to prove this).

2) We only need to do sliding if the player has not moved as a result of ther normal movement.

3) The wall detection doesn't care about walls directly to the side of the player, only those directly in front of, and those on the diagonals to the players base. Basically, you take the area in front of the player, and then shift it left or right (from the characters facing direction) up to 1 tiles worth, each direction relating to each sliding direction. If these tiles are clear, then the player can slide in that direction. The reason we need to look at the shifts 0 to 1 is because we dont know how much the player is clipping the wall, how large the gap they are sliding into is (we don't want to over measure and detect the wall on the other side).

4) It is worthwhile to note that because this is not looking at the tiles to the side of the player, this allows the player to move onto a wall to accomplish the sliding, which may sound odd, but is actually how the original movement behaves.

5) If you use a sliding speed greater than 1/16 (1 pixel) per timeout, then you need to check that the player is not overshooting the free area. For example, if you have a gap which is perfectly the width of the player, its likely that they will need to slide in order to line up with it. If the sliding speed is too fast, they will slide back and forth between the two sides, and never align with the gap.

If you want any clarification on the things I've said, dont hesitate to ask! ^^

projectigi

02-21-2006 06:08 PM

Quote:

Originally Posted by Polo

4) It is worthwhile to note that because this is not looking at the tiles to the side of the player, this allows the player to move onto a wall to accomplish the sliding, which may sound odd, but is actually how the original movement behaves.

i dont get this one lol

thanks for the others =D

Polo	02-21-2006 08:04 PM

1 Attachment(s)

Quote:

Originally Posted by projectigi

i dont get this one [number 4 - Storm] lol

thanks for the others =D

Ok, consider the 2 examples in the attached image. The black are shows the wall, and the blue area shows where we need to check before sliding the player.

The first example is demonstrating where we check to see if they can slide, with the player walking to the right.

In the second example, we are still checking the same area, and as it is clear, we should make the player slide, even though it will move them up over the top wall to do this. Hope that clarifies things a bit. ^^

projectigi

02-21-2006 08:55 PM

Yes, it does.
thanks

Polo	02-21-2006 09:03 PM

Quote:

Originally Posted by Polo

1) We only need to do the sliding when only one direction is being pressed. If the player is trying to walk on a diagonal, the sliding should not be done. (It's fairly easy to prove this).

I actually lied a little bit here. There is one case where sliding when holding a diagonal can occur, but I thought it was a lot less common than it is. When holding the diagonal, you need to check for sliding along both leading edges of the player, but you only have to do half the check for each. They should not slide away from the diagonal which they are holding.

For example, if the player is holding up and right, then we can either face upwards and slide to the right, or face to the right and slide upwards. The other 2 checks, facing right and sliding downwards, and facing up and sliding to the left, would feel unnatural to the user, and should be avoided.

jake13jake

02-21-2006 09:07 PM

using my control movement script (movement functions, uploaded on graal.net), I came up with this specifically. Does it just about perfectly, except my movement scripts go exactly to the wall rather than rounding.

PHP Code:


		
			
function side_movement() {

  this.w = 1;

  this.h = 1;

  for (i=0; i<4; i++) {

    if (keydown(i)) {

      temp.case_x = player.x+1 + vecx(i)*1.5*vecDir(this.speed_factor) - abs(vecy(i))*0.5;

      temp.case_y = player.y+1.5 + vecy(i)*1.5*vecDir(this.speed_factor) - abs(vecx(i))*0.5;

      temp.case_one = tilesSwitch(temp.case_x,temp.case_y,7/8,7/8);

      temp.case_x = player.x+1 + vecx(i)*1.5*vecDir(this.speed_factor) + abs(vecy(i))*(5/8);

      temp.case_y = player.y+1.5 + vecy(i)*1.5*vecDir(this.speed_factor) + abs(vecx(i))*(5/8);

      temp.case_two = tilesSwitch(temp.case_x,temp.case_y,7/8,7/8);;    

    /* In case I screw this up

      temp.case_x = player.x+1 + vecx(i)*1.5 - abs(vecy(i))*0.5;

      temp.case_y = player.y+1.5 + vecy(i)*1.5 - abs(vecx(i))*0.5;

      temp.case_one = tilesSwitch(temp.case_x,temp.case_y,7/8,7/8);

      temp.case_x = player.x+1 + vecx(i)*1.5 + abs(vecy(i))*(5/8);

      temp.case_y = player.y+1.5 + vecy(i)*1.5 + abs(vecx(i))*(5/8);

      temp.case_two = tilesSwitch(temp.case_x,temp.case_y,7/8,7/8);;

    */

      if (temp.case_one xor temp.case_two) {

        if (temp.case_one) {

          this.offx = 1.0 + vecx(i)*1.5*vecDir(this.speed_factor) + abs(vecy(i))*0.5;

          this.offy = 1.5 + vecy(i)*1.5*vecDir(this.speed_factor) + abs(vecx(i))*0.5;

          movedx(abs(vecy(i))*this.sidemove_speed,player);

          movedy(abs(vecx(i))*this.sidemove_speed,player);

        } else {

          this.offx = 1.0 + vecx(i)*1.5*vecDir(this.speed_factor) - abs(vecy(i))*0.5;

          this.offy = 1.5 + vecy(i)*1.5*vecDir(this.speed_factor) - abs(vecx(i))*0.5;

          movedx(-abs(vecy(i))*this.sidemove_speed,player);

          movedy(-abs(vecx(i))*this.sidemove_speed,player);

        }

      }

    }

  }

}

forgot to say, tilesSwitch would be the function you use for wall detection on an area.

ApothiX

02-24-2006 03:18 AM

Quote:

Originally Posted by jake13jake

What's up with the double-semicolon?
>> temp.case_two = tilesSwitch(temp.case_x,temp.case_y,7/8,7/8);;

jake13jake

02-24-2006 06:30 AM

Quote:

Originally Posted by ApothiX

What's up with the double-semicolon?
>> temp.case_two = tilesSwitch(temp.case_x,temp.case_y,7/8,7/8);;

Ooops, something I got out of there eventually. (that's a really old version of the script because I couldn't get on RC from where I was posting :P)

Add: the one I'm using now just uses the onTiles function I made because I am finally able to detect NPCs correctly for Stefan adding an npc.var for whether or not the NPC is blocking. Now I just need to wait for Stefan to add read access to players[i].paused, players[i].rating, and players[i].ratingd, and then reimplement the AP system somehow... though reimplementing the AP system is going to be hard. Gotta look for NPCs that don't use the heal() function, gotta make exceptions for spar and event levels, and I gotta add a earnedhp variable so the maxhp variable can override it (which will be a fun challenge).

hp = how many hearts
maxhp = how many hearts you can have currently.
earnedhp = how many hearts you have by default

maxhp can go under earnedhp depending on AP, but I don't want to cap it because perhaps there would be some event in which you want to give a player 20 hearts.

But yea, that's the easiest way to manipulate to include the AP system based on how everything's already built for Classic.

I don't know how I got on this tangent.

Dach	03-02-2006 01:48 AM

http://wiki.graal.us/Movement_Tutorial

wikified for accessibility and further modification

jake13jake

03-02-2006 03:27 AM

Quote:

Originally Posted by Dach

http://wiki.graal.us/Movement_Tutorial

wikified for accessibility and further modification

I wouldn't exactly call that a relevant tutorial. After all, side moving doesn't obey the same wall detection.

ApothiX

03-02-2006 02:35 PM

Quote:

Originally Posted by jake13jake

I wouldn't exactly call that a relevant tutorial. After all, side moving doesn't obey the same wall detection.

I think it's a tad more relevant than this:

Quote:

Originally Posted by jake13jake

Now I just need to wait for Stefan to add read access to players[i].paused, players[i].rating, and players[i].ratingd, and then reimplement the AP system somehow... though reimplementing the AP system is going to be hard. Gotta look for NPCs that don't use the heal() function, gotta make exceptions for spar and event levels, and I gotta add a earnedhp variable so the maxhp variable can override it (which will be a fun challenge).

hp = how many hearts
maxhp = how many hearts you can have currently.
earnedhp = how many hearts you have by default

maxhp can go under earnedhp depending on AP, but I don't want to cap it because perhaps there would be some event in which you want to give a player 20 hearts.

But yea, that's the easiest way to manipulate to include the AP system based on how everything's already built for Classic.

All times are GMT +2. The time now is 09:37 AM.