Porblem with Tutorial

[kidscancode]

Porblem with Tutorial

[Uradamus]

I'm having a similar issue. Though I stopped at the point where the hud is implemented, since the game fails to spawn enemies at that point where it says to test it out. One thing I noticed over the last few hours of trying to figure out why it might not be working is that I can't use the documentation lookup shortcut on the following line.
var mob = Mob.instance()

In fact, while typing it out, I wasn't offered any sort of autocomplete, which was also strange. Makes me think something has changed since this tutorial was made in regards to either how PackedScenes are handled, or at least the way they should be instanced.

This is really frustrating though, as I've rechecked all the code so far in all the scripts and the node layouts dozens of times and nothing looks out of place and there are no errors, beyond the following warning.
`W 0:00:01.075 The argument 'body' is never used in the function '_on_Player_body_entered'. If this is intended, prefix it with an underscore: '_body'
<C++ Error> UNUSED_ARGUMENT

Player.gd:45`

Which I assume is just down to something not being covered yet at this point in the tutorial, and since it is in relation to the Player, which is working just fine, it seems unrelated.

[Uradamus]

As a minor update, I found myself looking into the Godot demo repo to see what was going on with that version, and I see there have been several changes to the Main.gd over there, and I tried all the relevant changes to the mob spawning portions, but they don't seem to make any difference. Still not seeing any mobs spawn.

Oh well, throwing in the towel on this one as a lost cause for now, and going to look for other tutorials instead until this is straightened out. I've spent too many hours at this point to be worth continuing until the tutorial is updated to something that properly works every step of the way. It's a real shame too, as this looked really promising and informative, but no use if it isn't going to run as presented in the tutorial.

Getting this fixed should be a priority, considering how the tutorial is so prominently positioned as a "Your First Game" tutorial on the official documentation site. Making it something that is likely to negatively impact a fairly large portion of the new user base coming to the engine for the first time. And it was promoted as one of the better starter tutorials by Terry Cavanagh in the intro page for his recent Stop Waiting for Godot game jam, which was what actually brought this tutorial to my attention (even though I only heard about the jam after it ended >.<).

I took a break from the engine for a while, and was just looking for some quick refreshers to get back up to speed. I thought I'd be done with the tutorial within an hour or two, but that has ballooned into 5+ hours now and still don't have a working game out of it. So it has been a real disappointment, and I'd hate for something similar happening to those just testing the waters and being turned off by the engine over it, especially with this being an official tutorial.

[theotherjasonrainbird]

I've just gone through the same frustrating experience as @Uradamus above.

After having carefully entered everything on the tutorial I saw had made a mistake with the collision code, so I came to this repo to double check what I had entered.

Only by entirely cloning the repo did I finally get something working, and even then what's in master isn't identical to what's in the tutorial (the Enter shortcut to start the game is missing).

This has been an off-putting experience and is not a welcome introduction to Godot.