Godot

Godot is an open source 2D and 3D game engine with a visual editor. Scripting in GDScript or C#.

Website: https://godotengine.org

Tutorials

• 12 Popular Games Made With The Godot Engine
• Basics | Godot Engine Fundamentals - I. Pong
• Enjoyable Game Architecture | Chickensoft — Open Source Tools for Godot and C#
• I Used Godot For 100 Hours, Here’s What I Learned
• Godot Game Development – Crash Course for Beginners
• Game Development Basics in Godot Engine
• How To Structure Your Godot Project (so You Don't Get Confused)

Makefile

The Godot editor runs headless and exports the web build (HTML5/WASM) plus the desktop binaries. Templates are in godot-tools:

• example-makefile.make → Makefile, then set PROJECT
• example-export_presets.cfg → export_presets.cfg (presets: Web, Windows x86, Windows x64, Linux x64, Mac universal)
• in Mac universal set application/bundle_identifier

Two settings that are easy to miss:

# project.godot — the arm64 macOS slice fails to export without this
[rendering]
textures/vram_compression/import_etc2_astc=true

# export_presets.cfg, Web preset — no threads, so the game runs without COOP/COEP headers
variant/thread_support=false

Variables

Targets

make build                     # godot --headless --import, creates .godot/ cache
make run                       # godot --path .
make web                       # export the Web preset into dist/web/
make export VERSION=1.0.0       # web export packed as godotdemo-1.0.0.html.zip
make binaries VERSION=1.0.0     # all desktop targets
make binary-win-x64 VERSION=1.0.0  # one target only
make watch                     # re-import on .gd / .tscn change (needs fswatch)
make clean                     # remove dist/ and .godot/

build is also a quick "does the project load" check. Run it on a fresh checkout before any export.

Desktop notes:

• Godot cross-exports every desktop platform from any host, including the linux CI image.
• macOS is one universal (intel + arm) build. Per-arch export would need custom templates.
• The .app is ad-hoc signed by Godot (codesign/codesign=1); arm64 macOS refuses unsigned binaries.
• Windows and Linux embed the .pck in the executable, so each zip holds a single file.
• Every zip follows the ReleaseAsset convention: one root folder, plus LICENSE and README.md when present.

VS Code

Copy example-tasks.json to .vscode/tasks.json. Tasks: Run (default, Cmd+Shift+B), Edit, Export Web, Make build.

Generated artifacts

Requirements

Local only: make, a Godot 4.x binary with export templates (web + desktop), export_presets.cfg, zip, unzip, and fswatch for watch mode. CI needs nothing in the repo.

Pipeline

Game repos contain no pipeline YAML and no CI make targets. Woodpecker asks the update server, and WarpEngine serves the whole config from /build/config (template lib/warp_engine/ci_templates/godot.yaml.erb).

The repo needs three things:

# .woodpecker.yaml
platform: godot

• metadata.json
• the application_token Woodpecker secret: a WarpEngine ApplicationToken with update + upload scopes
• name: <software> in the marker only when the software name differs from the repo name

Builder images (e.g. godot-builder:4.7.1) come from the update server's ci_platforms config. Preview the served pipeline:

curl "https://teletypegames.org/build/config?platform=godot"

Steps

The builder image is godot-ci (headless editor and the matching export templates) with make, zip, unzip and jq added, so no step runs apt-get. It is built from builder.Dockerfile in godot-tools.

curl -X POST -H "X-Update-Secret: <SECRET>" \
  "https://teletypegames.org/build/publish?name=godotdemo&platform=godot&version=1.0.0"

Result

Web build and four desktop targets, each in its own zip, attached to the release as ReleaseAssets and downloadable from the catalog page. The public game index updates itself.