The C# alternative for the Godot code, was using a non existing `PlaybackSpeed` property instead of the same property used by the GDScript alternative: speed_scale (SpeedScale in C#).
As a result the C# alternative would not run, while the GDScript alternative worked just fine.
I followed the entire 3d tutorial with godot 4.x and the changes to the
docs repo were small. The largest change was needing to replace the
outdated links to the old starter project with assets. Since there was
no longer a non-complete starter project, I made a PR to
godot-docs-project-starters. That would need to be reviewed and merged
first before the link to the new starter project zip file would be
valid.
New starter/assets project PR:
https://github.com/godotengine/godot-docs-project-starters/pull/9
Better steer people to create MobPath as a child of Main, so that they
don't accidentally create it as a child of StartPosition (the previously
selected item), which has a transform.
If they happen to re-parent to Main after creating the Path2D as a child
of StartPosition, they end up with a transform on the Path2D, which
breaks the expected spawn point of mobs.
See https://github.com/godotengine/godot-docs/pull/10698#issuecomment-2664002759.
Closes#6372, closes#10698.
- Change all links to '_doc' anchors instead of 'toc's.
- Move 'doc_c_sharp' and 'doc_gdscript' to the index pages.
- Add 'doc_gdscript_reference' anchor.
- Update all existing links to point to the right place,
updating grammar if needed.
* Updating "Run Current Scene" usage for consistency and adding note distinguishing Play Current Scene from Run Project
Corrects inconsistent usage of "Play Scene" to refer to "Run Current Scene" button (F6). Also adds a note distinguishing between the two as this is the first occurrence of usage in the docs and may help address concerns discussed here
Per suggestion from @tetrapod00, removing the newly-added note and instead adding clarification of which button to press to the action step for initiating play.
When following the tutorial instructions I reached the point of running the scene to test the button that starts and stops movement of the Godot icon. After following the instructions explicitly, you will have the node_2d scene selected, but you are currently instructed to "run the scene". If you choose to do so by pressing F5 or the play button in the UI, the default scene will run, which does not contain the button.
Added some clarifying text to help make the transition from double clicking Ball.tscn to editing the specific Ball node itself. Now it is clear to first click within the left nav before moving over to the inspector tab.
