Skip to content
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.

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

Dodge the creeps is helpful but outdated and no longer works completely #7022

Closed
DanielMcGuffey opened this issue Mar 19, 2023 · 14 comments
Closed
Labels
area:getting started Issues and PRs related to the Getting Started section of the documentation bug

Comments

@DanielMcGuffey
Copy link

4.0

I followed the dodge the creeps tutorial as someone completely new to coding and game dev. It was helpful only to a point. I finished coding player movement and did the rest of the code and it ran but nothing showed up no HUD or Mobs or even the player. When I was coding it there were some things that were outdated and no longer worked but most were not a very big deal. Except for the signals. I could make new signals but the emit code was null so didn't work I tried to rig something together. I am assuming the reason the game didn't start was because it didn't emit or call the new_game signal but, that is just a guess please update the tutorial so it doesn't have this problem in the future or add a warning saying "this is outdated and doesn't work except for player movement."

thank you for everything but please try fixing the problem.

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

@MisoMosiSpy
Copy link
Contributor

I went though this tutorial:

Using GDScript: The tutorial is almost correct (except for the signals and some minor errors), I was able to finish and run the game.

Using C#: There are quite a few issues, I am working on PR to fix them.

If you tried with GDScript what kind of issues are you facing?

@DanielMcGuffey
Copy link
Author

DanielMcGuffey commented Mar 23, 2023 via email

@MisoMosiSpy
Copy link
Contributor

OK, thanks for the info!

@DanielMcGuffey
Copy link
Author

DanielMcGuffey commented Mar 23, 2023 via email

@mj-h
Copy link

mj-h commented Mar 23, 2023

I was stuck in the 2d tutorial here. I think there is a step missing: The user has to add (drag/drop) the "Player" scene to the "Main" scene.

@MisoMosiSpy
Copy link
Contributor

MisoMosiSpy commented Mar 24, 2023 via email

@lancemgiles
Copy link

I had a similar issue as Daniel, but after finishing "the main game scene" section, the player became visible again. I don't think this is actually a bug but it would likely be helpful to new people to point out that the game won't really be testable again from the end of the the player section until the end of the main section. At least, that is what I thought was going on.

For me, the player does not get hidden when colliding with the mob - searching for information about that is what lead me to this thread. I'm not sure if this is problem on my end or not.

@skyace65 skyace65 added the area:getting started Issues and PRs related to the Getting Started section of the documentation label Mar 29, 2023
@Creidhne86
Copy link

Creidhne86 commented Apr 2, 2023

I'm stuck on the OnBodyEntered() part of the "Coding the player" section. I'm using C#.

Its a bit odd, because I'm connecting the signal, but getting an error as soon as I try and build the code that Godot imports..

Errors I'm getting:
...\2d_Game_Dodge_Creeps\player.cs(76,1): Top-level statements must precede namespace and type declarations.
...\2d_Game_Dodge_Creeps\player.cs(76,1): The modifier 'private' is not valid for this item

line 76 is this: private void _on_body_entered(Node2D body)

it seems like this might be a Godot issue, though, not a tutorial issue.. almost like the inserted code is supposed to go in the class, but the built in function generated the code outside the class.

@MisoMosiSpy
Copy link
Contributor

MisoMosiSpy commented Apr 2, 2023 via email

@raulsntos
Copy link
Member

I've recently seen some people get confused about this, so I think it would be nice to add a note in the tutorial about this until the bug is fixed.

@immortius
Copy link

For me, the player does not get hidden when colliding with the mob - searching for information about that is what lead me to this thread. I'm not sure if this is problem on my end or not.

I think I've worked this out, the tutorial code for the player's start func in gdscript has $CollisionShape2D.disabled = false, which doesn't do anything according to doco - should be $CollisionShape2D.set_deferred("disabled", false) instead.

@AThousandShips
Copy link
Member

That doesn't hide anything, the hide code is three lines above, the "disabled" just disables the collision shape so it doesn't collide any more, it isn't drawn anyway

@immortius
Copy link

You misunderstand. This is the code to enable the collision for the player on start. It doesn't work, so when the mobs should hit the player they pass straight through and never trigger the hiding of the player.

@Piralein
Copy link
Member

The "Getting Started 2D Section" received multiple bugfix and enhancement PR's since this issue was opened.
As there is no concrete problem mentioned, (except the c# issue, which is tracked in other issues) I will close this issue for now.
If you still have a problem with the tutorial please open a new issue with a detailed description of the problem.

Please feel free to ask for help in any of the offical Community Channels if you are stuck at any point of the tutorial.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:getting started Issues and PRs related to the Getting Started section of the documentation bug
Projects
None yet
Development

No branches or pull requests

10 participants