getting_started/first_2d_game/05.the_main_game_scene

[giscus[bot]]

getting_started/first_2d_game/05.the_main_game_scene

Now it's time to bring everything we did together into a playable game scene. Create a new scene and add a Node named Main. (The reason we are using Node instead of Node2D is because this node will...

https://docs.godotengine.org/en/latest/getting_started/first_2d_game/05.the_main_game_scene.html

[BFrek]

For the code to actually work, the timer need to be activated through: "func _on_start_timer_timeout():". However, to do so you need to head into the timer node(for the example above, it would be the StartTimer node on the left side of your screen under main in the scene) change tab from inspector to node on the right side of your screen and connect the timeout signal to the main node. Just right click the timeout signal(or double click it), a window will pop up and then left click the main node and press connect. Then do that for all three of the timers(StartTimer, ScoreTimer, MobTimer). (The code didn't work for me until I did this, so I dont know if its my personal issue or not but ill leave the solution here for future viewers)

[psycowboy57]

Thanks for this. I had one timer that wasn't connected.

[kalvinzabo]

I think the tutorial is missing to autostart in addition to the one shot. Anybody knows how to fix this in the documentation

This should not be necessary, since the StartTimer is manually started in the new_game() function. Maybe you didn't notice the last step of the tutorial, which is calling new_game() in _ready()?.

[dejavu3750]

Thank you for this!

[drewcoder]

I'm using 4.5dev4 and I also had to enable Autostart before the mob appeared on my screen.

MacBook Pro M2 Max
Sequoia 15.5

[drewcoder]

Enabling Autostart causes an issue later when testing out the Heads up Display. When you run the program you will see the HUD and about 2 seconds later a mob appears and the program crashes.

[Minoxsta]

I'm having problems with the "$Player.start($StartPosition.position)", it gives "Invalid call. Nonexistent function 'start' in base 'Area2D (Player.gd)'?

I was thinking it would be more like "$Player.position(...)" but that doesn't work either.

[WldGeese]

If you check the script on your Player (you can get to this by clicking on the scroll next to your Player node on your main scene) do you have a start function defined there? It should look like this:

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

[Minoxsta]

I did not. I went back to check if it was in the instructions, and I seem to have missed that part. Oopsie. Thank you very much for helping.

[discohands]

@WldGeese brilliant. I guess I overlooked this code block as being a part of community notes.

[softwarehunter07]

In the testing phase, the creatures don't appear.
I'm using C#

[softwarehunter07]

https://github.com/softwarehunter07/MiniGameCS.git

[softwarehunter07]

i fixed problem, thanks for help

[ThomasCrane]

How did you fix the problem? I'm running into the same issue. I grabbed your git and it's not working either, so no idea what you did to fix it.

[ThomasCrane]

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

For example:

When connecting timeout() from MobTimer, ScoreTimer, StartTimer to Main, it will default to _on_mob_timer_timeout and so on. This needs to be changed to OnMobTimerTimeout(), and so on for the rest.

If you are having this issue at this point, you will also need to go back into the Player class and change _on_body_entered to OnBodyEntered()

[ThomasCrane]

Actually, after testing, leave the () off at the end because Godot throws an error, 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.

[ThomasCrane]

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

For example:

When connecting timeout() from MobTimer, ScoreTimer, StartTimer to Main, it will default to _on_mob_timer_timeout and so on. This needs to be changed to OnMobTimerTimeout(), and so on for the rest.

If you are having this issue at this point, you will also need to go back into the Player class and change _on_body_entered to OnBodyEntered()

[ThomasCrane]

Actually, after testing, leave the () off at the end because Godot throws an error, 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.

[A-Nick-0]

Thanks! it worked for me!

[vmorris]

Next, select the instance of the Player scene under Main node in the Scene dock, and access the Node dock on the sidebar. Make sure to have the Signals tab selected in the Node dock.

This is crazy talk... please maybe an animation or a screenshot of what you're saying here?

[vmorris]

How about this:

Open the Player scene, either by clicking on the tab if it's still open, or double clicking on the player.tscn file in the FileSystem.

[vmorris]

func game_over():
	$ScoreTimer.stop()
	$MobTimer.stop()

It's just really confusing where this code should go.

[vmorris]

Oh, I see.. at no point was I instructed to add Player as a sub node to Main... that's pretty confusing.

[vmorris]

Click the Instance button (represented by a chain link icon) and select your saved player.tscn.

I stand corrected.

[Swagalicious1228]

Hi, I keep getting the error "Invalid set index 'position' (on base: 'RigidBody2D (mob.gd)') with value of type 'PathFollow2D'. I'm new to Godot so I've got no idea what it means, it causes the game to crash after a couple seconds. Any help would be greatly appreciated.

[ElectricZax]

If you haven't found the cause you may start a new project and go through the tutorial again. I had to restart a few times and every time I understand more and more of the code (and why it fails).

[jknezevic1712]

I had the same issue and the bug was in the line:

mob.position = mob_spawn_location

You just need to write it like this:

mob.position = mob_spawn_location.position

[starmandeluxe]

I get this error: "player.gd:10 @ start(): Node not found: "CollisionShape2D" (relative to "/root/Main/Player")", so it doesn't run at all. I double checked and there is indeed a CollisionShape2D node underneath Player... What am I doing wrong?

[Harpogma]

I had the same mistake. Check on your Player if your "CollisionShape2D" is under your Player or under your "AnimatedSprite2D". For me it was under the sprite and not a child of the Player. If it is the case just move it under Player, save, and it should be ok.

[dbehmoaras]

I'm running into the same issue - I verified this by reparenting the CollisionShape2D node to the player but I'm still unable to run the game. What's weird is that it works just fine if I run the player scene by itself.

I should note that my player scrippt is in GDScript while my Main script is in C# so I'm using the GD.Load method to load the player script so that could be related. In case anyone tried to experiment with this, I will update my findings to see if this is the cause.

[dbehmoaras]

I just figured out the problem that currently has no workaround. It's related to this issue discussed below. It seems that while cross-language scripting works, inheritance does not. So when the engine looks for CollisionShape2D child of the player.gd in a C# context, it will throw the null pointer. While this is out of scope for the tutorial, I'm glad I learned this lesson.

Inheritance Issue: godotengine/godot#38352
Cross-language scripting doc page for reference: https://docs.godotengine.org/en/stable/tutorials/scripting/cross_language_scripting.html

[ghost]

Hi, newbie here trying to get tutorial working. Godot version 4.3 stable in question.
After finishing this page and trying to run I got:

"Script inherits from native type 'RigidBody2D', so it can't be assigned to an object of type: 'AnimatedSprite2D'

Tried to find out if anyone else has this problem but no luck.

[lukasQuatro]

hi, confirm the Mob is type RigidBody2D. link

found this, hope it helps

[MaryGz]

I was following along pretty well but I´m a bit lost on the _on_mob_timer_timeout function. My questions are:

• What is progress ratio? I imagine it's a spot on the path, but I´m not sure
• the direction variable is to avoid sending the mob outside the screen, I think
• does the range -PI/4, PI/4 ensure that the mob doesn't point outside?
• I have no idea what we did for the velocity variable. Why are we using vector2? I imagine there´s an obvious reason but I don't know what it is. What are we randomizing in the parameter?
• Is the add_child() the start of the lifecycle of mob and queue_free() the end?

The rest of the tutorial is amazing. Thank you for the excellent work you put into it.

[mike-j-brooks]

add_child() is a method of the Node class, it adds a child node. You can right click the name "add_child()" in the code editor and select "Lookup symbol" which opens the documentation directly in the editor - really neat feature.

[mike-j-brooks]

queue_free() sends the node into a queue to be deleted at the end of the current frame (per the docs). It could probably use a better name. "free" as in "free the memory allocation", or in human-speak "delete".

[mike-j-brooks]

PI == 180 degrees, so PI/4 == 45 degrees. The tutorial has you set the rotation of the mob at 90 degrees relative to the path that represents the level boundary. So imagine the mob is spawning on the right-side wall. It would by default be pointing directly left. Adding this range of (-45 to +45 degrees) will turn its direction somewhat up, or down, randomly. This is what results in the random direction effect.

[edjiang000]

Regarding PI/4 and PI/2: As the docs mention you can use degrees instead and convert to radians, which is more intuitive in my opinion. You can replace the following code:

	var direction = mob_spawn_location.rotation + PI / 2

with

	var direction = mob_spawn_location.rotation + deg_to_rad(90.0)

Same thing when randomizing the rotation of the mobs.

	direction += randf_range(-PI / 4, PI / 4)

can be replaced with:

	direction += randf_range(deg_to_rad(-45.0), deg_to_rad(45.0))

[kalvinzabo]

When you have doubts about any of Godot's built-in methods or members, remember that you can Ctrl+click it on the editor to access the offline documentation! It's one of Godot's coolest features imo.

[lethall]

Something odd with Godot 4.3 on Mac Sequoia (not verified with other platforms). The game starts and plays as expected but the MobTimer stops firing after a random number of mob instances has been created and freed. Eventually the player is left on the screen with no more mob instances and I have to quit the game. I added prints to verify this.

[lethall]

:-D Ha!

By adding a print statement in the game_over method, I found that I had actually been getting hit by a mob entity! Since there is no feedback yet... I was thinking that I had successfully dodged the creep :-D

My bad :-(

[GrindingCode]

so its not working when i put hide() in the player script on _ready the player never pops back up. When I put new_game() in the _ready function in Main the game crashes and I get 3 errors about unused parameters these include:

_process function delta parameter in main.gd
_on_body_entered() body parameter in player.gd
_process function delta parameter in mob.gd

Even when new_game() is taken out of the ready function in main.gd the game runs with an empty window just a blank grey screen. Please Help.

[ElectricZax]

_process function delta... this is because you have not removed the parts that are added by default. This part:
func _process(delta: float) -> void: pass

_on_body_entered... there is a suggestion to use "_body" instead of "body". You can change it if you want to.

None of these is a reason for the code to fail (they are in yellow). In my case I had missed the brackets and had "new_game" instead of "new_game()". You are missing something, but can't say what. Maybe start again.

[PikminDS]

I'm confused and stuck at _on_mob_timer_timeout. I copy and pasted the code into the main script but can't see the creatures. Using GDScript.

[ElectricZax]

Do you have the "$MobTimer.start()" ? A mob should appear at timeout, but if it doesn't start, then there is no timeout.

[wuliwong]

I had to add

MobTimer.start() to the new_game() function. Otherwise, it takes really long for mobs to start spawning.

[ElectricZax]

Mob timer and Start timer start after Start timer expires (one shot is ON). If you have high value for Start timer, then it will take a while for Mob timer and Start timer as well.

[jessodum]

To elaborate on comments above and in the code on how _on_mob_timer_timeout() spawns the mobs:

Imagine that the path drawn is a clockwise race car track where the start/finish line is point 1 (the upper-left corner, where we started drawing the path). When an imaginary race car is on any point of the track, it's pointing in the "forward" direction of the track.

As the race car is going along the track, it's progressing along from 0 to 100% of the track... (or a ratio 0.0 to 1.0).

randf() returns a random floating point number within 0.0 to 1.0.

Node MobSpawnLocation (aliased to variable mob_spawn_location) is our imaginary race car. So the line

mob_spawn_location.progress_ratio = randf()

... is setting the race car location to a random amount of "progress" along the track (or lap). Its direction is pointing "forward" for its position on the track.

To change the direction to point inward, (which is on the race car's right side), we first rotate it +90 degrees (PI/2). But then we want to add some variation by adding or subtracting up to 45 degrees (PI/4) to that perpendicular direction.
(I don't know why the mob.position is set in between the initial 90 degree rotation and the random +/- 45 degree adjustment. I suspect that line could... maybe even should... be moved above var direction = ... line).

randf_range(min, max) picks a random floating pointing number between min and max, instead of 0.0 and 1.0.

[ElectricZax]

I do not have the 'hit' scene. Even without filter 'hit' I cannot find it anywhere in the scenes.
I first created a node named "noob" instead of "player", but it was the wrong type, so I created the player as well. Then I have followed the steps and haven't made significant changes that (I think) could affect this.

https://ibb.co/vjnyDM2
(screenshot expires april 2025)

[ElectricZax]

I checked twice and it was there. I think that something went wrong with the copying of the node and data. It looks connected, but it does not appear. I started doing the tutorial from scratch and I passed that stage. I have other troubles now, but I will try to figure it on my own first.
The guide looks quite hard for first-timers, but after I made tons of mistakes and now that I'm doing it for the third time, it is way more understandable :D

[ElectricZax]

(is there an Edit or Delete function here?)

[Calinou]

(is there an Edit or Delete function here?)

Yes, but it's not exposed on the Giscus web interface. You need to go to the GitHub Discussions page instead, log into GitHub, then use the Edit button that's hidden behind the 3 dots icon in the top-right corner of your comment. The same goes for deleting a post.

[ElectricZax]

Thank you, you're great!
I managed to delete some stupid comments and on my 5th attempt I finally reach the next page.

[dud3]

Make sure your player.gd or noob.gd script is attached to the Player or Noob node itself.

[Quaid-004]

Hi all, Im new to Godot and trying to learn it for a team project (we all are but im the furthest ahead) and we all picked this to be our practice to get used to it, I was able to get my lil man back on screen after having to re do the entire thing due to an error on my part but the enemies wont spawn (earlier nothing spawned)

player.gd

extends Area2D
signal hit

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

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

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.animation = "walk"
		$AnimatedSprite2D.flip_v = false
		# See the note below about the following boolean assignment.
		$AnimatedSprite2D.flip_h = velocity.x < 0
	elif velocity.y != 0:
		$AnimatedSprite2D.animation = "up"
		$AnimatedSprite2D.flip_v = velocity.y > 0


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

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

mob.gd

extends RigidBody2D


func _ready():
	var mob_types = $AnimatedSprite2D.sprite_frames.get_animation_names()
	$AnimatedSprite2D.play(mob_types[randi() % mob_types.size()])
	
func _on_visible_on_screen_notifier_2d_screen_exited():
	queue_free()


main.gd

extends Node

@export var mob_scene: PackedScene
var score

func _ready() -> void:
	new_game()

# 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()

func new_game():
	score = 0
	$Player.start($StartPosition.position)
	$StartTimer.start()

func _on_score_timer_timeout():
	score += 1

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)

also I appologies, i dont know how to indent the code here, maybe i did it there, but if not, please forgive me

[LAyaJnamiJ]

I'm guessing it's one of two things:

1. the ModPath was drew anticlockwise instead of clockwise
2. the MobScene in main.gd is empty

[EngiDev-coder]

Check mob_scene. Is it selected or not. if it didn't then select it

[nyDupont]

Has anyone encountered this error before?
Invalid assignment of property or key 'progress_ratio' with value of type 'float' on a base object of type 'null instance'.

It gets raised in my _on_mob_timer_timemout() function, more specifically here:

mob_spawn_location.progress_ratio = randf()```

Thanks in advance :) 

[LAyaJnamiJ]

You might want to check the path of your mob_spawn_location; I managed to recreate the error by misspelling the path. It should be $MobPath/MobSpawnLocation.

[smallsweet]

make sure your mob path and mob path location nodes match the names the script is expecting (MobPath/MobSpawnLocation)

[nyDupont]

Having named the mob path "ModPath" was indeed my problem... Thanks a lot!

[Code-Wombat]

Hi! I started learning Godot, and the tutorial is working as intended, but i think i miss something. When i try to collide the player agaisnt a Mob, it pass through the mob and the game doesnt end. Can someone help please?

[Code-Wombat]

Update: I step back and re-connect the signal "on_body_entered". Now it works!

[EngiDev-coder]

I got this problem but not like that my game had crashed whenever i hit by enemy but now its working. how i did that?
just re connect the body node.

[dogstrot]

Don't know how to add a comment myself, so I'll write here, sorry! For anybody using C# and having the problem with the player not colliding with mobs, here's what worked for me:

1. Check whether you're setting CollisionShape2D`s property named Disabled in the code as true through SetDeferred. I put SetDeferred in the _Ready function and input true as an argument, which caused the player's collision to always be off, which made OnBodyEnter never work! You can see that the player's collision shape will always be gray (which means that it's off) while running the project and using Visible Collision Shapes option in the Debug menu.
2. Check that the OnBodyEnter function ( which should be in PascalCase in both the code and the Signal editor on the right) name is correct, and that it also has Node2D argument, otherwise it won't work.
3. Check that the player's collision mask bit is set to the same collision layer as the mobs`.

[shroomwiz]

Hi! I just started to learn Godot and have been following this tutorial. I'm having a problem with where the mobs spawn. They keep spawning in the top left corner where the path starts, but nowhere else. I re-read the steps at least 10 times and even re-did the path two times while checking it with the tutorial every second. Does anyone have any tips on how to fix this and make mobs spawn around the screen?

[jessodum]

It sounds like the mob position isn't getting set to the random value. Are you using GDScript or C#?
If you look at the mob timer timeout handler function (e.g., func _on_mob_timer_timeout() for GDScript), then these lines should be doing the random position:

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

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

Check to make sure those match what you have.

[shroomwiz]

Thanks so much. I somehow managed to miss the mob_spawn_location.progress_ratio = randf() all the times I checked through

[WDDD99]

I am new and I have followed the steps all the way till we test it on this step and I keep getting this error

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

I have tried to fix it but I nothing I do fixes it please help

[avery2588]

Also new here- looks like you may not have brought the player into the main node? im currently having an issue where nothing appears

[snowy3869]

Hi, I'm a newbie and when testing the game at this step, I keep getting the error Invalid assignment of property or key "position" with value of type "Vector2" on a base object of type "Node" and it points to this line of code:

mob.position = mob_spawn_location.position

and I'm not sure how to fix this. Here's the rest of the code for the Mob node, which should be identical to the tutorial.

extends Node
@export var mob_scene: PackedScene
var score

func _ready() -> void:
	new_game()

func _process(delta: float) -> void:
	pass

func game_over() -> void:
	$ScoreTimer.stop()
	$MobTimer.stop()
	
func new_game():
	score = 0
	$Player.start($StartPosition.position)
	$StartTimer.start()


func _on_mob_timer_timeout() -> void:
	var mob = mob_scene.instantiate()
	
	var mob_spawn_location = $MobPath/MobSpawnLocation
	mob_spawn_location.progress_ratio = randf()
	mob.position = mob_spawn_location.position
	
	var direction = mob_spawn_location.rotation + PI/2
	
	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

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

[snowy3869]

Nevermind, I fixed it. It turns out I accidentally made 2 mob scenes, the root node being Node type and another that is RigidBody2D.

[alexparm4]

ISSUE (Solved): Mob Enemy Animations not playing (stuck on one animation frame)
SOLUTION: Use code from a previous tutorial.

As of 3/25/2025
I did this whole tutorial a couple months ago in 4.3, and came back to do it again as a refresher. I noticed after following the tutorial exactly, THIS time the enemy animations would not work! While in the old tutorial, they still worked (thankfully have that code saved).

The problem is one changed line (actually from the previous section, but as the game is not tested until this part of the tutorial, I am putting it here, as I'd assume others with the same issue would check this comment section first before going to a previous one.)

In mob.tscn at the function " func _ready()" : the current tutorial has you use this line:
$AnimatedSprite2D.animation = mob_types.pick_random()

To get the mob sprites to play properly, I had to revert to the old line:
$AnimatedSprite2D.play(mob_types[randi() % mob_types.size()])

and then it worked for me

[Calinou]

You need to call play() after setting the animation property on AnimatedSprite2D. Using play() with a parameter is functionally equivalent, but the previous code is missing a line.

[alexparm4]

youre right:

$AnimatedSprite2D.animation = mob_types.pick_random()
$AnimatedSprite2D.play()

works also. Cool, thanks.

[milamazim]

Had the same problem, thanks for sharing

[UnexpectedPenguin]

Is there a reason the "_ready" and "_procces" functions are unused? I though they were both required or at the every least useful to make things in your game work?

[Honnigorega]

I am determined to use C# but the whole "Signals" event system seems to cause trouble. As suggested by someone else, I am creating the callback functions and then building the project, before I connect them to the signal by using "Pick".

So far it has worked just fine, but with the "hit" and "timeout" signals I am getting the following warning:

Missing connected method 'GameOver' for signal 'Hit' from node 'Main/Player' to node 'Main'.

These methods exist and they are indeed connected. The game runs fine... Then why do I get those warnings?

[Lurplle]

I added the code and rechecked it 3 times now, why won't my character move!?

[avery2588]

nothing shows up when i start.. am i missing anything or???

[avery2588]

game over was indeed defined in main scene, i was missing ".position" on the second line on new game but even after i fixed it nothing showed up

[Nowell5]

Hello everyone, when I test the game. The mobs are just flying across the screen and not using their animation properly. Looking for some help :)

Velocity controls that right? I have it set to 150.0 and 250.0 in the mob timer timeout function.

[Nowell5]

I fixed my problem by the way. Not only were the mobs just flying across the screen they would instantly drop as soon as they spawned.

I fixed it by going into project settings went to physics, clicked on 2D and set my default gravity to 0.0. It was set at 980 that is why my mobs were instantly dropping as soon as they spawn into the map !

[DanielLoeb]

Maybe this is useful to somebody: I ran into the problem that my player wasn't showing up during the gameplay test.

Here's what had happened: When creating the mobs, I accidentally created them as a part of the player scene. Reading the main game scene section of the tutorial, I realized my error and went to the player scene to "Save Branch as Scene" the mobs. After that, I could complete the main game scene and the mobs showed up, but the player didn't.

It turns out, I also had to remove the mobs from the player scene. Exporting them created a separate mob.tscn, but it did not remove the assets and code from the player scene. After I had removed the mobs from the player scene, the player showed up in the game.

[HeavyMetalPup]

Hey I'm new to Godot and programming in general and am using 4.4.1. I have the player node linked to the main node like it said to do and am having an issue where it won't load the test. The error I keep receiving is "Script inherits from native type 'Area2D', so it can't be assigned to an object type: 'Node'". As a note I also have the "main" node set as the Main Node for the project like the tutorial says and have all the code written as presented throughout the tutorial up to this point.

I've tried unlinking it and still get the same error and I've reattached it just for my own sanity. I've been staring at it for at least an hour trying to figure this out myself and even tried googling the issue to no avail. Any help/advice would be appreciated

[Calinou]

The root node of the player scene must be a node of type Area2D, not any other type. If the extends type at the top of the script is not the same class (or a parent class), it won't work. The tutorial is written with the assumption that the player scene's root node is an Area2D. Double-check that this is the case in the Scene tree dock; if not, right-click the node and use Change Type to change it to an Area2D.

[HeavyMetalPup]

I made sure the root node for the player scene is Area2D and it was and I even changed it to Area2D again just make certain but it's still returning the same error.

The "main" scene node root is just Node and I've linked them together like the tutorial says to do. Do I need to make the root Node for the main scene Area2D as well?

[HeavyMetalPup]

I'm also having an issue with the hit signal and creating the game_over() function. I have the player instanced in the main scene, but the connector only creates the game_over() function in the player script an not in the main script like it should. I've disconnected and reconnected it multiple times and even deleted the function out of player written it from scratch in the main scene and tried connecting it< but it only ever creates the function in the player scene

[mikegoatly]

The error I keep receiving is "Script inherits from native type 'Area2D', so it can't be assigned to an object type: 'Node'".

I ran into this - I'm not sure how it happened, but the Player script had been attached to the Main node as well. Double-check that the Main script is attached to your Main node (hover over the little script icon next to it).

[McJty]

I'm a bit confused. I have everything done exactly like the tutorial says (I double checked) but when I run the game I can move the player but the enemies appear briefly at the side of the screen and then immediatelly dissapear again. They don't move. Not sure what could be wrong here? Thanks

[McJty]

Never mind, fixed it. I accidentally used screen_entered instead of screen_exited for the mobs