godot-master

name

godot-master

description

Consolidated expert library for professional Godot 4.7+ game and application development. Orchestrates 92 Domain Skills through architectural workflows, anti-pattern catalogs, performance budgets, and Server API patterns. Use when: (1) starting a new Godot project, (2) designing game or app architecture, (3) building entity/component systems, (4) debugging performance or physics issues, (5) choosing between 2D/3D approaches, (6) implementing multiplayer, (7) optimizing draw calls or script time, (8) porting between platforms, (9) migrating from 4.6 to 4.7. Primary entry point for ALL Godot development tasks. Keywords: Godot 4.7, AreaLight3D, HDR, Asset Store, godot-master.

Godot Master: Lead Architect Knowledge Hub

Every section earns its tokens by focusing on Knowledge Delta — the gap between what the base model already knows and what a senior Godot engineer knows from shipping real products.

Library target — Godot 4.7+

All Domain Skill mirrors target Godot 4.7+ (stable). For any engine version upgrade (1.x/2.x legacy → 3→4 → hop-by-hop 4.x), use godot-version-migration — do not treat this hub as a migration changelog.

Cross-cutting 4.7 reminders while routing: AreaLight3D / HDR → 3D Lighting; Asset Store vs Asset Library → export/platform modules; RichTextLabel ImageUnit, input device ID constants, Jolt behavior → migration hub module notes.

---

🧠 Part 1: Expert Thinking Frameworks

"Who Owns What?" — The Architecture Sanity Check

Before writing any system, answer these three questions for EVERY piece of state:

• Who owns the data? (The StatsComponent owns health, NOT the CombatSystem)
• Who is allowed to change it? (Only the owner via a public method like apply_damage())
• Who needs to know it changed? (Anyone listening to the health_changed signal)

If you can't answer all three for every state variable, your architecture has a coupling problem. This is not OOP encapsulation — this is Godot-specific because the signal system IS the enforcement mechanism, not access modifiers.

The Godot "Layer Cake"

Organize every feature into four layers. Signals travel UP, never down:

┌──────────────────────────────┐
│  PRESENTATION (UI / VFX)     │  ← Listens to signals, never owns data
├──────────────────────────────┤
│  LOGIC (State Machines)      │  ← Orchestrates transitions, queries data
├──────────────────────────────┤
│  DATA (Resources / .tres)    │  ← Single source of truth, serializable
├──────────────────────────────┤
│  INFRASTRUCTURE (Autoloads)  │  ← Signal Bus, SaveManager, AudioBus
└──────────────────────────────┘

Critical rule: Presentation MUST NOT modify Data directly. Infrastructure speaks exclusively through signals. If a Label node is calling player.health -= 1, the architecture is broken.

The Signal Bus Tiered Architecture

• Global Bus (Autoload): ONLY for lifecycle events (match_started, player_died, settings_changed). Debugging sprawl is the cost — limit events to < 15.
• Scoped Feature Bus: Each feature folder has its own bus (e.g., CombatBus only for combat nodes). This is the compromise that scales.
• Direct Signals: Parent-child communication WITHIN a single scene. Never across scene boundaries.

🔗 The "Smart Interconnect" Mandate

Expert systems are defined not by their isolation, but by their Payload Synthesis.

• Physics → Performance: PhysicsServer2D and RenderingServer bypass SceneTree node overhead. Use for 1,000+ bullets or particles to achieve O(1) processing.
• Animation → Physics: AnimationTree.get_root_motion_position() converts animation displacement into physics velocity, preventing "foot sliding" in complex movement.
• Data → Reactivity: Serialized Resource objects (like Stats) emit signals when modified, allowing UI to update automatically without tight coupling.
• Asset → Spawning: An O(1) Dictionary-based cache (preloaded during ResourceLoader async phases) prevents I/O hitches when spawning items or enemies.
• Mobile → Visuals: Prevent runtime frame-hitches by instantiating hidden effects during loading screens to force GPU shader pipeline compilation.
• Networking → Bandwidth: Use bit-packing into PackedByteArray for synchronization instead of JSON/Strings to keep packets under 100 bytes.
• Genre Synthesis:
  • Shooter: strictly use intersect_ray() (direct space state) over RayCast3D nodes for 100x performance.
  • RPG: Damage follows base * pow(scaling, level) to sustain end-game progression.
  • RTS: Moves groups based on their Center of Mass with Relative Offset to preserve formation integrity.
  • Metroidvania: Uses ResourceLoader.load_threaded_request() for seamless room swaps.
  • Platformer: Mandatory Jump Buffering (~0.15s) and Coyote Time for professional feel.
  • Simulation: Tick Manager batch processing; avoid per-entity _process to sustain thousands of units.
  • Romance: Multi-Axial Affection (Attraction, Trust, Comfort) to map complex narrative branching.
  • Architecture: Signal Architecture strictly follows Signal Up, Call Down to eliminate circular scene coupling.

---

🧭 Part 2: Architectural Decision Frameworks

The Master Decision Matrix

Scenario	Strategy	MANDATORY Skill Chain	Trade-off
Rapid Prototype	Event-Driven Mono	READ: Foundations → Autoloads. Do NOT load genre or platform refs.	Fast start, spaghetti risk
Complex RPG	Component-Driven	READ: Composition → States → RPG Stats. Do NOT load multiplayer or platform refs.	Heavy setup, infinite scaling
Massive Open World	Resource-Streaming	READ: Open World → Save/Load. Also load Performance.	Complex I/O, float precision jitter past 10K units
Server-Auth Multi	Deterministic	READ: Server Arch → Multiplayer. Do NOT load single-player genre refs.	High latency, anti-cheat secure
Mobile/Web Port	Adaptive-Responsive	READ: UI Containers → Adapt Desk→Mobile → Platform Mobile.	UI complexity, broad reach
Application / Tool	App-Composition	READ: App Composition → Theming. Do NOT load game-specific refs.

The "When NOT to Use a Node" Decision

One of the most impactful expert-only decisions. The Godot docs explicitly say "avoid using nodes for everything":

Type	When to Use	Cost	Expert Use Case
Object	Custom data structures, manual memory management	Lightest. Must call .free() manually.	Custom spatial hash maps, ECS-like data stores
RefCounted	Transient data packets, logic objects that auto-delete	Auto-deleted when no refs remain.	DamageRequest, PathQuery, AbilityEffect — logic packets that don't need the scene tree
Resource	Serializable data with Inspector support	Slightly heavier than RefCounted. Handles .tres I/O.	ItemData, EnemyStats, DialogueLine — any data a designer should edit in Inspector
Node	Needs _process/_physics_process, needs to live in the scene tree	Heaviest — SceneTree overhead per node.	Only for entities that need per-frame updates or spatial transforms

The expert pattern: Use RefCounted subclasses for all logic packets and data containers. Reserve Node for things that must exist in the spatial tree. This halves scene tree overhead for complex systems.

---

🔧 Part 3: Core Workflows

Workflow 1: Professional Scaffolding

From empty project to production-ready container.

MANDATORY — READ ENTIRE FILE: Foundations

1. Organize by Feature (/features/player/, /features/combat/), not by class type. A player/ folder contains the scene, script, resources, and tests for the player.
2. READ: Signal Architecture — Create GlobalSignalBus autoload with < 15 events.
3. READ: GDScript Mastery — Enable untyped_declaration warning in Project Settings → GDScript → Debugging.
4. Apply Project Templates for base .gitignore, export presets, and input map.
5. Use Builder (create_scene.py, add_node.py, save_scene.py) to generate scene hierarchies programmatically via the Godot CLI.

[!CAUTION] Workflow 1 NEVER List

• NEVER use res:// paths in logic scripts. Use @export_file or @export_dir to ensure resources remain valid when moved.
• NEVER initialize children in _init(). The scene tree isn't ready. Use _ready() or @onready.
• NEVER keep "Default" project settings for Physics Ticks. Set to 60 for consistency, or use Engine.physics_ticks_per_second for adaptive logic.
• NEVER use print() in _process() for debugging; use the Debugger or push_error() to avoid frame-time spikes.

Do NOT load combat, multiplayer, genre, or platform references during scaffolding.

Workflow 2: Entity Orchestration

Building modular, testable characters.

MANDATORY Chain — READ ALL: Composition → State Machine → CharacterBody2D or Physics 3D → Animation Tree Do NOT load UI, Audio, or Save/Load references for entity work.

• The State Machine queries an InputComponent, never handles input directly. This allows AI/Player swap with zero refactoring.
• The State Machine ONLY handles transitions. Logic belongs in Components. MoveState tells MoveComponent to act, not the other way around.
• Every entity MUST pass the F6 test: pressing "Run Current Scene" (F6) must work without crashing. If it crashes, your entity has scene-external dependencies.

[!CAUTION] Workflow 2 NEVER List

• NEVER call parent.do_thing(). If the parent changes, the entity breaks. Emit a signal request_action instead.
• NEVER use _process for movement. Use _physics_process to avoid jitter on variable-refresh-rate monitors.
• NEVER hardcode animation names. Use a StringName constant or a Resource map to enable easy renaming in AnimationPlayer.
• NEVER use get_node() with absolute paths. Use %UniqueName to survive tree refactoring.

Workflow 3: Data-Driven Systems

Connecting Combat, Inventory, Stats through Resources.

MANDATORY Chain — READ ALL: Resource Patterns → RPG Stats → Combat → Inventory

• Create ONE ItemData.gd extending Resource. Instantiate it as 100 .tres files instead of 100 scripts.
• The HUD NEVER references the Player directly. It listens for player_health_changed on the Signal Bus.
• Enable "Local to Scene" on ALL @export Resource variables, or call resource.duplicate() in _ready(). Failure to do this is Bug #1 in Part 8.

[!CAUTION] Workflow 3 NEVER List

• NEVER pass Node references in a Signal Bus. Objects get freed; RIDs or IDs are safer for long-term tracking.
• NEVER modify a .tres file at runtime via code (it modifies the disk file). Always .duplicate() before modifying.
• NEVER use Array for high-frequency search. Use Dictionary with StringName keys for O(1) lookups.
• NEVER use float for item counts or precise resource tracking; use int and scale for display.

Workflow 4: Persistence Pipeline

MANDATORY: Autoload Architecture → Save/Load → Scene Management

• Use dictionary-mapped serialization. Old save files MUST not corrupt when new fields are added — use .get("key", default_value).
• For procedural worlds: save the Seed plus a Delta-List of modifications, not the entire map. A 100MB world becomes a 50KB save.

[!CAUTION] Workflow 4 NEVER List

• NEVER save whole Object or Node instances. They contain transient pointers. Extract data into a Dictionary or custom Resource.
• NEVER use JSON for data that needs strict typing (e.g., Vector2). Use var_to_bytes or ConfigFile for structured Godot types.
• NEVER block the main thread for auto-saves. Use a Thread or WorkerThreadPool to serialize large dictionaries.
• NEVER save to res:// in an exported project; strictly use user:// for persistent data.

Workflow 5: Performance Optimization

MANDATORY: Debugging/Profiling → Performance Optimization

Diagnosis-first approach (NEVER optimize blindly):

1. High Script Time → Profile with built-in Profiler. Check if _process is being called on hundreds of nodes. Move to single-manager pattern or Server APIs (see Part 6).
2. High Draw Calls → Use MultiMeshInstance for repetitive geometry. Batch materials with ORM textures.
3. Physics Stutter → Simplify collisions to primitive shapes. Load 2D Physics or 3D Physics. Check if _process is used instead of _physics_process for movement.
4. VRAM Overuse → Switch textures to VRAM Compression (BPTC/S3TC for desktop, ETC2 for mobile). Never ship raw PNG.
5. Intermittent Frame Spikes → Usually GC pass, synchronous load(), or NavigationServer recalculation. Use ResourceLoader.load_threaded_request().

[!CAUTION] Workflow 5 NEVER List

• NEVER use get_nodes_in_group() inside _process. It's an O(n) operation every frame. Cache the array in _ready().
• NEVER use Area2D signals for "Stay" logic. Use get_overlapping_bodies() periodically or a manager-level PhysicsServer check.
• NEVER optimize before profiling. A 1ms script is irrelevant if you have 2000 draw calls killing the GPU.
• NEVER use load() in hot paths; strictly preload or use ResourceLoader for async loading.

Workflow 6: Cross-Platform Adaptation

MANDATORY: Input Handling → Adapt Desktop→Mobile → Platform Mobile Also read: Platform Desktop, Platform Web, Platform Console, Platform VR as needed.

• Use an InputManager autoload that translates all input types into normalized actions. NEVER read Input.is_key_pressed() directly — it blocks controller and touch support.
• Mobile touch targets: minimum 44px physical size. Use MarginContainer with Safe Area logic for notch/cutout devices.
• Web exports: Godot's AudioServer requires user interaction before first play (browser policy). Handle this with a "Click to Start" screen.

[!CAUTION] Workflow 6 NEVER List

• NEVER use OS.get_name() for feature detection. Use OS.has_feature("mobile") or custom feature tags to handle subsets like "SteamDeck."
• NEVER assume a specific aspect ratio. Always use Expand or Keep Aspect in combinations with Anchor nodes.
• NEVER use desktop-only shaders (e.g., complex depth sampling) on Mobile/Web without a GLES3/Compatibility secondary path.
• NEVER ignore physical_keycode for desktop builds; it ensures keyboard layouts (AZERTY/QWERTY) don't break movement.

• NEVER pass unsanitized strings to JavaScriptBridge.eval() — Prevents script injection in web builds. Use a sanitize_js_string() helper.

Workflow 7: Procedural Generation

MANDATORY: Procedural Gen → Tilemap Mastery or 3D World Building → Navigation

• ALWAYS use FastNoiseLite resource with a fixed seed for deterministic generation.
• Never bake NavMesh on the main thread. Use NavigationServer3D.parse_source_geometry_data() + NavigationServer3D.bake_from_source_geometry_data_async().
• For infinite worlds: chunk loading MUST happen on a background thread using WorkerThreadPool. Build the scene chunk off-tree, then add_child.call_deferred() on the main thread.

[!CAUTION] Workflow 7 NEVER List

• NEVER instantiate nodes for "Background" noise. Use MultiMeshInstance or draw loops in _draw for thousands of small details.
• NEVER regenerate the entire map for one change. Use a "Dirty Chunk" system to only update what exactly changed.
• NEVER place collisions on the same frame as mesh generation if using concave_polygon_shape. It stalls the physics thread.
• NEVER perform pathfinding queries every frame for all units. Use a NavigationAgent with target_position updates on a timer.

Workflow 8: Multiplayer Architecture

MANDATORY — READ: Single→Multiplayer → Networking → Server Arch Do NOT load single-player genre blueprints.

• Client sends Input, Server calculates Outcome. The Client NEVER determines damage, position deltas, or inventory changes.
• Use Client-Side Prediction with server reconciliation: predict locally, correct from server snapshot. Hides up to ~150ms of latency.
• MultiplayerSpawner handles replication in Godot 4. Configure it per scene, not globally.

[!CAUTION] Workflow 8 NEVER List

• NEVER trust rpc_id(1, ...) (Client to Server) without validation. A hacked client can send damage = 999999.
• NEVER replicate _process transforms directly. Replicate Input vector and simulate movement on both sides.
• NEVER use TCP for high-frequency packets (movement). Use UDP / ENet and handle dropped packets with interpolation.
• NEVER synchronize every projectile; use Client-Side Prediction for visuals and only RPC the "Fire" event.

• ReflectionProbe vs VoxelGI vs SDFGI: Probes are cheap/static, VoxelGI is medium/baked, SDFGI is expensive/dynamic. Choose based on your platform budget (see Part 5).

Workflow 9: Responsive UI & Expert Theming (Audit Verified)

MANDATORY Chain: UI Containers → UI Theming → Rich Text → Tweening

1. The F6 Principle: Every UI scene must be testable in isolation. Use MOUSE_FILTER_STOP only on the background, PASS on children.
2. Breathing Room: Use add_theme_constant_override("separation", X) over manual padding.
3. Adaptive Scaling: Use responsive_layout_builder.gd for breakpoint-aware mobile/desktop switching.
4. Lifecycle Safety: Never scroll to a new child on the same frame. await get_tree().process_frame before modifying scroll_vertical.
5. Data Integration: Use Resource-to-UI binding; UI nodes MUST be stateless projection layers.

[!CAUTION] Workflow 9 NEVER List

• NEVER use absolute pixel offsets. UI becomes unreadable on 4K or tiny mobile screens. Use Container sizing.
• NEVER deep-nest MarginContainers. It makes the Inspector unusable. Use a single Theme resource for project-wide margins.
• NEVER connect UI buttons to gameplay logic directly. UI sends "Signal", PlayerController listens. This prevents UI-deletion crashes.
• NEVER use _process() to move a UI element to a target. Use a Tween to avoid stuttering and frame-rate dependence.
• NEVER leave mouse_filter as STOP on transparent containers; it "eats" clicks for everything behind it.

• NEVER use dynamic load() on paths without validating the res:// prefix and safe extension (.tres, .res, .theme) — Prevents arbitrary code/resource execution.

Workflow 10: Cinematic Lighting & VFX (Audit Verified)

MANDATORY Chain: 3D Lighting → Particles → 3D Materials → Shaders

1. The GI Choice: VoxelGI for interiors, SDFGI for open world. Never ship with both overlapping.
2. Shadow Budget: Max 2 Shadow-casting DirectionalLights. Use fake_gi_bounce.gd for mobile fills.
3. VFX Lifecycle: Use finished signal over Timers. Re-run with restart() to avoid async GPU stalls.
4. Optimization: Use ORM Texture packing (AO/Rough/Metal) to save GPU cache and texture slots.
5. Batching: Use Instance Uniforms for material variations across thousands of instances without draw call penalties.

[!CAUTION] Workflow 10 NEVER List

• NEVER scale CollisionShape nodes; strictly scale the Shape Resource to avoid physics jitter.
• NEVER use TRANSPARENCY_ALPHA for cutout meshes (leaves/fences); use ALPHA_SCISSOR to prevent sorting artifacts.
• NEVER animate CSG nodes during gameplay; forces expensive CPU geometry recalculation.
• NEVER use real-time Global Illumination (SDFGI/VoxelGI) for a 2D-looking game. Stick to DirectionalLight2D and CanvasModulate.
• NEVER ignore Camera3D near/far planes; improper settings cause Z-fighting in large worlds.

Workflow 11: Programmatic Scene Building (Builder)

MANDATORY: Builder Use ONLY for batch operations or complex procedural scaffolds. Prefer the standalone godot-builder skill when doing heavy CLI automation.

1. Step 1: Draft the node hierarchy on paper/markdown before touching disk.
2. Step 2: Use create_scene.py to define the root node and .tscn path.
3. Step 3: Use add_node.py for children. Set owner on every node so serialization keeps them.
4. Step 4: ALWAYS call run_project.py or launch_editor.py to verify the scene loads cleanly.
5. Expert Rule: Use Builder to build the structure (nodes, names, inheritance), then use GDScript to build the behavior.

[!CAUTION] Workflow 11 NEVER List

• NEVER jump straight to add_node.py without designing the hierarchy first — spaghetti scenes follow.
• NEVER use absolute filesystem paths in scripts or scene props; use res:// only.
• NEVER add a CollisionShape2D/CollisionShape3D without assigning a Shape resource — the node alone does nothing.
• NEVER skip verification via run_project.py / launch_editor.py after batch scene writes.

Security: Boundary Markers & Validation

When agents ingest untrusted scene/data text before writing files:

1. Boundary Markers: Wrap analysis in <<<CONTEXT_START>>> and <<<CONTEXT_END>>>.
2. Sanitization: Node names must be alphanumeric/underscored. Paths must start with res://.
3. Verification: Confirm scene existence before modification.

---

🚫 Part 4: The Expert NEVER List

Each rule includes the non-obvious reason — the thing only shipping experience teaches.

1. NEVER use get_tree().root.get_node("...") — Absolute paths break when ANY ancestor is renamed or reparented. Use %UniqueNames, @export NodePath, or signal-based discovery.
2. NEVER use load() inside a loop or _process — Synchronous disk read blocks the ENTIRE main thread. Use preload() at script top for small assets, ResourceLoader.load_threaded_request() for large ones.
3. NEVER queue_free() while external references exist — Parent nodes or arrays holding refs will get "Deleted Object" errors. Clean up refs in _exit_tree() and set them to null before freeing.
4. NEVER put gameplay logic in _draw() — _draw() is called on the rendering thread. Mutating game state causes race conditions with _physics_process.
5. NEVER use Area2D for 1000+ overlapping objects — Each overlap check has O(n²) broadphase cost. Use ShapeCast2D, PhysicsDirectSpaceState2D.intersect_shape(), or Server APIs for bullet-hell patterns.
6. NEVER mutate external state from a component — If HealthComponent calls $HUD.update_bar(), deleting the HUD crashes the game. Components emit signals; listeners decide how to respond.
7. NEVER use await in _physics_process — await yields execution, meaning the physics step skips frames. Move async operations to a separate method triggered by a signal.
8. NEVER use String keys in hot-path dictionary lookups — String hashing is O(n). Use StringName (&"key") for O(1) pointer comparisons, or integer enums.
9. NEVER store Callable references to freed objects — Crashes silently or throws errors. Disconnect signals in _exit_tree() or use CONNECT_ONE_SHOT.
10. NEVER use _process for 1000+ entities — Each _process call has per-node SceneTree overhead. Use a single Manager._process that iterates an array of data structs (Data-Oriented pattern), or use Server APIs directly.

---

📊 Part 5: Performance Budgets (Concrete Numbers)

Metric	Mobile Target	Desktop Target	Expert Note
Draw Calls	< 100 (2D), < 200 (3D)	< 500	MultiMeshInstance for foliage/debris
Triangle Count	< 100K visible	< 1M visible	LOD system mandatory above 500K
Texture VRAM	< 512MB	< 2GB	VRAM Compression: ETC2 (mobile), BPTC (desktop)
Script Time	< 4ms per frame	< 8ms per frame	Move hot loops to Server APIs
Physics Bodies	< 200 active	< 1000 active	Use PhysicsServer direct API for mass sim
Particles	< 2000 total	< 10000 total	GPU particles, set visibility_aabb manually
Audio Buses	< 8 simultaneous	< 32 simultaneous	Use Audio Systems bus routing
Save File Size	< 1MB	< 50MB	Seed + Delta pattern for procedural worlds
Scene Load Time	< 500ms	< 2s	ResourceLoader.load_threaded_request()

---

⚙️ Part 6: Server APIs — The Expert Performance Escape Hatch

This is knowledge most Godot developers never learn. When the scene tree becomes a bottleneck, bypass it entirely using Godot's low-level Server APIs.

When to Drop to Server APIs

• 10K+ rendered instances (sprites, meshes): Use RenderingServer with RIDs instead of Sprite2D/MeshInstance3D nodes.
• Bullet-hell / particle systems with script interaction: Use PhysicsServer2D body creation instead of Area2D nodes.
• Mass physics simulation: Use PhysicsServer3D directly for ragdoll fields, debris, or fluid-like simulations.

📊 Performance Comparison: SceneTree vs. Server APIs

Bypassing the SceneTree eliminates the heavy CPU overhead of node lifecycle management, signal propagation, and virtual function overhead (like _process).

Metric	SceneTree (Nodes)	Server APIs (RIDs)	Expert Rationale
Object Limit	~1,000 - 5,000	50,000+	SceneTree has O(n) traversal costs; Servers use O(1) direct RID handles.
Memory Overhead	~2KB - 10KB per Node	< 200 bytes per RID	Nodes carry tree state, signals, and inspector metadata. RIDs are opaque 24-byte handles.
CPU Time	High (Virtual calls)	Minimal (Direct API)	Nodes must call _process for every instance. Servers batch operations in C++.
Threading	Main Thread Only	Inherently Thread-Safe	Most Server APIs are thread-safe (must be enabled in Project Settings).
Garbage Collection	Automatic (RefCounted)	Manual (Alloc/Free)	Servers require manual lifecycle management (RID creation/deletion).

Expert Note: Using RIDs allows managing raw data and interacting directly with engine core logic. This is the primary "escape hatch" for bullet-hells, massive foliage, or complex procedural simulations where SceneTree housekeeping becomes the bottleneck.

The RID Pattern (Expert)

Server APIs communicate through RID (Resource ID) — opaque handles to server-side objects. Critical rules:

# Create server-side canvas item (NO node overhead)
var ci_rid := RenderingServer.canvas_item_create()
RenderingServer.canvas_item_set_parent(ci_rid, get_canvas_item())

# CRITICAL: Keep resource references alive. RIDs don't count as references.
# If the Texture resource is GC'd, the RID becomes invalid silently.
var texture: Texture2D = preload("res://sprite.png")
RenderingServer.canvas_item_add_texture_rect(ci_rid, Rect2(-texture.get_size() / 2, texture.get_size()), texture)

Threading with Servers

• The scene tree is NOT thread-safe. But Server APIs (RenderingServer, PhysicsServer) ARE thread-safe when enabled in Project Settings.
• You CAN build scene chunks (instantiate + add_child) on a worker thread, but MUST use add_child.call_deferred() to attach them to the live tree.
• GDScript Dictionaries/Arrays: reads and writes across threads are safe, but resizing (append, erase, resize) requires a Mutex.
• NEVER load the same Resource from multiple threads simultaneously — use one loading thread.

---

🧩 Part 7: Expert Code Patterns

Expert implementations of common architectural and gameplay systems.

• Component Registry: Centralized dictionary-based component retrieval.
• Safe Signal Handler: Preventing crashes on freed object references.
• Async Resource Loader: Threaded asset ingestion.
• State Machine Transition Guard: Validating state changes.
• Thread-Safe Chunk Loader: Low-level server-api construction.
• Vision Cone Detection: Expert NPC vision with dot products and raycasts.
• Sound Propagation System: Acoustic occlusion logic.
• Stealth Hiding Logic: Global visibility and concealment management.

---

🔥 Part 8: Godot 4.x Gotchas (Veteran-Only)

1. @export Resources are shared by default: Multiple scene instances ALL share the same Resource. Use resource.duplicate() in _ready() or enable "Local to Scene" checkbox. This is the #1 most reported Godot 4 bug by newcomers.
2. Signal syntax silently fails: connect("signal_name", target, "method") (Godot 3 syntax) compiles but does nothing in Godot 4. Must use signal_name.connect(callable).
3. Tween is no longer a Node: Created via create_tween(), bound to the creating node's lifetime. If that node is freed, the Tween dies. Use get_tree().create_tween() for persistent tweens.
4. PhysicsBody layers vs masks: collision_layer = "what I am". collision_mask = "what I scan for". Setting both to the same value causes self-collision or missed detections.
5. StringName vs String in hot paths: StringName (&"key") uses pointer comparison (O(1)). String uses character comparison (O(n)). Always use StringName for dictionary keys in _process.
6. @onready timing: Runs AFTER _init() but DURING _ready(). If you need constructor-time setup, use _init(). If you need tree access, use @onready or _ready(). Mixing them causes nulls.
7. Server query stalls: Calling RenderingServer or PhysicsServer getter functions in _process forces a synchronous pipeline flush. These servers run async — requesting data from them stalls the entire pipeline until the server catches up.
8. move_and_slide() API change: Returns bool (whether collision occurred). Velocity is now a property, not a parameter. velocity = dir * speed before calling move_and_slide().

---

📂 Part 9: Module Directory (99 Blueprints)

[!IMPORTANT] Load ONLY the modules needed for your current workflow. Use the Decision Matrix in Part 2 to determine which chain to follow.

Architecture & Foundation

Foundations | Composition | App Composition | Signals | Autoloads | States | Resources | Templates | Analyst | Auditor | Builder

Version upgrades (external hub): godot-version-migration — full-history router (legacy eras, 3→4 bridge, 4.0→4.7 hops); not mirrored here.

GDScript & Testing

GDScript Mastery | Testing Patterns | Debugging/Profiling | Performance Optimization

2D Systems

2D Animation | 2D Physics | Tilemaps | Animation Player | Animation Tree | CharacterBody2D | Particles | Tweening | Shader Basics | Camera Systems

3D Systems

3D Lighting | 3D Materials | 3D World Building | Physics 3D | Navigation/Pathfinding | Procedural Generation | Raycasting

Gameplay Mechanics

Abilities | Combat | Dialogue | Economy | Inventory | Questing | RPG Stats | Turn System | Audio | Scene Transitions | Save/Load | Secrets | Collections | Waves | Harvesting | Time Trials | Revival | Monte Carlo Balancer

UI & UX

UI Containers | Rich Text | Theming | Input Handling | Seasonal Theming | Agent Vision

Connectivity & Platforms

Multiplayer | Server Logic | Export Builds | Desktop | Mobile | Web | Console | VR

Adaptation Guides

• Adapting Desktop -> Mobile
• Adapting Mobile -> Desktop
• Adapting Single -> Multiplayer
• Adapting 2D -> 3D
• Adapting 3D -> 2D

Genre Blueprints (Exhaustive)

Action RPG | Shooter | Shooter FPS | RTS | MOBA | Rogue-like | Survival | Open World | Metroidvania | Platformer | Fighting | Stealth | Sandbox | Horror | Puzzle | Racing | Rhythm | Sports | Battle Royale | Card Game | Visual Novel | Romance | Simulation | Tower Defense | Idle Clicker | Party | Educational

---

🐛 Part 10: Expert Diagnostic Patterns

The "Invisible Node" Bug

Symptom: Node exists in tree but isn't rendering. Expert diagnosis chain: visible property → z_index → parent CanvasLayer wrong layer → modulate.a == 0 → behind camera's near clip (3D) → SubViewport.render_target_update_mode not set → CanvasItem not in any CanvasLayer (renders behind everything).

The "Input Eaten" Bug

Symptom: Clicks or key presses ignored intermittently. Expert diagnosis: Another Control node with mouse_filter = STOP overlapping the target. Or, modal PopupMenu consuming unhandled input. Or, _unhandled_input() in another script calling get_viewport().set_input_as_handled().

The "Physics Jitter" Bug

Symptom: Character vibrates at surface contacts. Expert diagnosis: Safe Margin too large. Or, _process used for movement instead of _physics_process (interpolation mismatch). Or, collision shapes overlap at spawn (push each other apart permanently).

The "Memory Leak"

Symptom: RAM grows steadily during play. Expert diagnosis: queue_free() called but reference held in Array/Dictionary. Or, signals connected with CONNECT_REFERENCE_COUNTED without cleanup. Use Profiler "Objects" tab to find orphaned instances. Search for Node instances without a parent.

The "Frame Spike"

Symptom: Smooth FPS but periodic drops. Expert diagnosis: GDScript GC pass. Or, synchronous load() for a large resource. Or, NavigationServer rebaking. Or, Server API query stall (requesting data from RenderingServer in _process). Profile with built-in Profiler → look for function-level spikes.

---

🚀 Part 11: Quick Start — Unity (C#) to Godot (GDScript)

Mental model shifts for senior engineers transitioning from the Unity ecosystem.

1. Nodes vs. GameObjects & Components

In Unity, a GameObject is a container for Components. In Godot, everything is a Node.

• Unity: GameObject + Transform + MeshFilter + Script.
• Godot: A MeshInstance3D node (which is a Transform and a Mesh) with a script attached.
• Expert Shift: Use Node composition. If you need a "Health Component", add a Node or Area3D as a child called "Health". Use RefCounted for logic-only components to save memory.

2. Scenes are Nested Prefabs

Godot doesn't have "Prefabs" because every scene is a prefab.

• You can instantiate a scene inside another scene, infinitely.
• Expert Shift: Every reusable system (Player, Enemy, UI Button) should be its own .tscn file. This promotes "Post-Order Traversal" (children are ready before parents).

3. Signals vs. Events/Actions

Godot's Signal system is a native implementation of the Observer pattern.

• Unity: event Action OnDeath;.
• Godot: signal died.
• Expert Shift: Signals are first-class citizens. They are visible in the Inspector and can be connected dynamically or via the editor. Use the "Signal Bus" pattern (Autoload) for global events to mimic Unity's Singleton managers.

4. Scripts as Class Extensions

When you attach a script to a node, that script is the node.

• Unity: GetComponent<MyScript>().
• Godot: The script extends the node's class (e.g., extends CharacterBody3D).
• Expert Shift: Use Typed GDScript (var x: int = 5) to gain compilation speedups and editor completion. Typed GDScript uses optimized opcodes when types are known at compile time.

5. Memory Management: No Garbage Collection stalls

Unlike Unity's C# which can have "GC spikes", GDScript uses Reference Counting.

• Expert Shift: Objects are freed the moment they are no longer referenced. This provides deterministic performance and avoids the intermittent "stutters" common in large Unity projects.

6. StringNames & Performance

Unity uses int or Enum for performance. Godot uses StringName.

• Expert Shift: Use &"name" for constant-time (O(1)) pointer comparisons in dictionaries and signal lookups.

---

Reference

• Godot 4.7 Official Documentation
• Godot 4.7 Migration Guide
• Godot Engine GitHub Discussions