getting_started/first_2d_game/06.heads_up_display

[giscus[bot]]

getting_started/first_2d_game/06.heads_up_display

The final piece our game needs is a User Interface (UI) to display things like score, a "game over" message, and a restart button. Create a new scene, click the "Other Node" button and add a Canvas...

https://docs.godotengine.org/en/stable/getting_started/first_2d_game/06.heads_up_display.html

[MountainWizard]

In the last part about "removing old creeps" the newest version of Godot now supports global and scene groups.
Click the + to add a new group and give it the name mobs. You don't need to make it a global group since the group does only apply to the mobs node.

[ThomasCrane]

C# users must change the connections under the Node tab to C# nomenclature, not the default it provides you.

Change these:

_on_start_button_pressed
_on_message_timer_timeout

to:

OnStartButtonPressed
OnMessageTimerTimeout

or, if you've already created the script as guided, you can select the Pick button to the right of the text field when editing the connection, and then select the appropriate method.

[K-Princ]

why am i not able to connect start_game signal of HUD node to new_game() function of Main node?

[MountainWizard]

Make sure you have a signal start_game in your HUD script. The connect the start button pressed node to you script to create the func _on_start_button_pressed(): function. And in the function you need the start_game.emit() to send the signal.
Then in Main connect the start_game node to the script. Something that confused met at first was, that you need to run the game from the Main Scene. If you have the HUD scene selected and press F6 to run the Game it doesn't work.

[gerritnowald]

The main scene from which the game starts can be set under:
Project Settings --> Application --> Run --> Main Scene

[K-Princ]

when i am trying to connect start_game signal of HUD node to new_game() function of Main node , I can't find the function new_game() in the options in the pop?

[GoutteDooo]

Did you write signal start_game in top of hud.gd script ?

[BastardSeagull]

Make sure you're in the HUD node under Main, not accidentally looking at your HUD scene.
I made that mistake, and it took me a sec to realize it.

[Fatyfeet]

I was having this problem too, I had neglected to save my hud.tscn again after creating the signal, so the instance of hud.tscn under the main scene did not have it. I saved it and it worked fine, and I spent far too long figuring that out.

[Roedhip]

When I create a new group named "mobs" and use the code to clear all mobs, the Player and the HUD are also cleared. I assume the problem is that they are being included the in mobs group, but I have no idea how this group is supposed to know what is inside it anyway. How do I make sure the "mobs" group only contains instances of Mob?

[Roedhip]

I have now looked up groups in the Godot documentation and found commands for adding Nodes to a group. By adding the line:

mob.add_to_group("mobs")

to the end _on_mob_timer_timeout() function, I can be sure all mobs that are created are added to the "mobs" group. I then unselected the "mobs" group in Main node so that Main was not in the "mobs" group any more. This fixed my problem.

[rmondragon]

After reading some of the comments, what it worked for me was :

• Be sure that "mobs" groups was created only in Mob scene and not in any other scenes by mistake with the same name.

• Make the group 'mobs" type Scene (no Global) to the main node of the Mob scene. Just the main one, I didn't need to select all sub-nodes. If you make it GLOBAL , it will show up on Main scene, available for all sub scenes.

• Add GetTree().CallGroup("mobs", Node.MethodName.QueueFree); at the end of `Main.GameOver.

I don't think that you need to do call mob.addGroup("mobs") b/c any instance of Mob will be part of "mobs" group b/c it was checked in Mob scene.

[AriHStein]

I had a related issue. Mobs were not being removed from the scene even though I had created the scene group and called "queue_free" on the group.

It turns out I had the VisibleOnScreenNotice2D node in the mob scene selected when I created the mob scene group, so the notification nodes were getting added to the group but NOT the root mob node. Checking the mobs scene group in the root mob node and unchecking it in the children resolved the issue.

Just in case anyone else ends up here with a related issue again. :)

[BastardSeagull]

Something breaking down between my _on_start_button_pressed and new_game, not sure what I'm missing.

Tried disconnecting and reconnecting, but no change. new_game triggers fine if I have _ready call it. I'm seeing the debug print I added for the start button press.

Best I can tell is the signal isn't being emitted.
Debugger is giving me "Standalone expression (the line may have no effect)." for my start_game.emit line, but it's identical to the finished project (pasting that in also doesn't resolve the bug).

Anyone have an idea what's breaking down?

Here's my _on_start_button_pressed:

func _on_start_button_pressed():
	print("Debug: Start Button pressed")
	$StartButton.hide()
	start_game.emit

Here's my new_game:

func new_game():
	print("Debug: new_game called")
	score = 0
	$Player.start($StartPosition.position)
	$StartTimer.start()
	$HUD.update_score(score)
	$HUD.show_message("Get Ready")

[Roedhip]

Have you connected the start_game() signal from your HUD node to the new_game() function in main.gd?

You can check if they are connected by selecting the HUD node in your main scene and looking at its signals in the right hand panel (in this panel, select "Node" from "Inspector"/"Node"/"History", and then make sure you are on "Signals" not "Groups"). At the top of the list of signals you should see the hud.gd category, and underneath it start_game(). In my scene, there is a green arrow underneath start_game() that points to new_game().

If this connection isn't there, here is the line from the tutorial above that explains how to make the connection:
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.

If the connection is there and is spelled correctly, I don't know what is going wrong.

[BastardSeagull]

Unfortunately I have; that's why I'm confused.

Looks like it's time to join the Discord!

[BastardSeagull]

I was just missing the () after emit. Whoops!

[sec-knight]

I was crashing with an error that it couldn't find "$HUD.update_score(score)" and I had to poke around for the solution. Mine was named #hud and not #HUD. Case matters apparently, because I fixed the case and the game works fine.

Hope that makes sense and helps someone.

[InfieldTriple]

So I worked through this over a couple of days and I was a bit confused at the end because I realized that I never added my mob scene to the Main tree. So I was left wondering "how the f is this even connected?" Of course it was a bit simple to solve by simply going backwards. But I wonder if it would be useful to show the mob scene in the tree somehow. Basically to show its being used by Mobpath. Maybe this would be good for a small game like this, and would be problematic in a complicated scene.

[jsonjunkie]

it isn't that the MobPath is using the mob scene, it is the other way around.

the mob scene uses MobPath to give an instantiated mob its positioning and related values like direction and velocity.

all this happens in the _on_mob_timer_timeout() function (in the script attached to the main scene) including the instantiation of a mob into the main scene:

var mob = mob_scene.instantiate()

[just1and0s]

Hi all, I have having an issue after pressing Start button. Error message: Attempt to call function 'start' in base 'null instance' on a null instance. There seems to be an issue with the message timer activation. 3 things were called onto the stack frames and the corresponding code below:

0. hud.gd at function: show_message

func show_message(text):
	$Message.text = text
	$Message.show()
	$MessageTimer.start()

1. main.gd at function: new_game

func new_game():
	score = 0
	$Player.start($StartPosition.position)
	$StartTimer.start()
	$HUD.update_score(score)
	$HUD.show_message("Get Ready")
	get_tree().call_group("mobs", "queue_free")

2. hud.gd at function:_on_start_button_pressed

func _on_start_button_pressed():
	$StartButton.hide()
	start_game.emit()

Can anyone share where I went wrong?

[just1and0s]

1 extra S in the $MessageTimer.start() haha

[ItzTK]

Did you figure out the issue? Because just1and0s is just lying?

[MaximeRoulin]

They are the original poster, so I'm guessing they just edited their own post above to have the correct syntax.

[ElectricZax]

Created by just1and0s - September 8th.
Edited by Calinou - September 15th.

Maybe the code was fixed and now you don't see the mistake that has been made in the first place?

[MatthewWinchester0]

The instructions say to extend HUD from CanvasLayer. But if I do I get this error:

script inherits from native type ‘area2d’ so it cannot be instanced in object of type node

Changing it to "extends Node" works - I found a similar question posed online too so I was surprised not to see a similar comment here.

[BraveVN]

which version of Godot are you using?

[MatthewWinchester0]

v4.3.stable.official [77dcf97d8]

However, when I used the project files downloaded from the site, and fixed a couple of things because they didn't support 4.3, it works using "extends Canvas Layer". So I'm going to assume I did something wrong earlier and that is the real error.

[vncafecode]

strange, I used the same version and the same assets and everything in the tutorial worked fine

[webnard]

I was running into a similar problem

Script inherits from native type 'CanvasLayer', so it can't be assigned to an object of type: 'Node'

It turned out that my Main.gd node had extends CanvasLayer, but the official demo file uses extends Node. I don't know how that happened. Changing the Main node to extend Node instead of CanvasLayer fixed it, and I could the HUD as extending CanvasLayer.

[webnard]

Oops, never mind, I was looking at the wrong script and can't edit my comment. I don't know why I'm getting the issue. I'm on v4.3.stable.mono.arch_linux

[LFAdams]

Hello I am having some issues with my scripts breaking at the

start_game.emit()

portion of the code. I have added

signal start_game

to the top of the HUD.gd script, under extends CanvasLayer, and linked the start game signal from later in the hud.gd script

func _on_start_button_pressed():
	$StartButton.hide()
	start_game.emit()

to the new_game() function in the main.gd script

func new_game():
	score = 0
	$Player.start($StartPosition.position)
	$StartTimer.start()
	$HUD.update_score(score)
	$HUD.show_message("Get Ready")
	get_tree().call_group("mobs", "queue_free")

Despite seemingly following the instructions, when I press the start button the game crashes, and the debugger identifies the line with start_game.emit() as the point where the code breaks. Can anyone tell me what I am doing wrong?

[LFAdams]

I deleted the line containing

start_game.emit()

and replaced it with

start_game.emit()

and it seems to work now, despite looking exactly the same to my eyes. I think there was some kind of hidden character messing it up or something.

[wuliwong]

I also had to start the ScoreTimer in the new_game function. I added the MobTimer.start() to it on the last tutorial section, it was also left out. I feel like I'm missing something but I can't seem to make it work without starting the timers when a new game starts. It also makes logical sense to start these timers when a new game starts. :shrugs:

	$ScoreTimer.start()
	$MobTimer.start()

[wuliwong]

Eesh, sorry, I should have previewed that before I sent it. Can't seem to edit it now. So anyway, here's my new_game function:

func new_game():
	get_tree().call_group("mobs", "queue_free")
	score = 0
	$Player.start($StartPosition.position)
	$HUD.update_score(score)
	$HUD.show_message("Get Ready")
	$StartTimer.start()
	$ScoreTimer.start()
	$MobTimer.start()

And this is connected the the HUD start_game method.

[jsonjunkie]

did you have your StartTimer node (with wait time set and one shot set to true) as a child of the root node of the main scene?

from there you have to connect that timer's timeout signal to the main scene and have it call _on_start_timer_timeout where the mob and score timers are set to start

func _on_start_timer_timeout():
	$MobTimer.start()
	$ScoreTimer.start()

after the set wait time passes for StartTimer, the function above should get called which in turn starts the mob and score timers

[ElectricZax]

Thanks to Calinou,
You can edit/delete comments from GitHub Discussions directly.
Login to GitHub and from #69 you can find your comment, then use drop-down menu to Edit or Delete your post.

https://ibb.co/7KZs9Xt

[freakyfrogboy24531]

I'm pretty sure I followed all the instructions but for some reason the score wont update. It merely stays at zero

[aniran96]

I am having the same issue.

[aniran96]

nvm. i got it. i was having issues with the timeout function.

[nashbeez]

What was the solution that you came to? I am having the same issue. All of my timers are connected to the Main node and the MobTimer and ScoreTimer are started with the StartTimer.

[RVishnu17]

I hope yall synced with per second counter,

score+=1
update_score/show_score(score) ??

[Langerz82]

When trying to make a signal from hud - start_game() to Main - new_game(). In the Connect a Signal to a method window I select Main (root node), but in the Select Method window the new_game() function is not appearing even though the main.tscn file is attached to the Main node. So I cant make the signal work. I have a working Player hit signal so I don't know what the Issue is.

See: https://i.imgur.com/suCspm4.jpeg

Using Godot Engine v4.3.stable.official [77dcf97d8]

[Langerz82]

I am so stupid. I checked my attached script in main.tscn and it was using "hud.gd", not "main.gd". If you get my issue double check your main.tscn file has "main.gd" attached. Glad I figured it out though.

[chenIshi]

I had a rather trivial question on the function design here:

func show_message(text):
	$Message.text = text
	$Message.show()
	$MessageTimer.start() # here starting a timer without timeout handler within scope

In this function, the callee show_message initializes the timer, while the caller show_game_over later uses wait to let the text shown for a while. My point is, the interaction here is weirdly coupled. The callee implicitly expects the caller to handle the timeout signal. Normally we want to keep components closed in necessary scopes, as mentioned in another doc. Is there any benefit for the current call structure? Otherwise, is it possible to make it like:

func show_message(text):
	$Message.text = text
	$Message.show()

func show_game_over():
    $MessageTimer.start()
	show_message("Game Over")
	await $MessageTimer.timeout

This approach makes sure that the usage of $MessageTimer only stays inside the show_game_over. I am not sure performance-wise it impacts anything (since I reduce no workload), but I assume it can be more debug-friendly?

[ElectricZax]

I played around a bit to change the rules of the game - instead of dying I wanted to collect mobs for extra points (and the game would end after 30 seconds). So I did the following:

func _on_player_hit():
		score +=10
		$Mob.hide()
		$HUD.update_score(score)

But the $Mob.hide() works only for the first mob. After that I just go through the mobs. I get the +10 points, so the collision works, the hit effect works, but only the $Mob.hide() stops working.

Any ideas?

[ElectricZax]

Okay... the last one is not entirely correct. $Mob.queue_free() works, but since there are new mobs every 0.5s it is buggy and sometimes removes the correct mob, other times removes another mob.

I can't find the comment section on Git to edit my comments. Where are they?

[Calinou]

I can't find the comment section on Git to edit my comments. Where are they?

Use the edit button in the top-right corner of each comments on the GitHub discussion page on the right (which I circled):

[ElectricZax]

My issue is where to find the 'discussion page'. I use the Edit on GitHub to go to the page, but then I don't see the discussion there.
I can't expect people to give me links to the discussion page every time...

[Calinou]

You can click the comment count at the top of the user notes:

I agree it's not obvious, especially since it doesn't look like a link. This could be improved on Giscus' end.

[VicLopes]

I believe you'd be better off putting a hit() detector on the mob itself to delete a singular instance of it rather than relying on the player's hit detection going up to the main scene, then triggering a deletion within the mob scene group.

[SoullessOwl77]

I am having issues with my Start Button. When I press it, it toggles down/up but does not start a new game or print the debug line I inserted.

func _on_start_button_pressed():
print("Debug: Start Button pressed")
$StartButton.hide()
start_game.emit()

It does show as connected, even deleted the connection and reconnected. I don't get any errors when I press the button and the only debugging info I am getting refers to delta not being used.

[chaixiaoai]

I had the same problem. I deleted the empty _ready() and _process() functions in main, and the game worked. But then I added them back, and it also worked. So, I don't know why it worked...

[stevula]

I didn't see this spelled out anywhere but I had to call game_over() in the signal handler _on_player_hit(), otherwise the game would keep going on after colliding with a creep.

[iAntaSt]

I need help. The score isn't working for me. When time passes the score stays the same i will put the hud and main codes in the reply to anyone explain why isnt working.

[iAntaSt]

main

extends Node2D

@export var mob_scene: PackedScene
var score


# Called when the node enters the scene tree for the first time.
func _ready() -> void:
	pass # Replace with function body.


# Called every frame. 'delta' is the elapsed time since the previous frame.
func _process(delta: float) -> void:
	pass


func game_over() -> void:
	$ScoreTimer.stop()
	$MobTimer.stop()
	$HUD.show_game_over()
	
func new_game():
	score = 0
	$Player.start($StartPosition.position)
	$StartTimer.start()
	$HUD.update_score(score)
	$HUD.show_message("Get Ready")
	get_tree().call_group("mobs", "queue_free")


func _on_score_timer_timeout() -> void:
	score += 1
	$HUD.update_score(score)


func _on_start_timer_timeout() -> void:
	$MobTimer.start()
	$ScoreTimer.start

func _on_mob_timer_timeout() -> void:
	var mob = mob_scene.instantiate()
	
	var mob_spawn_location = $MobPath/MobPathFollow2D
	mob_spawn_location.progress_ratio = randf()
	
	var direction = mob_spawn_location.rotation + PI / 2
	
	mob.position = mob_spawn_location.position
	
	direction += randf_range(-PI / 4, PI / 4)
	mob.rotation = direction
	
	var velocity = Vector2(randf_range(150.0, 250.0), 0.0)
	mob.linear_velocity = velocity.rotated(direction)
	
	add_child(mob)

[iAntaSt]

hud

extends CanvasLayer

signal start_game

func show_message(text):
	$Message.text = text
	$Message.show()
	$MessageTimer.start()
	
func show_game_over():
	show_message("Game Over")
	
	await $MessageTimer.timeout
	
	$Message.text = "Dodge the Creeps!"
	$Message.show()
	
	await get_tree().create_timer(1.0).timeout
	$StartButton.show()

func update_score(score):
	$ScoreLabel.text = str(score)

# Called when the node enters the scene tree for the first time.
func _ready() -> void:
	pass # Replace with function body.


# Called every frame. 'delta' is the elapsed time since the previous frame.
func _process(delta: float) -> void:
	pass


func _on_start_button_pressed() -> void:
	$StartButton.hide()
	start_game.emit()


func _on_message_timer_timeout() -> void:
	$Message.hide()

[AlexLea444]

Your error is having $ScoreTimer.start in main instead of $ScoreTimer.start().

[szpolny]

Maybe I'm not sure, because i'm coming from the webdev. Isn't it better to make interaction on even button_up than on pressed?

[Calinou]

By default, pressed is emitted when the button is released, so it's the same as button_up. However, you can also change the button press behavior to happen on press instead of on release in the Button properties. This is useful for certain use cases such as keyboard/gamepad input, where acting on press is the usual UX convention instead of acting on release.

[Bagher79]

hi
i fallowed every step of this tutorial but i have a problem:
my game start without pressing start button.
this is my main and HUD codes:
main:

extends Node

@export var mob_sence :PackedScene
var score

func _ready() -> void:
	new_game()
	
func game_over() -> void:
	$mob_timer.stop()
	$score_timer.stop()
	$HUD.show_game_over()

func new_game():
	$player.start($start_position.position)
	$start_timer.start()
	score=0
	$HUD.updare_score(score)
	$HUD.show_massage("Get Ready")
	get_tree().call_group("mobs","queue_free")

func _on_mob_timer_timeout() -> void:
	var mob=mob_sence.instantiate()
	
	var mob_spwan_location=$mob_path/mob_spwan_location
	mob_spwan_location.progress_ratio=randf()
	
	var direction=mob_spwan_location.rotation+PI/2
	
	mob.position=mob_spwan_location.position
	
	direction+=randf_range(-PI/4,PI/4)
	mob.rotation=direction
	
	var velocity=Vector2(randf_range(150.0,250.0),0.0)
	mob.linear_velocity+=velocity.rotated(direction)
	
	add_child(mob)


func _on_score_timer_timeout() -> void:
	score+=1
	$HUD.updare_score(score)

func _on_start_timer_timeout() -> void:
	$mob_timer.start()
	$score_timer.start()

HUD:

extends Label

signal start_game

func show_massage(text):
	$massage.text=text
	$massage.show()
	$show_massage_timer.start()
	
func show_game_over():
	show_massage("Game Over")
	await $show_massage_timer.timeout
	$massage.text="Doge the creeps!"
	$massage.show()
	await get_tree().create_timer(1.0).timeout
	$play_button.show()

func updare_score(score):
	$score.text=str(score)
	


func _on_play_button_pressed() -> void:
	$play_button.hide()
	start_game.emit()


func _on_show_massage_timer_timeout() -> void:
	$massage. Hide()

[chaixiaoai]

You need to delete the _ready() func in main.

[MrSamuerYTBER]

help me there are 2 problems:

1 - i can only start the game with the main node selected and pressing F6 (play current scene)
2 - when i start the game the creeps doesn't do anything to me

[MrSamuerYTBER]

oh i got the creep problem

[MrSamuerYTBER]

i got another problem too:

when it goes game over the game crashes or instead doesn't show the start button

console:
hud.gd:24 @ show_game_over(): Note not found "HUD" (relative to "/root/Main/HUD").

[Crysteier]

In cases like these it's better to show code snippets of you code. Try posting you code in hud.gd and main.gd.
Your first problem with the scene, maybe you just forgot to set the main scene in the FileSystem dock.
Your game crashing problem, maybe you just forgot to insert the HUD scene into the Main scene.

[A-Nick-0]

I'm so dumb, I called MessageLabel Message and not worked

[Steelroo]

As soon as I hit the start button, the game crashes with this error,

"main.gd:18 @ new_game(): Node not found. "HUD" (relative to "/root/main")."

This is the func that the error is and its on the "$HUD.update_score(score)" line.

func new_game():
	score = 0
	$Player.start($StartPosition.position)
	$StartTimer.start()
	$HUD.update_score(score)
	$HUD.show_message("Get Ready")

[Karnak-Kid]

This happens because the “Hud” child in Main’s Scene menu has to be the same name (case sensitive) as the gd script value “$HUD.”

[mungggu]

I'm really new to godot so perhaps it's a stupid question:
the "hit" signal that is emitted when a mob collides with the player, what is this signal for? Am I wrong or is it never used!?

[evilnose]

The "hit" signal should be connected to the game_over function in the Main node. You can confirm by selecting the Player Node and checking the "Node" tab on the right. The handler "game_over" should be under "hit()". If it's not,

[curtburgess]

Just a tip, when I encounter bugs (as I did on the last two sections) it helped me to compare my GDscript code to the tutorial code from the Github link they shared. For whatever reason there have been a couple of instances where I totally left out lines of code in a function for some reason, and just comparing my functions to the Github code has been a quick and easy way to tell if I just missed something or mistyped something.

[Jacinto73]

My God I actually finished it. I have no training or coding skills but still can't shake a fascination with it. But I changed it so player turns in whatever direction they're going, also changed $HUD.show_game_over() to $HUD.show_message("Game Over"), where you can put whatever text you want there. There is one problem: none of the creeps are moving. They spawn randomly along the path, and animate correctly, but don't go anywhere. The "Game Over" works when I run into them, but they're paralyzed. Did this happen with anyone else? Does it have to do with paths? Here's the code I have for that section, I'd appreciate any help:

func _on_mob_timer_timeout() -> void:
	# create a new instance of the scene
	var mob = mob_scene.instantiate()
	# Choose a random location on Path2D.
	var mob_spawn_location = $MobPath/MobSpawnLocation
	mob_spawn_location.progress_ratio = randf()
	# Set the mob's direction perpendicular to the path direction.
	var direction = mob_spawn_location.rotation + PI / 2
	# Set the mob's position to a random location
	mob.position = mob_spawn_location.position
	# Add some randomness to the direction.
	direction += randf_range (-PI / 4, PI / 4)
	mob.rotation = direction
	# Choose the velocity for the mob
	var velocity = Vector2(randf_range(150.0, 250.0), 0.0)
	add_child(mob)

[rodlopes981]

You have declared the value of var velocity, but seem to be missing a step to assign it to the mob after the declaration:
mob.linear_velocity = velocity.rotated(direction)

[Jacinto73]

Thank you so much, you're a lifesaver. That worked. Don't know how I missed it after scrutinizing everything so acutely.

[MrSamuerYTBER]

help me i have a problem with the player being invisible in-game and when in title screen the player is visible here is my code

# player.gd
extends Area2D
signal hit

@export var speed = 400 # How fast the player will move (pix/sec)
var screen_size # Size of the game window.

func _ready():
	screen_size = get_viewport_rect().size
	show()

func _process(delta):
	var velocity = Vector2.ZERO # The player's movement vector
	if Input.is_action_pressed("move_right"):
		velocity.x += 1
	if Input.is_action_pressed("move_left"):
		velocity.x -= 1
	if Input.is_action_pressed("move_down"):
		velocity.y += 1
	if Input.is_action_pressed("move_up"):
		velocity.y -= 1
	
	if velocity.length() > 0:
		velocity = velocity.normalized() * speed
		$AnimatedSprite2D.play()
	else:
		$AnimatedSprite2D.stop()

	position += velocity * delta
	position = position.clamp(Vector2.ZERO, screen_size)

	if velocity.x < 0:
		$AnimatedSprite2D.flip_h = true
	else:
		$AnimatedSprite2D.flip_h = false


func _on_body_entered(_body: Node2D) -> void:
	pass # Replace with function body.
	hide() # Player disappears after being hit
	hit.emit()
	# Must be deferred as we can't change physics proprierties on a physics callback.
	$CollisionShape2D.set_deferred("disabled", true)

func start(pos):
	position = pos
	show()
	$CollisionShape2D.disabled = false

# main.gd
extends Node

@export var mob_scene: PackedScene
var score

func game_over():
	$ScoreTimer.stop()
	$MobTimer.stop()
	$HUD.show_game_over()
	$Music.stop()
	$DeathSound.play()

func new_game():
	score = 0
	$Player.start($StartPosition.position)
	$StartTimer.start()
	$HUD.update_score(score)
	$HUD.show_message("Get ready!")
	$Music.play()
	get_tree().call_group("mobs", "queue_free")

func _on_score_timer_timeout():
	score += 1
	$HUD.update_score(score)

func _on_start_timer_timeout():
	$MobTimer.start()
	$ScoreTimer.start()

func _on_mob_timer_timeout():
	# Create a new instance of the Mob scene.
	var mob = mob_scene.instantiate()
	
	# Choose a random location on Path2D.
	var mob_spawn_location = $MobPath/MobSpawnLocation
	mob_spawn_location.progress_ratio = randf()
	
	# Set the mob's direction perpendicular to the path direction.
	var direction = mob_spawn_location.rotation + PI / 2
	
	# Set the mob's position to a random location.
	mob.position = mob_spawn_location.position
	
	# Add some randomness to the direction.
	direction += randf_range(-PI / 4, PI / 4)
	mob.rotation = direction
	
	# Choose the velocity for the mob.
	var velocity = Vector2(randf_range(150.0, 250.0), 0.0)
	mob.linear_velocity = velocity.rotated(direction)
	
	# Spawn the mob by adding it to the Main scene.
	add_child(mob)

[curtburgess]

I think it's because when velocity is 0 you stop animation? Maybe try playing an "idle" animation.

[curtburgess]

But I'm often wrong. 😆

[iiipt]

Hi I am having problem with the Start button, It does nothing when I press it.

My Main:

extends Node

@export var mob_scene: PackedScene
var score

func game_over():
	$MobTimer.stop()
	$ScoreTimer.stop()
	$HUD.show_game_over()
	
func new_game():
	get_tree().call_group("mobs", "queue_free")
	score = 0
	$Player.start($StartPosition.position)
	$StartTimer.start()
	$HUD.update_score(score)
	$HUD.show_message("Get Ready")
	
func _on_score_timer_timeout():
	score += 1
	$HUD.update_score(score)
	
func _on_start_timer_timeout():
	$MobTimer.start()
	$ScoreTimer.start()
	
func _on_mob_timer_timeout():
	# Create a new instance of the Mob scene.
	var mob = mob_scene.instantiate()

	# Choose a random location on Path2D.
	var mob_spawn_location = $MobPath/MobSpawnLocation
	mob_spawn_location.progress_ratio = randf()

	# Set the mob's direction perpendicular to the path direction.
	var direction = mob_spawn_location.rotation + PI / 2

	# Set the mob's position to a random location.
	mob.position = mob_spawn_location.position

	# Add some randomness to the direction.
	direction += randf_range(-PI / 4, PI / 4)
	mob.rotation = direction

	# Choose the velocity for the mob.
	var velocity = Vector2(randf_range(150.0, 250.0), 0.0)
	mob.linear_velocity = velocity.rotated(direction)

	# Spawn the mob by adding it to the Main scene.
	add_child(mob)

my HUD:

extends CanvasLayer

# Notifies `Main` node that the button has been pressed
signal start_game

func show_message(text):
	$Message.text = text
	$Message.show()
	$MessageTimer.start()
	
func show_game_over():
	show_message("Game Over")
	# Wait until the MessageTimer has counted down.
	await $MessageTimer.timeout
	$Message.text = "Dodge the Creeps!"
	$Message.show()
	# Make a one-shot timer and wait for it to finish.
	await get_tree().create_timer(1.0).timeout
	$StartButton.show()
	
func update_score(score):
	$ScoreLabel.text = str(score)
	
func _on_start_button_pressed():
	$StartButton.hide()
	start_game.emit()

func _on_message_timer_timeout():
	$Message.hide()

[chiq2045]

Did you connect the pressed() signal on the StartButton node to the HUD node? In the tutorial, that would have been the instructions given right before the code for _on_start_button_pressed() and _on_message_timer_timeout()

[iiipt]

yeah that was it. Thanks a lot.

[FiendZ911]

I just wanted to state my issue and how I resolved it for anyone who may have been dealing with the same thing. When trying to get the script to delete the old creeps by using the call group function to have them cleared from queue, it was not working for me in the new game function. I remedied by adding the same line of code to the game over function and it works like a charm.