Godot 4 3D Game Development

Problem Being Solved

3D projects often stall on environment, assets, and validation: a main.tscn without WorldEnvironment or DirectionalLight3D renders black; .gltf imports can fail silently; character control, collision, navigation, and HUD are tightly coupled. This skill constrains Godot 4 + GDScript 3D development into an executable workflow, aiming to take a project from zero to playable, screenshot-verifiable, and ready to export.

How It Works

• Graybox first: use CSGBox3D or primitive geometry to validate layout and feel, then replace it with final models.
• Character controllers: first-person uses CharacterBody3D + Camera3D; third-person swaps in SpringArm3D, adds yaw rotation, and smooths model turning.
• Asset pipeline: prefer .glb, instantiate via preload(...).instantiate(), enable Generate Physics or call create_trimesh_collision() for static collision, and list animations with get_animation_list() before play().
• Levels and materials: repeat kit assets, use MultiMeshInstance3D or GridMap, and configure StandardMaterial3D with albedo, normal, roughness/AO/metallic, with sky-based ambient light.
• AI and validation: bake NavigationRegion3D, structure enemies into patrol, detect, chase, and attack states, and verify each system by capturing get_viewport().get_texture() to check black frames, magenta materials, clipping, and scale.

Boundaries and Notes

This is an engineering workflow, not an art-direction guide. For weak targets, switch to Mobile or Compatibility rendering first; fix model scale in import settings instead of scaling rigidbodies manually; and rebake navigation meshes after level edits.