Node References / Scene Hierarchy

[DavidMWright]

Node References

• onready's replaces with exports
• Added categories and groups to exports on vehicle

Reasoning:

• Using exports to reference nodes makes it much easier to swap components out, only needing to select from the scene tree rather than having to retype the full path
• Leverages using the editor to configure the game, rather than hard-coded references in script
• Groups and categories added for additional organization and built in documentation

Split vehicle into it's own scene

• Updated Vehicle script to be it's own class
• Added public function to get position
• Updated vehicle function names to align with Godot style guide

Reasoning:

• Allows for easier editing of the vehicle itself in editor. Won't have to deal with clutter from the main scene
• Splitting Vehicle into it's own scene makes it easier to duplicate and re-use later (multiplayer, NPCs, etc.)
• Defining Vehicle as a class allows for code completion on function calls
• Creating a public function for the position ensures Vehicle has ownership on how this data is passed if the vehicle's physics / control is changed later down the line
• This coding style is not only standard in Godot's docs, but helps prevent programmers from using internal only functions, as Godot does not have real private membership restrictions

Updated view script

• Calls new public Vehicle function to get position over the direct reference

Reasoning:

• Decouples the camera and vehicle

[DavidMWright]

Forgot to mention, all functionality has stayed the same. Purely organizational and structure changes