Using KinematicBody2D

    Note

    This document assumes you’re familiar with Godot’s various physics bodies. Please read first.

    What is a kinematic body?

    KinematicBody2D is for implementing bodies that are controlled via code. Kinematic bodies detect collisions with other bodies when moving, but are not affected by engine physics properties, like gravity or friction. While this means that you have to write some code to create their behavior, it also means you have more precise control over how they move and react.

    Tip

    A KinematicBody2D can be affected by gravity and other forces, but you must calculate the movement in code. The physics engine will not move a KinematicBody2D.

    When moving a KinematicBody2D, you should not set its position property directly. Instead, you use the move_and_collide() or move_and_slide() methods. These methods move the body along a given vector and instantly stop if a collision is detected with another body. After a KinematicBody2D has collided, any collision response must be coded manually.

    Warning

    You should only do Kinematic body movement in the _physics_process() callback.

    The two movement methods serve different purposes, and later in this tutorial, you’ll see examples of how they work.

    This method takes one parameter: a indicating the body’s relative movement. Typically, this is your velocity vector multiplied by the frame timestep (delta). If the engine detects a collision anywhere along this vector, the body will immediately stop moving. If this happens, the method will return a KinematicCollision2D object.

    KinematicCollision2D is an object containing data about the collision and the colliding object. Using this data, you can calculate your collision response.

    move_and_slide

    The move_and_slide() method is intended to simplify the collision response in the common case where you want one body to slide along the other. It is especially useful in platformers or top-down games, for example.

    Tip

    move_and_slide() automatically calculates frame-based movement using delta. Do not multiply your velocity vector by delta before passing it to move_and_slide().

    In addition to the velocity vector, move_and_slide() takes a number of other parameters allowing you to customize the slide behavior:

    • up_direction - default value: Vector2( 0, 0 )

    • stop_on_slope - default value: false

    • max_slides - default value: 4

    • floor_max_angle - default value: 0.785398 (in radians, equivalent to 45 degrees)

    • infinite_inertia - default value: true

    When this parameter is true, the body can push RigidBody2D nodes, ignoring their mass, but won’t detect collisions with them. If it’s false the body will collide with rigid bodies and stop.

    This method adds some additional functionality to move_and_slide() by adding the snap parameter. As long as this vector is in contact with the ground, the body will remain attached to the surface. Note that this means you must disable snapping when jumping, for example. You can do this either by setting snap to Vector2.ZERO or by using move_and_slide() instead.

    Detecting collisions

    When using move_and_collide() the function returns a KinematicCollision2D directly, and you can use this in your code.

    When using move_and_slide() it’s possible to have multiple collisions occur, as the slide response is calculated. To process these collisions, use get_slide_count() and get_slide_collision():

    GDScript   C#

    1. // Using MoveAndCollide.
    2. var collision = MoveAndCollide(velocity * delta);
    3. if (collision != null)
    4. {
    5.     GD.Print("I collided with ", ((Node)collision.Collider).Name);
    6. }
    8. // Using MoveAndSlide.
    9. velocity = MoveAndSlide(velocity);
    10. for (int i = 0; i < GetSlideCount(); i++)
    11. {
    12.     var collision = GetSlideCollision(i);
    13.     GD.Print("I collided with ", ((Node)collision.Collider).Name);
    14. }

    Note

    get_slide_count() only counts times the body has collided and changed direction.

    See for details on what collision data is returned.

    A common question from new Godot users is: “How do you decide which movement function to use?” Often, the response is to use move_and_slide() because it’s “simpler,” but this is not necessarily the case. One way to think of it is that move_and_slide() is a special case, and move_and_collide() is more general. For example, the following two code snippets result in the same collision response:

    GDScript   C#

    1. # using move_and_collide
    2. var collision = move_and_collide(velocity * delta)
    3. if collision:
    4.     velocity = velocity.slide(collision.normal)
    6. # using move_and_slide
    7. velocity = move_and_slide(velocity)
    1. // using MoveAndCollide
    2. var collision = MoveAndCollide(velocity * delta);
    3. if (collision != null)
    4. {
    5.     velocity = velocity.Slide(collision.Normal);
    6. }
    7. // using MoveAndSlide
    8. velocity = MoveAndSlide(velocity);

    Anything you do with move_and_slide() can also be done with move_and_collide(), but it might take a little more code. However, as we’ll see in the examples below, there are cases where move_and_slide() doesn’t provide the response you want.

    In the example above, we assign the velocity that move_and_slide() returns back into the velocity variable. This is because when the character collides with the environment, the function recalculates the speed internally to reflect the slowdown.

    For example, if your character fell on the floor, you don’t want it to accumulate vertical speed due to the effect of gravity. Instead, you want its vertical speed to reset to zero.

    move_and_slide() may also recalculate the kinematic body’s velocity several times in a loop as, to produce a smooth motion, it moves the character and collides up to five times by default. At the end of the process, the function returns the character’s new velocity that we can store in our velocity variable, and use on the next frame.

    Examples

    To see these examples in action, download the sample project: using_kinematic2d.zip.

    Movement and walls

    If you’ve downloaded the sample project, this example is in “BasicMovement.tscn”.

    For this example, add a KinematicBody2D with two children: a Sprite and a CollisionShape2D. Use the Godot “icon.png” as the Sprite’s texture (drag it from the Filesystem dock to the Texture property of the Sprite). In the CollisionShape2D‘s Shape property, select “New RectangleShape2D” and size the rectangle to fit over the sprite image.

    Note

    See 2D movement overview for examples of implementing 2D movement schemes.

    Attach a script to the KinematicBody2D and add the following code:

    1. using Godot;
    2. using System;
    4. public class KBExample : KinematicBody2D
    5. {
    6.     public int Speed = 250;
    7.     private Vector2 _velocity = new Vector2();
    9.     public void GetInput()
    10.     {
    11.         // Detect up/down/left/right keystate and only move when pressed
    12.         _velocity = new Vector2();
    14.         if (Input.IsActionPressed("ui_right"))
    15.             _velocity.x += 1;
    17.         if (Input.IsActionPressed("ui_left"))
    18.             _velocity.x -= 1;
    21.             _velocity.y += 1;
    23.         if (Input.IsActionPressed("ui_up"))
    24.             _velocity.y -= 1;
    25.         _velocity = _velocity.Normalized() * Speed;
    26.     }
    28.     public override void _PhysicsProcess(float delta)
    29.     {
    30.         GetInput();
    31.         MoveAndCollide(_velocity * delta);
    32.     }
    33. }

    Run this scene and you’ll see that move_and_collide() works as expected, moving the body along the velocity vector. Now let’s see what happens when you add some obstacles. Add a with a rectangular collision shape. For visibility, you can use a sprite, a Polygon2D, or turn on “Visible Collision Shapes” from the “Debug” menu.

    Run the scene again and try moving into the obstacle. You’ll see that the KinematicBody2D can’t penetrate the obstacle. However, try moving into the obstacle at an angle and you’ll find that the obstacle acts like glue - it feels like the body gets stuck.

    This happens because there is no collision response. move_and_collide() stops the body’s movement when a collision occurs. We need to code whatever response we want from the collision.

    Try changing the function to move_and_slide(velocity) and running again. Note that we removed delta from the velocity calculation.

    move_and_slide() provides a default collision response of sliding the body along the collision object. This is useful for a great many game types, and may be all you need to get the behavior you want.

    What if you don’t want a sliding collision response? For this example (“BounceandCollide.tscn” in the sample project), we have a character shooting bullets and we want the bullets to bounce off the walls.

    This example uses three scenes. The main scene contains the Player and Walls. The Bullet and Wall are separate scenes so that they can be instanced.

    The Player is controlled by the w and s keys for forward and back. Aiming uses the mouse pointer. Here is the code for the Player, using move_and_slide():

    GDScript   C#

    1. extends KinematicBody2D
    3. var Bullet = preload("res://Bullet.tscn")
    4. var speed = 200
    5. var velocity = Vector2()
    7.     # Add these actions in Project Settings -> Input Map.
    8.     velocity = Vector2()
    9.     if Input.is_action_pressed('backward'):
    10.         velocity = Vector2(-speed/3, 0).rotated(rotation)
    11.     if Input.is_action_pressed('forward'):
    12.         velocity = Vector2(speed, 0).rotated(rotation)
    13.     if Input.is_action_just_pressed('mouse_click'):
    14.         shoot()
    16. func shoot():
    17.     # "Muzzle" is a Position2D placed at the barrel of the gun.
    18.     var b = Bullet.instance()
    19.     b.start($Muzzle.global_position, rotation)
    20.     get_parent().add_child(b)
    22. func _physics_process(delta):
    23.     get_input()
    24.     var dir = get_global_mouse_position() - global_position
    25.     # Don't move if too close to the mouse pointer.
    26.     if dir.length() > 5:
    27.         rotation = dir.angle()
    28.         velocity = move_and_slide(velocity)
    1. using Godot;
    2. using System;
    4. public class KBExample : KinematicBody2D
    5. {
    6.     private PackedScene _bullet = (PackedScene)GD.Load("res://Bullet.tscn");
    7.     public int Speed = 200;
    8.     private Vector2 _velocity = new Vector2();
    10.     public void GetInput()
    11.     {
    12.         // add these actions in Project Settings -> Input Map
    13.         _velocity = new Vector2();
    14.         if (Input.IsActionPressed("backward"))
    15.         {
    16.             _velocity = new Vector2(-Speed/3, 0).Rotated(Rotation);
    17.         }
    18.         if (Input.IsActionPressed("forward"))
    19.         {
    20.             _velocity = new Vector2(Speed, 0).Rotated(Rotation);
    21.         }
    22.         if (Input.IsActionPressed("mouse_click"))
    23.         {
    24.             Shoot();
    25.         }
    26.     }
    28.     public void Shoot()
    29.     {
    30.         // "Muzzle" is a Position2D placed at the barrel of the gun
    31.         var b = (Bullet)_bullet.Instance();
    32.         b.Start(GetNode<Node2D>("Muzzle").GlobalPosition, Rotation);
    33.         GetParent().AddChild(b);
    34.     }
    36.     public override void _PhysicsProcess(float delta)
    37.     {
    38.         GetInput();
    39.         var dir = GetGlobalMousePosition() - GlobalPosition;
    40.         // Don't move if too close to the mouse pointer
    41.         if (dir.Length() > 5)
    42.         {
    43.             Rotation = dir.Angle();
    44.             _velocity = MoveAndSlide(_velocity);
    45.         }
    46.     }
    47. }

    And the code for the Bullet:

    GDScript   C#

    1. using Godot;
    2. using System;
    4. public class Bullet : KinematicBody2D
    5. {
    6.     public int Speed = 750;
    7.     private Vector2 _velocity = new Vector2();
    9.     public void Start(Vector2 pos, float dir)
    10.     {
    11.         Rotation = dir;
    12.         Position = pos;
    14.     }
    16.     public override void _PhysicsProcess(float delta)
    17.         var collision = MoveAndCollide(_velocity * delta);
    18.         if (collision != null)
    19.         {
    20.             _velocity = _velocity.Bounce(collision.Normal);
    21.             if (collision.Collider.HasMethod("Hit"))
    22.             {
    23.                 collision.Collider.Call("Hit");
    24.             }
    25.         }
    26.     }
    28.     public void OnVisibilityNotifier2DScreenExited()
    29.     {
    30.         QueueFree();
    31.     }
    32. }

    The action happens in _physics_process(). After using move_and_collide(), if a collision occurs, a KinematicCollision2D object is returned (otherwise, the return is Nil).

    If there is a returned collision, we use the normal of the collision to reflect the bullet’s velocity with the Vector2.bounce() method.

    If the colliding object (collider) has a hit method, we also call it. In the example project, we’ve added a flashing color effect to the Wall to demonstrate this.

    ../../_images/k2d_bullet_bounce.gif

    Platformer movement

    Let’s try one more popular example: the 2D platformer. move_and_slide() is ideal for quickly getting a functional character controller up and running. If you’ve downloaded the sample project, you can find this in “Platformer.tscn”.

    For this example, we’ll assume you have a level made of StaticBody2D objects. They can be any shape and size. In the sample project, we’re using Polygon2D to create the platform shapes.

    Here’s the code for the player body:

    GDScript   C#

    1. extends KinematicBody2D
    3. export (int) var run_speed = 100
    4. export (int) var jump_speed = -400
    5. export (int) var gravity = 1200
    7. var velocity = Vector2()
    8. var jumping = false
    10. func get_input():
    11.     velocity.x = 0
    12.     var right = Input.is_action_pressed('ui_right')
    13.     var left = Input.is_action_pressed('ui_left')
    14.     var jump = Input.is_action_just_pressed('ui_select')
    16.     if jump and is_on_floor():
    17.         jumping = true
    18.         velocity.y = jump_speed
    19.     if right:
    20.         velocity.x += run_speed
    21.     if left:
    22.         velocity.x -= run_speed
    24. func _physics_process(delta):
    25.     get_input()
    26.     velocity.y += gravity * delta
    27.     if jumping and is_on_floor():
    28.         jumping = false
    29.     velocity = move_and_slide(velocity, Vector2(0, -1))
    1. using Godot;
    2. using System;
    4. public class KBExample : KinematicBody2D
    5. {
    6.     [Export] public int RunSpeed = 100;
    7.     [Export] public int JumpSpeed = -400;
    8.     [Export] public int Gravity = 1200;
    10.     Vector2 velocity = new Vector2();
    11.     bool jumping = false;
    13.     public void GetInput()
    14.     {
    15.         velocity.x = 0;
    16.         bool right = Input.IsActionPressed("ui_right");
    17.         bool left = Input.IsActionPressed("ui_left");
    18.         bool jump = Input.IsActionPressed("ui_select");
    20.         if (jump && IsOnFloor())
    21.         {
    22.             jumping = true;
    23.             velocity.y = JumpSpeed;
    24.         }
    26.         if (right)
    27.             velocity.x += RunSpeed;
    28.         if (left)
    29.             velocity.x -= RunSpeed;
    30.     }
    32.     public override void _PhysicsProcess(float delta)
    33.     {
    34.         GetInput();
    35.         velocity.y += Gravity * delta;
    36.         if (jumping && IsOnFloor())
    37.             jumping = false;
    38.         velocity = MoveAndSlide(velocity, new Vector2(0, -1));
    39.     }
    40. }

    When using move_and_slide(), the function returns a vector representing the movement that remained after the slide collision occurred. Setting that value back to the character’s velocity allows us to move up and down slopes smoothly. Try removing velocity = and see what happens if you don’t do this.

    Also note that we’ve added Vector2(0, -1) as the floor normal. This vector points straight upward. As a result, if the character collides with an object that has this normal, it will be considered a floor.

    This angle also allows you to implement other features like wall jumps using , for example.