Architecture, Components, and Reusable Systems

Restructure prototypes into maintainable projects using composition, signals, components, state machines, and data-driven systems.

What you will learn

• Choose clear ownership boundaries
• Build reusable components and state machines
• Refactor tangled gameplay without changing behavior

Course syllabus

1. 01
   Why prototype code becomes difficult to maintain
2. 02
   Scene composition
3. 03
   Inheritance versus composition
4. 04
   Clear ownership of behavior
5. 05
   Passing references safely
6. 06
   Signal-based communication
7. 07
   Groups as tags and communication channels
8. 08
   Reusable component scenes
9. 09
   Health components
10. 10
    Interaction components
11. 11
    Cooldown components
12. 12
    State-machine design
13. 13
    State nodes
14. 14
    State classes
15. 15
    Autoloads
16. 16
    When not to use an Autoload
17. 17
    Service nodes
18. 18
    Event-bus advantages and risks
19. 19
    Data-driven systems
20. 20
    Custom Resources as configuration
21. 21
    Project-folder conventions
22. 22
    Script naming
23. 23
    Dependency direction
24. 24
    Refactoring a large script
25. 25
    Documenting a public API
26. 26
    Performing an architecture review