Godot 3D Gameplay

Implement 3D gameplay as a coordinated physics, camera, and rendering system. Preserve the project's existing architecture and tune from observed behavior rather than replacing working systems with a generic controller.

Inspect Before Editing

Do not write scenes, scripts, or project settings until this inspection is complete.

1. Find project.godot and confirm the project root. Read config/features, the rendering method, physics tick rate, display settings, 3D physics layer names, and existing Input Map actions.
2. Run the project's established Godot executable with --version when available. Match APIs to that exact Godot 4.x release; do not silently upgrade the project or its resource formats.
3. Inspect representative .tscn, .gd, and imported 3D assets. Record scene ownership, node naming, typed GDScript style, signal style, groups, autoloads, folder layout, and whether node references use exported nodes, unique names, or paths.
4. Inspect the current player, camera, level, environment, collision layers and masks, model scale, applied transforms, and input bindings. Check whether meshes or resources are shared before editing them.
5. Identify the target renderer and hardware. A Forward+ desktop scene, a Mobile-renderer game, and a Compatibility project require different lighting and environment choices.
6. Establish a runnable baseline and note existing warnings. Do not attribute pre-existing errors to the requested change.

If the editor version, project feature tag, and requested API disagree, stop and resolve the version mismatch before authoring resources.

Choose the Smallest Suitable Design