Moving the player with code

It’s time to code! We’re going to use the input actions we created in the last part to move the character.

Note

For this project, we will be following the Godot naming conventions.

  • GDScript: Classes (nodes) use PascalCase, variables and functions use snake_case, and constants use ALL_CAPS (See GDScript style guide).

  • C#: Classes, export variables and methods use PascalCase, private fields use _camelCase, local variables and parameters use camelCase (See C# style guide). Be careful to type the method names precisely when connecting signals.

Right-click the Player node and select Attach Script to add a new script to it. In the popup, set the Template to Empty before pressing the Create button. We set it to Empty because we want to write our own code for player movement.

image0

Let’s start with the class’s properties. We’re going to define a movement speed, a fall acceleration representing gravity, and a velocity we’ll use to move the character.

GDScriptC#

  1. extends CharacterBody3D
  3. # How fast the player moves in meters per second.
  4. @export var speed = 14
  5. # The downward acceleration when in the air, in meters per second squared.
  6. @export var fall_acceleration = 75
  8. var target_velocity = Vector3.ZERO
  1. using Godot;
  3. public partial class Player : CharacterBody3D
  4. {
  5.     // Don't forget to rebuild the project so the editor knows about the new export variable.
  7.     // How fast the player moves in meters per second.
  8.     [Export]
  9.     public int Speed { get; set; } = 14;
  10.     // The downward acceleration when in the air, in meters per second squared.
  11.     [Export]
  12.     public int FallAcceleration { get; set; } = 75;
  14.     private Vector3 _targetVelocity = Vector3.Zero;
  15. }

These are common properties for a moving body. The target_velocity is a 3D vector combining a speed with a direction. Here, we define it as a property because we want to update and reuse its value across frames.

Note

The values are quite different from 2D code because distances are in meters. While in 2D, a thousand units (pixels) may only correspond to half of your screen’s width, in 3D, it’s a kilometer.

Let’s code the movement. We start by calculating the input direction vector using the global Input object, in _physics_process().

GDScriptC#

  1. func _physics_process(delta):
  2.     # We create a local variable to store the input direction.
  3.     var direction = Vector3.ZERO
  5.     # We check for each move input and update the direction accordingly.
  6.     if Input.is_action_pressed("move_right"):
  7.         direction.x += 1
  8.     if Input.is_action_pressed("move_left"):
  9.         direction.x -= 1
  10.     if Input.is_action_pressed("move_back"):
  11.         # Notice how we are working with the vector's x and z axes.
  12.         # In 3D, the XZ plane is the ground plane.
  13.         direction.z += 1
  14.     if Input.is_action_pressed("move_forward"):
  15.         direction.z -= 1
  1. public override void _PhysicsProcess(double delta)
  2. {
  3.     // We create a local variable to store the input direction.
  4.     var direction = Vector3.Zero;
  6.     // We check for each move input and update the direction accordingly.
  7.     if (Input.IsActionPressed("move_right"))
  8.     {
  9.         direction.X += 1.0f;
  10.     }
  11.     if (Input.IsActionPressed("move_left"))
  12.     {
  13.         direction.X -= 1.0f;
  14.     }
  15.     if (Input.IsActionPressed("move_back"))
  16.     {
  17.         // Notice how we are working with the vector's X and Z axes.
  18.         // In 3D, the XZ plane is the ground plane.
  19.         direction.Z += 1.0f;
  20.     }
  21.     if (Input.IsActionPressed("move_forward"))
  22.     {
  23.         direction.Z -= 1.0f;
  24.     }
  25. }

Here, we’re going to make all calculations using the _physics_process() virtual function. Like _process(), it allows you to update the node every frame, but it’s designed specifically for physics-related code like moving a kinematic or rigid body.

See also

To learn more about the difference between _process() and _physics_process(), see Idle and Physics Processing.

We start by initializing a direction variable to Vector3.ZERO. Then, we check if the player is pressing one or more of the move_* inputs and update the vector’s x and z components accordingly. These correspond to the ground plane’s axes.

These four conditions give us eight possibilities and eight possible directions.

In case the player presses, say, both W and D simultaneously, the vector will have a length of about 1.4. But if they press a single key, it will have a length of 1. We want the vector’s length to be consistent, and not move faster diagonally. To do so, we can call its normalized() method.

GDScriptC#

  1. #func _physics_process(delta):
  2.     #...
  4.     if direction != Vector3.ZERO:
  5.         direction = direction.normalized()
  6.         # Setting the basis property will affect the rotation of the node.
  7.         $Pivot.basis = Basis.looking_at(direction)
  1. public override void _PhysicsProcess(double delta)
  2. {
  3.     // ...
  5.     if (direction != Vector3.Zero)
  6.     {
  7.         direction = direction.Normalized();
  8.         // Setting the basis property will affect the rotation of the node.
  9.         GetNode<Node3D>("Pivot").Basis = Basis.LookingAt(direction);
  10.     }
  11. }

Here, we only normalize the vector if the direction has a length greater than zero, which means the player is pressing a direction key.

We compute the direction the $Pivot is looking by creating a Basis that looks in the direction direction.

Then, we update the velocity. We have to calculate the ground velocity and the fall speed separately. Be sure to go back one tab so the lines are inside the _physics_process() function but outside the condition we just wrote above.

GDScriptC#

  1. func _physics_process(delta):
  2.     #...
  3.     if direction != Vector3.ZERO:
  4.         #...
  6.     # Ground Velocity
  7.     target_velocity.x = direction.x * speed
  8.     target_velocity.z = direction.z * speed
  10.     # Vertical Velocity
  11.     if not is_on_floor(): # If in the air, fall towards the floor. Literally gravity
  12.         target_velocity.y = target_velocity.y - (fall_acceleration * delta)
  14.     # Moving the Character
  15.     velocity = target_velocity
  16.     move_and_slide()
  1. public override void _PhysicsProcess(double delta)
  2. {
  3.     // ...
  4.     if (direction != Vector3.Zero)
  5.     {
  6.         // ...
  7.     }
  9.     // Ground velocity
  10.     _targetVelocity.X = direction.X * Speed;
  11.     _targetVelocity.Z = direction.Z * Speed;
  13.     // Vertical velocity
  14.     if (!IsOnFloor()) // If in the air, fall towards the floor. Literally gravity
  15.     {
  16.         _targetVelocity.Y -= FallAcceleration * (float)delta;
  17.     }
  19.     // Moving the character
  20.     Velocity = _targetVelocity;
  21.     MoveAndSlide();
  22. }

The CharacterBody3D.is_on_floor() function returns true if the body collided with the floor in this frame. That’s why we apply gravity to the Player only while it is in the air.

For the vertical velocity, we subtract the fall acceleration multiplied by the delta time every frame. This line of code will cause our character to fall in every frame, as long as it is not on or colliding with the floor.

The physics engine can only detect interactions with walls, the floor, or other bodies during a given frame if movement and collisions happen. We will use this property later to code the jump.

On the last line, we call CharacterBody3D.move_and_slide() which is a powerful method of the CharacterBody3D class that allows you to move a character smoothly. If it hits a wall midway through a motion, the engine will try to smooth it out for you. It uses the velocity value native to the CharacterBody3D

And that’s all the code you need to move the character on the floor.

Here is the complete player.gd code for reference.

GDScriptC#

  1. extends CharacterBody3D
  3. # How fast the player moves in meters per second.
  4. @export var speed = 14
  5. # The downward acceleration when in the air, in meters per second squared.
  6. @export var fall_acceleration = 75
  8. var target_velocity = Vector3.ZERO
  11. func _physics_process(delta):
  12.     var direction = Vector3.ZERO
  14.     if Input.is_action_pressed("move_right"):
  15.         direction.x += 1
  16.     if Input.is_action_pressed("move_left"):
  17.         direction.x -= 1
  18.     if Input.is_action_pressed("move_back"):
  19.         direction.z += 1
  20.     if Input.is_action_pressed("move_forward"):
  21.         direction.z -= 1
  23.     if direction != Vector3.ZERO:
  24.         direction = direction.normalized()
  25.         $Pivot.basis = Basis.looking_at(direction)
  27.     # Ground Velocity
  28.     target_velocity.x = direction.x * speed
  29.     target_velocity.z = direction.z * speed
  31.     # Vertical Velocity
  32.     if not is_on_floor(): # If in the air, fall towards the floor. Literally gravity
  33.         target_velocity.y = target_velocity.y - (fall_acceleration * delta)
  35.     # Moving the Character
  36.     velocity = target_velocity
  37.     move_and_slide()
  1. using Godot;
  3. public partial class Player : CharacterBody3D
  4. {
  5.     // How fast the player moves in meters per second.
  6.     [Export]
  7.     public int Speed { get; set; } = 14;
  8.     // The downward acceleration when in the air, in meters per second squared.
  9.     [Export]
  10.     public int FallAcceleration { get; set; } = 75;
  12.     private Vector3 _targetVelocity = Vector3.Zero;
  14.     public override void _PhysicsProcess(double delta)
  15.     {
  16.         var direction = Vector3.Zero;
  18.         if (Input.IsActionPressed("move_right"))
  19.         {
  20.             direction.X += 1.0f;
  21.         }
  22.         if (Input.IsActionPressed("move_left"))
  23.         {
  24.             direction.X -= 1.0f;
  25.         }
  26.         if (Input.IsActionPressed("move_back"))
  27.         {
  28.             direction.Z += 1.0f;
  29.         }
  30.         if (Input.IsActionPressed("move_forward"))
  31.         {
  32.             direction.Z -= 1.0f;
  33.         }
  35.         if (direction != Vector3.Zero)
  36.         {
  37.             direction = direction.Normalized();
  38.             GetNode<Node3D>("Pivot").Basis = Basis.LookingAt(direction);
  39.         }
  41.         // Ground velocity
  42.         _targetVelocity.X = direction.X * Speed;
  43.         _targetVelocity.Z = direction.Z * Speed;
  45.         // Vertical velocity
  46.         if (!IsOnFloor()) // If in the air, fall towards the floor. Literally gravity
  47.         {
  48.             _targetVelocity.Y -= FallAcceleration * (float)delta;
  49.         }
  51.         // Moving the character
  52.         Velocity = _targetVelocity;
  53.         MoveAndSlide();
  54.     }
  55. }

Testing our player’s movement

We’re going to put our player in the Main scene to test it. To do so, we need to instantiate the player and then add a camera. Unlike in 2D, in 3D, you won’t see anything if your viewport doesn’t have a camera pointing at something.

Save your Player scene and open the Main scene. You can click on the Main tab at the top of the editor to do so.

image1

If you closed the scene before, head to the FileSystem dock and double-click main.tscn to re-open it.

To instantiate the Player, right-click on the Main node and select Instantiate Child Scene.

image2

In the popup, double-click player.tscn. The character should appear in the center of the viewport.

Adding a camera

Let’s add the camera next. Like we did with our Player‘s Pivot, we’re going to create a basic rig. Right-click on the Main node again and select Add Child Node. Create a new Marker3D, and name it CameraPivot. Select CameraPivot and add a child node Camera3D to it. Your scene tree should look similar to this.

image3

Notice the Preview checkbox that appears in the top-left of the 3D view when you have the Camera selected. You can click it to preview the in-game camera projection.

image4

We’re going to use the Pivot to rotate the camera as if it was on a crane. Let’s first split the 3D view to be able to freely navigate the scene and see what the camera sees.

In the toolbar right above the viewport, click on View, then 2 Viewports. You can also press Ctrl + 2 (Cmd + 2 on macOS).

image11

image5

On the bottom view, select your Camera3D and turn on camera Preview by clicking the checkbox.

image6

In the top view, make sure your Camera3D is selected and move the camera about 19 units on the Z axis (drag the blue arrow).

image7

Here’s where the magic happens. Select the CameraPivot and rotate it -45 degrees around the X axis (using the red circle). You’ll see the camera move as if it was attached to a crane.

image8

You can run the scene by pressing F6 and press the arrow keys to move the character.

image9

We can see some empty space around the character due to the perspective projection. In this game, we’re going to use an orthographic projection instead to better frame the gameplay area and make it easier for the player to read distances.

Select the Camera again and in the Inspector, set the Projection to Orthogonal and the Size to 19. The character should now look flatter and the ground should fill the background.

Note

When using an orthogonal camera in Godot 4, directional shadow quality is dependent on the camera’s Far value. The higher the Far value, the further away the camera will be able to see. However, higher Far values also decrease shadow quality as the shadow rendering has to cover a greater distance.

If directional shadows look too blurry after switching to an orthogonal camera, decrease the camera’s Far property to a lower value such as 100. Don’t decrease this Far property too much, or objects in the distance will start disappearing.

image10

Test your scene and you should be able to move in all 8 directions and not glitch through the floor!

Ultimately, we have both player movement and the view in place. Next, we will work on the monsters.

User-contributed notes

Please read the User-contributed notes policy before submitting a comment.

Previous Next