Skip to content

Instantly share code, notes, and snippets.

Show Gist options
  • Select an option

  • Save TravnikovDev/2514c1bc59767b147fcdd154490ecf49 to your computer and use it in GitHub Desktop.

Select an option

Save TravnikovDev/2514c1bc59767b147fcdd154490ecf49 to your computer and use it in GitHub Desktop.
LinkedIn Post - 2026-03-13 19:31

Most AI game tutorials end the same way - a stiff HTML canvas demo that feels like homework, not play. Ask the model to “build a game” and it grabs Unity or Godot by name, then quietly retreats to JavaScript and a rectangle.

My AI research agent pulled the raw patterns on what actually ships in 2026, and the truth is boring and beautiful: the winners don’t let the bot pick the engine. They pick one stack that lets them feel the game every 30 seconds, then use AI like a loud autocomplete.

Here’s the stack that keeps you in flow, not in docs: Godot 4 with GDScript. Why? Scene tree plus signals, instant reload, real 2D and 3D, exports that don’t break your soul. GDScript reads like Python, compiles fast, and maps one to one with the editor. You live in the Godot editor, not in terminal hell. For assets, Aseprite for sprites and Godot’s TileMap for levels. That’s it. Keep it small, keep it real.

How AI fits: treat it like a junior dev who types fast and forgets names. Feed it your node tree and exact API signatures. Example prompt that works: “I have Player.gd with a KinematicBody2D named Player, a Camera2D child, and an AnimationTree named Anim. Write a function to buffer coyote time and play jump animation. Use move_and_slide and Input actions jump and left-right. Do not invent nodes.” When it hallucinates, paste the error back and force a diff. Never ask for “the game” - ask for one script, one signal, one test.

The dirty secret: feel beats features. Your real loop is run - tweak gravity - jump - smile - ship. Godot’s Remote Inspector, AnimationTree, and Tween let you juice in seconds. Build a tiny playground scene just for tuning. Expose constants, bind them to hotkeys, and record GIFs. AI can’t feel a jump arc. You can.

Catch: if you need AAA lighting or a 500 player netcode, this won’t save you - and you probably aren’t solo anyway. But if you’re one person or a tiny team, this is the freight train. HTML toy MVPs are fine for Medium posts. Fun requires a stack that fights for flow.

My take: In 2026, vibe coding means Godot 4 plus GDScript, with AI as your noisy scripter and you in the editor every 30 seconds. Don’t outsource taste.

What’s your loop time right now - minutes or seconds? 🎮

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment