4-space is our convention for indented blocks and should be used consistently.
The only exception is for C++ code which is tab-indented, as the engine code.
For "Let's look is ``process_movement`` next", the following text is
actually referring to "process_input", and even says "and now back to
process_input" later in the same section.
Complete Part05 general phrase corrections
Updated the line 722 in Turret.gd script
Updated a line to be the same as in the current master branch in the Turret.gd script. Before I just pasted my code from the editor following the tutorial from the website witch has an outdated line of code
Removed an empty line inserted by mistake
Part06 partial phrase corrections
Part05 fixed a typo in the corrections
Complete Part06 general phrase corrections
Changed line 488 to be more clear for beginners
I changed the line 488 from "if ray_result:" to "if ray_result != null" so it should be more in line with the code standards and to be more easy to understand by the new users learning how to code.
* FPS Tutorial Part02 general phrase corrections
* FPS Tutorial Part03 minor phrase corrections
Also I have fixed the audio name convention so now the sound will play as intended.
* FPS Tutorial Part04 minor phrase corrections
* Changes to the joypad input handling to include the PS controller
I have made some changes so the tutorial works for both the Xbox controller and the Playstation controller. However I have not managed to find a solution to include them in the same script so now it works just with one of them or the other.
* Changed the wording in the first three parts of the FPS tutorial to
not use "we" when refering to the player.
Changed the name of variables outside of a function to "class variables"
(instead of "global variables", which was less accurate and can be confusing)
Changed the code in RigidBody_hit_test.gd to take bullet rotation into account.
* Changed part 4 and part 5 of the FPS tutorial to not use "we" as often, and not to use "we" for referring to scripts
and other objects.
Changed some of the code to reflect changes in RigidBody_hit_test.gd.
Fixed typos and other small changes.
* Changed part 6 of the FPS tutorial to not use "we" when referring to scripts and other objects.
Fixed a couple minor things in part 2.
Updated all of the zip files to reflect the changed code in RigidBody_hit_test.gd.
* Started remastering first two parts of the FPS tutorial.
Now both parts follow a consistant coding style,
have up to date Zip files for every part.
* Finished the first draft for part 2, and did some edits to part 1.
* Finished writing the first draft for part 3. (Still needs editing)
I also added a blank page for part 5 and added it to the index.
* Updated and fixed a few things in Part 3
* Removed the old part 4 of the FPS tutorial and replaced it with a new part!
(Which would have been part 5 had part 4 not been removed)
* Added part 5 of the FPS tutorial.
Made a few changes to parts 4 and 1.
Added a template/overview of what to write in part 6.
* Finished part 6 of the FPS tutorial.
Now every part of the FPS tutorial is written out!
Made some minor edits to part 5.
* Added all of the zip files for the first three parts of the FPS tutorial.
Updated/Redid all of the pictures for the first three parts as well.
Fixed a few minor issues/inconsistencies in the written material.
* Added all of the zip files for the last three parts of the FPS tutorial.
Updated/Redid all of the pictures for the last three parts as well.
Fixed a few minor issues/inconsistencies in the written material.
Updated the blender files zip.
* Did some editing on parts 3 through 5 on the FPS tutorial.
* Updated script to 3.0 version
Use '$' instead of 'get_node'.
Functions '_process', _physics_process', '_input' and other similar functions will be detected automatically since 3.0.
* The first part covers making a first person character.
* The second part covers adding weapons/guns to the character built in part one.
* The third part adds ammo to the guns and sounds for when the player fires.
blurrred