What's the difference between Godot.Collections.Array and System.Collections.Generic.List?

Godot.Collections.Array is the Variant-backed container that crosses the C++/C# boundary. Use it for engine APIs (signal args, Variant params). For pure C# LINQ, convert via .ToList().

How do I declare a typed Godot Array?

Godot.Collections.Array<T>. The generic version enforces element type and reduces Variant boxing overhead.

Use Godot.Collections.Array for params marked Variant. Pass typed Array<T> where the API accepts a typed list.

Fix: Godot C# Collections.Array vs C# Array

Quick answer: Use Godot.Collections.Array<T> for engine APIs. Convert to List<T> via LINQ for managed code.

Function returns Godot.Collections.Array. You assign to List<Node>. Compile error. Two different beasts.

The Fix

using Godot;
using System.Linq;
using System.Collections.Generic;

// Engine API returns Godot.Collections.Array
Godot.Collections.Array<Node> children = GetChildren();

// Convert for LINQ
List<Node> list = children.ToList();
var filtered = list.Where(n => n.Visible).ToList();

// Pass back to engine
Godot.Collections.Array<Node> back = new(filtered);

Godot.Collections.Array is required where Godot APIs expect Variant. List is for managed-only LINQ work.

Verifying

Compile clean. LINQ runs on List. Result converts back to Godot Array for signal emit. No conversion errors.

“Engine: Godot Array. Code: List. Convert at boundaries.”

Related Issues

For C# Export flags, see flags. For C# signal emit, see signal emit.

Convert at boundaries. Types align.