Question 1

How do I expose a D class as a script in Godot?

Accepted Answer

Inherit from GodotScript with the Godot class (e.g., GodotScript!Button), then annotate properties and methods with @Property and @Method UDAs. The README provides a full example with TestButton showing property hints and signal emission.

Question 2

Godot-D vs C++ for performance in Godot?

Accepted Answer

Both use GDNative for similar native performance, but Godot-D offers D's type safety and metaprogramming, while C++ has broader Godot community support. Godot-D auto-generates bindings, reducing boilerplate compared to manual C++ integration.

Question 3

Is Godot-D compatible with all Godot versions?

Accepted Answer

It supports version checking via GDNative extension properties, but bindings must be generated with the latest GDNative API. The README notes binary compatibility across versions, but runtime checks are needed for newer functions.

Question 4

Can I use existing D libraries with Godot-D?

Accepted Answer

Yes, since Godot-D is a D binding, you can import other D libraries directly, but they must be compiled into the dynamic library. Integration depends on the library's compatibility with Godot's threading and memory model.

Question 5

What happens if Godot updates its API?

Accepted Answer

You may need to regenerate bindings using the API generator for custom builds or new Godot releases. The README explains this under 'Building Godot-D manually', which adds maintenance overhead.

Question 6

How do I debug Godot-D scripts?

Accepted Answer

Debugging relies on D's toolchain (e.g., DMD or LDC debuggers) and Godot's native script logging, as there's no integrated editor debugging like GDScript. Print statements or external D debuggers are typically used.

Godot-D

What is Godot-D?

Overview

Use Cases

Best For

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions