game-godot-specialist

Create a generic FSM scene with a State base class and child nodes for each state such as Idle, Run, Jump, and Fall, using fully typed GDScript. Each state handles its own enter, exit, and physics update logic, and transitions are driven by signals or explicit state calls.

Use signals for upward communication from leaf nodes to parents, and an EventBus autoload for cross-system communication. Never reference nodes across scene boundaries with long get_node paths, since they break when the scene tree is restructured.

Yes, GDScript supports full static typing for variables, parameters, and return types, and it catches errors at parse time while improving performance. Typed signals with parameter types are supported since Godot 4.2, and typed dictionaries arrived in 4.4.

Use GDExtension only after profiling proves GDScript is the bottleneck, such as tight loops over large datasets or wrapping external C/C++ libraries. Do not use it for general gameplay logic, UI code, or anything that changes frequently during prototyping.

Runtime scene instantiation blocks the main thread and causes frame spikes. Use the built-in Profiler to confirm the bottleneck, then implement object pooling by pre-instantiating scenes and reusing them with visible set to false and process_mode disabled.

Godot's high-level multiplayer API uses ENet with MultiplayerSpawner, MultiplayerSynchronizer, and RPCs, but it does not include rollback netcode or matchmaking. For competitive games you need an addon like GDScript Rollback Networking, and lobbies require Steam or a custom server.