Use professional AAA practices in your Godot game NOW | Part I

<aside>

The code state at the moment of video ends: https://github.com/Gab-ani/Godot_Universal-Controller-tutorial/tree/episode-1

</aside>

• video description

Architecture of a character

• pep talk

MVC and basic implementation

Player character is a system which controls, simulates, and visualizes a character that is controlled not by an autonomous script, but by a human that actively presses their inputs. It follows pattern: MVC (Model-View-Controller).

<aside>

godot template

</aside>

Godot has an option to use a template for new scripts, and one of these templates is a basic controller for a 3D character. (CharacterBody3D node).

Let's read it: "If input then model; if input then model simulate.". But we don't have any graphics yet. Let's add a capsule to our player. Now we can launch our game and control the character.

The code didn't change, but the visuals are updating. Why is it?

• The capsule is a child node to the character. The term 'child' in this context means that it copies some transformation from the parent.
• So, in the frame update function, there is an invisible instruction: "We moved parent, now move children."

If input happens, then change model parameters, then simulate, then visualize.

⇒ The basic character template already complies with the MVC approach.

Better (OOP)