03.coding_the_player.rst 18 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556
  1. .. _doc_your_first_2d_game_coding_the_player:
  2. Coding the player
  3. =================
  4. In this lesson, we'll add player movement, animation, and set it up to detect
  5. collisions.
  6. To do so, we need to add some functionality that we can't get from a built-in
  7. node, so we'll add a script. Click the ``Player`` node and click the "Attach
  8. Script" button:
  9. .. image:: img/add_script_button.webp
  10. In the script settings window, you can leave the default settings alone. Just
  11. click "Create":
  12. .. note:: If you're creating a C# script or other languages, select the language
  13. from the `language` drop down menu before hitting create.
  14. .. image:: img/attach_node_window.webp
  15. .. note:: If this is your first time encountering GDScript, please read
  16. :ref:`doc_scripting` before continuing.
  17. Start by declaring the member variables this object will need:
  18. .. tabs::
  19. .. code-tab:: gdscript GDScript
  20. extends Area2D
  21. @export var speed = 400 # How fast the player will move (pixels/sec).
  22. var screen_size # Size of the game window.
  23. .. code-tab:: csharp
  24. using Godot;
  25. public partial class Player : Area2D
  26. {
  27. [Export]
  28. public int Speed { get; set; } = 400; // How fast the player will move (pixels/sec).
  29. public Vector2 ScreenSize; // Size of the game window.
  30. }
  31. .. code-tab:: cpp
  32. // A `player.gdns` file has already been created for you. Attach it to the Player node.
  33. // Create two files `player.cpp` and `player.hpp` next to `entry.cpp` in `src`.
  34. // This code goes in `player.hpp`. We also define the methods we'll be using here.
  35. #ifndef PLAYER_H
  36. #define PLAYER_H
  37. #include <AnimatedSprite2D.hpp>
  38. #include <Area2D.hpp>
  39. #include <CollisionShape2D.hpp>
  40. #include <Godot.hpp>
  41. #include <Input.hpp>
  42. class Player : public godot::Area2D {
  43. GODOT_CLASS(Player, godot::Area2D)
  44. godot::AnimatedSprite2D *_animated_sprite;
  45. godot::CollisionShape2D *_collision_shape;
  46. godot::Input *_input;
  47. godot::Vector2 _screen_size; // Size of the game window.
  48. public:
  49. real_t speed = 400; // How fast the player will move (pixels/sec).
  50. void _init() {}
  51. void _ready();
  52. void _process(const double p_delta);
  53. void start(const godot::Vector2 p_position);
  54. void _on_body_entered(godot::Node2D *_body);
  55. static void _register_methods();
  56. };
  57. #endif // PLAYER_H
  58. Using the ``export`` keyword on the first variable ``speed`` allows us to set
  59. its value in the Inspector. This can be handy for values that you want to be
  60. able to adjust just like a node's built-in properties. Click on the ``Player``
  61. node and you'll see the property now appears in the "Script Variables" section
  62. of the Inspector. Remember, if you change the value here, it will override the
  63. value written in the script.
  64. .. warning::
  65. If you're using C#, you need to (re)build the project assemblies
  66. whenever you want to see new export variables or signals. This
  67. build can be manually triggered by clicking the "Build" button at
  68. the top right of the editor.
  69. .. image:: img/build_dotnet.webp
  70. A manual build can also be triggered from the MSBuild Panel. Click
  71. the word "MSBuild" at the bottom of the editor window to reveal the
  72. MSBuild Panel, then click the "Build" button.
  73. .. image:: img/export_variable.webp
  74. The ``_ready()`` function is called when a node enters the scene tree, which is
  75. a good time to find the size of the game window:
  76. .. tabs::
  77. .. code-tab:: gdscript GDScript
  78. func _ready():
  79. screen_size = get_viewport_rect().size
  80. .. code-tab:: csharp
  81. public override void _Ready()
  82. {
  83. ScreenSize = GetViewportRect().Size;
  84. }
  85. .. code-tab:: cpp
  86. // This code goes in `player.cpp`.
  87. #include "player.hpp"
  88. void Player::_ready() {
  89. _animated_sprite = get_node<godot::AnimatedSprite2D>("AnimatedSprite2D");
  90. _collision_shape = get_node<godot::CollisionShape2D>("CollisionShape2D");
  91. _input = godot::Input::get_singleton();
  92. _screen_size = get_viewport_rect().size;
  93. }
  94. Now we can use the ``_process()`` function to define what the player will do.
  95. ``_process()`` is called every frame, so we'll use it to update elements of our
  96. game, which we expect will change often. For the player, we need to do the
  97. following:
  98. - Check for input.
  99. - Move in the given direction.
  100. - Play the appropriate animation.
  101. First, we need to check for input - is the player pressing a key? For this game,
  102. we have 4 direction inputs to check. Input actions are defined in the Project
  103. Settings under "Input Map". Here, you can define custom events and assign
  104. different keys, mouse events, or other inputs to them. For this game, we will
  105. map the arrow keys to the four directions.
  106. Click on *Project -> Project Settings* to open the project settings window and
  107. click on the *Input Map* tab at the top. Type "move_right" in the top bar and
  108. click the "Add" button to add the ``move_right`` action.
  109. .. image:: img/input-mapping-add-action.webp
  110. We need to assign a key to this action. Click the "+" icon on the right, to
  111. open the event manager window.
  112. .. image:: img/input-mapping-add-key.webp
  113. The "Listening for Input..." field should automatically be selected.
  114. Press the "right" key on your keyboard, and the menu should look like this now.
  115. .. image:: img/input-mapping-event-configuration.webp
  116. Select the "ok" button. The "right" key is now associated with the ``move_right`` action.
  117. Repeat these steps to add three more mappings:
  118. 1. ``move_left`` mapped to the left arrow key.
  119. 2. ``move_up`` mapped to the up arrow key.
  120. 3. And ``move_down`` mapped to the down arrow key.
  121. Your input map tab should look like this:
  122. .. image:: img/input-mapping-completed.webp
  123. Click the "Close" button to close the project settings.
  124. .. note::
  125. We only mapped one key to each input action, but you can map multiple keys,
  126. joystick buttons, or mouse buttons to the same input action.
  127. You can detect whether a key is pressed using ``Input.is_action_pressed()``,
  128. which returns ``true`` if it's pressed or ``false`` if it isn't.
  129. .. tabs::
  130. .. code-tab:: gdscript GDScript
  131. func _process(delta):
  132. var velocity = Vector2.ZERO # The player's movement vector.
  133. if Input.is_action_pressed("move_right"):
  134. velocity.x += 1
  135. if Input.is_action_pressed("move_left"):
  136. velocity.x -= 1
  137. if Input.is_action_pressed("move_down"):
  138. velocity.y += 1
  139. if Input.is_action_pressed("move_up"):
  140. velocity.y -= 1
  141. if velocity.length() > 0:
  142. velocity = velocity.normalized() * speed
  143. $AnimatedSprite2D.play()
  144. else:
  145. $AnimatedSprite2D.stop()
  146. .. code-tab:: csharp
  147. public override void _Process(double delta)
  148. {
  149. var velocity = Vector2.Zero; // The player's movement vector.
  150. if (Input.IsActionPressed("move_right"))
  151. {
  152. velocity.X += 1;
  153. }
  154. if (Input.IsActionPressed("move_left"))
  155. {
  156. velocity.X -= 1;
  157. }
  158. if (Input.IsActionPressed("move_down"))
  159. {
  160. velocity.Y += 1;
  161. }
  162. if (Input.IsActionPressed("move_up"))
  163. {
  164. velocity.Y -= 1;
  165. }
  166. var animatedSprite2D = GetNode<AnimatedSprite2D>("AnimatedSprite2D");
  167. if (velocity.Length() > 0)
  168. {
  169. velocity = velocity.Normalized() * Speed;
  170. animatedSprite2D.Play();
  171. }
  172. else
  173. {
  174. animatedSprite2D.Stop();
  175. }
  176. }
  177. .. code-tab:: cpp
  178. // This code goes in `player.cpp`.
  179. void Player::_process(const double p_delta) {
  180. godot::Vector2 velocity(0, 0);
  181. velocity.x = _input->get_action_strength("move_right") - _input->get_action_strength("move_left");
  182. velocity.y = _input->get_action_strength("move_down") - _input->get_action_strength("move_up");
  183. if (velocity.length() > 0) {
  184. velocity = velocity.normalized() * speed;
  185. _animated_sprite->play();
  186. } else {
  187. _animated_sprite->stop();
  188. }
  189. }
  190. We start by setting the ``velocity`` to ``(0, 0)`` - by default, the player
  191. should not be moving. Then we check each input and add/subtract from the
  192. ``velocity`` to obtain a total direction. For example, if you hold ``right`` and
  193. ``down`` at the same time, the resulting ``velocity`` vector will be ``(1, 1)``.
  194. In this case, since we're adding a horizontal and a vertical movement, the
  195. player would move *faster* diagonally than if it just moved horizontally.
  196. We can prevent that if we *normalize* the velocity, which means we set its
  197. *length* to ``1``, then multiply by the desired speed. This means no more fast
  198. diagonal movement.
  199. .. tip:: If you've never used vector math before, or need a refresher, you can
  200. see an explanation of vector usage in Godot at :ref:`doc_vector_math`.
  201. It's good to know but won't be necessary for the rest of this tutorial.
  202. We also check whether the player is moving so we can call ``play()`` or
  203. ``stop()`` on the AnimatedSprite2D.
  204. .. tip:: ``$`` is shorthand for ``get_node()``. So in the code above,
  205. ``$AnimatedSprite2D.play()`` is the same as
  206. ``get_node("AnimatedSprite2D").play()``.
  207. In GDScript, ``$`` returns the node at the relative path from the
  208. current node, or returns ``null`` if the node is not found. Since
  209. AnimatedSprite2D is a child of the current node, we can use
  210. ``$AnimatedSprite2D``.
  211. Now that we have a movement direction, we can update the player's position. We
  212. can also use ``clamp()`` to prevent it from leaving the screen. *Clamping* a
  213. value means restricting it to a given range. Add the following to the bottom of
  214. the ``_process`` function (make sure it's not indented under the `else`):
  215. .. tabs::
  216. .. code-tab:: gdscript GDScript
  217. position += velocity * delta
  218. position = position.clamp(Vector2.ZERO, screen_size)
  219. .. code-tab:: csharp
  220. Position += velocity * (float)delta;
  221. Position = new Vector2(
  222. x: Mathf.Clamp(Position.X, 0, ScreenSize.X),
  223. y: Mathf.Clamp(Position.Y, 0, ScreenSize.Y)
  224. );
  225. .. code-tab:: cpp
  226. godot::Vector2 position = get_position();
  227. position += velocity * (real_t)p_delta;
  228. position.x = godot::Math::clamp(position.x, (real_t)0.0, _screen_size.x);
  229. position.y = godot::Math::clamp(position.y, (real_t)0.0, _screen_size.y);
  230. set_position(position);
  231. .. tip:: The `delta` parameter in the `_process()` function refers to the *frame
  232. length* - the amount of time that the previous frame took to complete.
  233. Using this value ensures that your movement will remain consistent even
  234. if the frame rate changes.
  235. Click "Play Scene" (:kbd:`F6`, :kbd:`Cmd + R` on macOS) and confirm you can move
  236. the player around the screen in all directions.
  237. .. warning:: If you get an error in the "Debugger" panel that says
  238. ``Attempt to call function 'play' in base 'null instance' on a null
  239. instance``
  240. this likely means you spelled the name of the AnimatedSprite2D node
  241. wrong. Node names are case-sensitive and ``$NodeName`` must match
  242. the name you see in the scene tree.
  243. Choosing animations
  244. ~~~~~~~~~~~~~~~~~~~
  245. Now that the player can move, we need to change which animation the
  246. AnimatedSprite2D is playing based on its direction. We have the "walk" animation,
  247. which shows the player walking to the right. This animation should be flipped
  248. horizontally using the ``flip_h`` property for left movement. We also have the
  249. "up" animation, which should be flipped vertically with ``flip_v`` for downward
  250. movement. Let's place this code at the end of the ``_process()`` function:
  251. .. tabs::
  252. .. code-tab:: gdscript GDScript
  253. if velocity.x != 0:
  254. $AnimatedSprite2D.animation = "walk"
  255. $AnimatedSprite2D.flip_v = false
  256. # See the note below about boolean assignment.
  257. $AnimatedSprite2D.flip_h = velocity.x < 0
  258. elif velocity.y != 0:
  259. $AnimatedSprite2D.animation = "up"
  260. $AnimatedSprite2D.flip_v = velocity.y > 0
  261. .. code-tab:: csharp
  262. if (velocity.X != 0)
  263. {
  264. animatedSprite2D.Animation = "walk";
  265. animatedSprite2D.FlipV = false;
  266. // See the note below about boolean assignment.
  267. animatedSprite2D.FlipH = velocity.X < 0;
  268. }
  269. else if (velocity.Y != 0)
  270. {
  271. animatedSprite2D.Animation = "up";
  272. animatedSprite2D.FlipV = velocity.Y > 0;
  273. }
  274. .. code-tab:: cpp
  275. if (velocity.x != 0) {
  276. _animated_sprite->set_animation("walk");
  277. _animated_sprite->set_flip_v(false);
  278. // See the note below about boolean assignment.
  279. _animated_sprite->set_flip_h(velocity.x < 0);
  280. } else if (velocity.y != 0) {
  281. _animated_sprite->set_animation("up");
  282. _animated_sprite->set_flip_v(velocity.y > 0);
  283. }
  284. .. Note:: The boolean assignments in the code above are a common shorthand for
  285. programmers. Since we're doing a comparison test (boolean) and also
  286. *assigning* a boolean value, we can do both at the same time. Consider
  287. this code versus the one-line boolean assignment above:
  288. .. tabs::
  289. .. code-tab :: gdscript GDScript
  290. if velocity.x < 0:
  291. $AnimatedSprite2D.flip_h = true
  292. else:
  293. $AnimatedSprite2D.flip_h = false
  294. .. code-tab:: csharp
  295. if (velocity.X < 0)
  296. {
  297. animatedSprite2D.FlipH = true;
  298. }
  299. else
  300. {
  301. animatedSprite2D.FlipH = false;
  302. }
  303. Play the scene again and check that the animations are correct in each of the
  304. directions.
  305. .. tip:: A common mistake here is to type the names of the animations wrong. The
  306. animation names in the SpriteFrames panel must match what you type in
  307. the code. If you named the animation ``"Walk"``, you must also use a
  308. capital "W" in the code.
  309. When you're sure the movement is working correctly, add this line to
  310. ``_ready()``, so the player will be hidden when the game starts:
  311. .. tabs::
  312. .. code-tab:: gdscript GDScript
  313. hide()
  314. .. code-tab:: csharp
  315. Hide();
  316. .. code-tab:: cpp
  317. hide();
  318. Preparing for collisions
  319. ~~~~~~~~~~~~~~~~~~~~~~~~
  320. We want ``Player`` to detect when it's hit by an enemy, but we haven't made any
  321. enemies yet! That's OK, because we're going to use Godot's *signal*
  322. functionality to make it work.
  323. Add the following at the top of the script. If you're using GDScript, add it after
  324. ``extends Area2D``. If you're using C#, add it after ``public partial class Player : Area2D``:
  325. .. tabs::
  326. .. code-tab:: gdscript GDScript
  327. signal hit
  328. .. code-tab:: csharp
  329. // Don't forget to rebuild the project so the editor knows about the new signal.
  330. [Signal]
  331. public delegate void HitEventHandler();
  332. .. code-tab:: cpp
  333. // This code goes in `player.cpp`.
  334. // We need to register the signal here, and while we're here, we can also
  335. // register the other methods and register the speed property.
  336. void Player::_register_methods() {
  337. godot::register_method("_ready", &Player::_ready);
  338. godot::register_method("_process", &Player::_process);
  339. godot::register_method("start", &Player::start);
  340. godot::register_method("_on_body_entered", &Player::_on_body_entered);
  341. godot::register_property("speed", &Player::speed, (real_t)400.0);
  342. // This below line is the signal.
  343. godot::register_signal<Player>("hit", godot::Dictionary());
  344. }
  345. This defines a custom signal called "hit" that we will have our player emit
  346. (send out) when it collides with an enemy. We will use ``Area2D`` to detect the
  347. collision. Select the ``Player`` node and click the "Node" tab next to the
  348. Inspector tab to see the list of signals the player can emit:
  349. .. image:: img/player_signals.webp
  350. Notice our custom "hit" signal is there as well! Since our enemies are going to
  351. be ``RigidBody2D`` nodes, we want the ``body_entered(body: Node2D)`` signal. This
  352. signal will be emitted when a body contacts the player. Click "Connect.." and
  353. the "Connect a Signal" window appears. We don't need to change any of these
  354. settings so click "Connect" again. Godot will automatically create a function in
  355. your player's script.
  356. .. image:: img/player_signal_connection.webp
  357. Note the green icon indicating that a signal is connected to this function. Add
  358. this code to the function:
  359. .. tabs::
  360. .. code-tab:: gdscript GDScript
  361. func _on_body_entered(body):
  362. hide() # Player disappears after being hit.
  363. hit.emit()
  364. # Must be deferred as we can't change physics properties on a physics callback.
  365. $CollisionShape2D.set_deferred("disabled", true)
  366. .. code-tab:: csharp
  367. private void OnBodyEntered(PhysicsBody2D body)
  368. {
  369. Hide(); // Player disappears after being hit.
  370. EmitSignal(SignalName.Hit);
  371. // Must be deferred as we can't change physics properties on a physics callback.
  372. GetNode<CollisionShape2D>("CollisionShape2D").SetDeferred(CollisionShape2D.PropertyName.Disabled, true);
  373. }
  374. .. code-tab:: cpp
  375. // This code goes in `player.cpp`.
  376. void Player::_on_body_entered(godot::Node2D *_body) {
  377. hide(); // Player disappears after being hit.
  378. emit_signal("hit");
  379. // Must be deferred as we can't change physics properties on a physics callback.
  380. _collision_shape->set_deferred("disabled", true);
  381. }
  382. Each time an enemy hits the player, the signal is going to be emitted. We need
  383. to disable the player's collision so that we don't trigger the ``hit`` signal
  384. more than once.
  385. .. Note:: Disabling the area's collision shape can cause an error if it happens
  386. in the middle of the engine's collision processing. Using
  387. ``set_deferred()`` tells Godot to wait to disable the shape until it's
  388. safe to do so.
  389. The last piece is to add a function we can call to reset the player when
  390. starting a new game.
  391. .. tabs::
  392. .. code-tab:: gdscript GDScript
  393. func start(pos):
  394. position = pos
  395. show()
  396. $CollisionShape2D.disabled = false
  397. .. code-tab:: csharp
  398. public void Start(Vector2 position)
  399. {
  400. Position = position;
  401. Show();
  402. GetNode<CollisionShape2D>("CollisionShape2D").Disabled = false;
  403. }
  404. .. code-tab:: cpp
  405. // This code goes in `player.cpp`.
  406. void Player::start(const godot::Vector2 p_position) {
  407. set_position(p_position);
  408. show();
  409. _collision_shape->set_disabled(false);
  410. }
  411. With the player working, we'll work on the enemy in the next lesson.