* Add note about removing new_game() _ready() in 2D tut
The Start button handles calling `new_game()` so without removing the `_ready()` function that called `new_game()`, the game will automatically start on launch.
* Revise 2d tut new_game() removal to be a reminder
Based on feedback from cbscribe since it's mentioned in the
previous part of the tutorial.
This is required for now, as the DirectionalLight3D's Shadow Max Distance
isn't taken into account when using an orthogonal camera.
This is an engine issue, but since this tutorial is a starting point
for a lot of people, it's important to point out a workaround right here.
- Link to Console support in Godot documentation.
- In the Console support in Godot page, link to the
"Godot and consoles, all you need to know" blog post as it contains
additional context.
- Link to Importing 3D scenes documentation directly to avoid copypasting
the answer.
- Replace uses of "open-source" with "open source" for consistency.
- `_Process` take its delta argument as a double
- Node classes need to be partial
- Use `SignalName.*` instead of `nameof(*)` for signals
- Add a note about how `delta` arguments are doubles
In "Using the animation editor":
"Once you created the animation"
should be:
"Once you've created the animation"
In "Animating the mobs":
"Then open Mob.tscn and open its animation player."
Mob.tscn doesn't have an animation player.
In "Jumping":
"In games, you really want controls to be responsive and giving instant speed boosts like these, while unrealistic, feel great."
should be:
"In games, you really want controls to be responsive and giving instant speed boosts like these, while unrealistic, feels great."
or:
"In games, you really want controls to be responsive and instant speed boosts like these, while unrealistic, feel great."
"Notice that the Y axis is positive upwards. That's unlike 2D, where the Y axis is positive downward."
should be:
"Notice that the Y axis is positive upwards. That's unlike 2D, where the Y axis is positive downwards."
or:
"Notice that the Y axis is positive upward. That's unlike 2D, where the Y axis is positive downward."
Changed code to use new event-style connections; changed
custom signal example to use the new `SignalName` global;
use `double` instead of `float` for `_Process` argument
The last code which would make the tutorial incompatible for 4.0 was this. I ran it locally on my 2D project to ensure it works.
Basically to replace the yield one-shot timer, I used this https://docs.godotengine.org/en/latest/classes/class_scenetreetimer.html
Fixes https://github.com/godotengine/godot-docs/issues/6234
@Calinou Related to this: If I do an upgrade/polish of the 2D tutorial [like I did with 3.0](https://github.com/godotengine/godot-docs/pull/6243) where I upload more **.webp** images and clarify and ref hyperlink here and there, would it be accepted soon, or delayed until after .webp support? Asking because it will take a day or two (I already have the images which is the hard part), and if that upgrade is merged in 4+ months, I would rather schedule my priorities in another way
Yuri Sizov