Skip to content

Removed redundancy and better wording. #8213

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

Removed redundancy and better wording. #8213

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 2 additions & 6 deletions getting_started/first_2d_game/06.heads_up_display.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -331,15 +331,13 @@ should look like this, so make sure you didn't miss anything:
Now we need to connect the ``HUD`` functionality to our ``Main`` script. This
requires a few additions to the ``Main`` scene:

In the Node tab, connect the HUD's ``start_game`` signal to the ``new_game()``
First, we don't want to start the new game automatically, so remove the call to ``new_game()``
in ``_ready()``. Then, in the Node tab, connect the HUD's ``start_game`` signal to the ``new_game()``
function of the Main node by clicking the "Pick" button in the "Connect a Signal"
window and selecting the ``new_game()`` method or type "new_game" below "Receiver Method"
in the window. Verify that the green connection icon now appears next to
``func new_game()`` in the script.

Remember to remove the call to ``new_game()`` from
``_ready()``.

In ``new_game()``, update the score display and show the "Get Ready" message:

.. tabs::
Expand Down Expand Up @@ -374,8 +372,6 @@ In ``game_over()`` we need to call the corresponding ``HUD`` function:

_hud->show_game_over();

Just a reminder: we don't want to start the new game automatically, so
remove the call to ``new_game()`` in ``_ready()`` if you haven't yet.

Finally, add this to ``_on_score_timer_timeout()`` to keep the display in sync
with the changing score:
Expand Down