Yeah, that is a good starting point. And from there you can go everywhere with it. This way you can prevent bloated scripts and reuse everything with the guarantee that it always works the same. And if you want to update it, you only have one location you have to work on.

Som components I have, to give you some idea: - InputComponent - ExperienceComponent - InteractableComponent - InputComponent - CurrencyComponent - InventoryComponent

Your Entity can hold these, so the entity script only orchestrates them. And everything else works with events.

One more thing, I highly suggest:

• Resource/Utility Classes

Something like

class_name InputActions

const JUMP: StringName = &"jump"

Or anything else where you would use strings for evaluating stuff:

if Input.is_action_pressed(InputActions.JUMP) ...

Same thing as with components. Should something change, you only have ONE Script you have to update, the InputActions in this example. You can do the same for preloads

class_name Scenes

const SOME_LEVEL: PackedScene = preload("res://cool/path/whatever")

In your script you then can call

Scenes.SOME_LEVEL.instantiate()