scripting-language-selection

name	scripting-language-selection
description	Core decision framework for choosing GDScript, C#, or mixed-language architecture in Godot based on team and runtime constraints.
tier	core
godot_version	4.6+
doc_anchors	["godot-docs/getting_started/step_by_step/scripting_languages.rst","godot-docs/tutorials/scripting/gdscript/gdscript_basics.rst","godot-docs/tutorials/scripting/c_sharp/index.rst"]
tags	["architecture","scripting","language-choice"]
depends_on	["godot-skills/godot-foundations/foundation-godot-version-doc-alignment/SKILL.md"]

Scripting Language Selection

Use When

• Starting a new Godot project or subsystem.
• Reconsidering language choice due to performance, tooling, or team composition changes.
• Defining boundaries in a mixed GDScript/C# codebase.

Outcomes

• Documented language choice with explicit rationale.
• Clear boundary rules for where each language is allowed.
• Validation plan for build/runtime workflow under the selected language model.

Required Rules

• Base choice on project constraints, not preference alone.
• Keep one authoritative rule for cross-language boundaries if mixed mode is used.
• Ensure all selected language toolchains are supported in CI/editor workflows.
• Revisit choice only when constraints change measurably.

Workflow

1. Capture constraints: team proficiency, expected scale, tooling, and target platforms.
2. Select baseline: GDScript-only, C#-heavy, or mixed.
3. Define boundaries (for mixed): gameplay hot paths, tooling scripts, and integration seams.
4. Validate editor/runtime flow on a minimal slice with the chosen setup.
5. Record decision and trigger criteria for future reevaluation.

Validation

• Create minimal scripts in selected language(s) and confirm they execute in-editor.
• Run diagnostics/build checks for selected language toolchain with no blocking errors.
• Confirm source control and CI can reproduce local script compilation and execution.

Failure Modes

• Mixed-language code without explicit boundary rules leads to ownership drift.
• Choosing C# without validating .NET toolchain availability across contributors/CI.
• Choosing one language for all layers despite clear mismatch with team/tool constraints.

Local Doc Anchors

• godot-docs/getting_started/step_by_step/scripting_languages.rst
• godot-docs/tutorials/scripting/gdscript/gdscript_basics.rst
• godot-docs/tutorials/scripting/c_sharp/index.rst