godotengine/godot-docs
1
0
Fork 0
mirror of https://github.com/godotengine/godot-docs.git synced 2025-12-31 17:49:03 +03:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #8466 from theDrake/patch-1

Browse Source 
Minor edits for scripting_player_input.rst
This commit is contained in:
Matthew
2023-11-28 21:15:43 -05:00
committed by GitHub
parent a84cd8e85e c274df34d9
commit d9725deef6
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
getting_started/step_by_step/scripting_player_input.rst
View File

@@ -7,7 +7,7 @@
Listening to player input
=========================
Building upon the previous lesson :ref:`doc_scripting_first_script`, let's look
Building upon the previous lesson, :ref:`doc_scripting_first_script`, let's look
at another important feature of any game: giving control to the player.
To add this, we need to modify our ``sprite_2d.gd`` code.
@@ -181,7 +181,7 @@ Summary
In summary, every script in Godot represents a class and extends one of the
engine's built-in classes. The node types your classes inherit from give you
access to properties like ``rotation`` and ``position`` in our sprite's case.
access to properties, such as ``rotation`` and ``position`` in our sprite's case.
You also inherit many functions, which we didn't get to use in this example.
In GDScript, the variables you put at the top of the file are your class's
@@ -196,5 +196,5 @@ button presses from the users. There are quite a few more.
The ``Input`` singleton allows you to react to the players' input anywhere in
your code. In particular, you'll get to use it in the ``_process()`` loop.
In the next lesson :ref:`doc_signals`, we'll build upon the relationship between
In the next lesson, :ref:`doc_signals`, we'll build upon the relationship between
scripts and nodes by having our nodes trigger code in scripts.