Dustcrawl Agentic Digest

Agentic Digest · Weekend Edition · · Issue #45

Pick the dock

Cursor still cannot see the scene tree. Four tools beat ten logos. Studios are picking productivity docks while the mood sours.

Dictionary

scene-blind

/siːn blaɪnd/ · adj.

An assistant that writes GDScript from a chat window that cannot see the scene tree, the viewport, or the error dock. A perfect jump script for a node that was never parented is scene-blind. A dock that moves nodes and screenshots Play is not.

Example Cursor refactored the player. The player was a comment. The tree did not care.

Wire, filtered

News

  • Cursor still cannot see the tree

    Ziva’s May 2026 Godot roundup is a map, not a shopping list. Eleven tools: six in-editor plugins, three MCP bridges, one AI-native engine, one external IDE. Cursor plus a .cursorrules file is strong at GDScript text and blind to the scene tree, the error dock, and the running game. Copilot ghost-text is narrower still. MCP (the dlight Godot AI plugin and its cousins) is for people who already live in Claude Code or Cursor and want the editor marshaled. In-editor agents change nodes through the editor API instead of patching .tscn by hand. LLMs asked to name the field still invent a five-tool shortlist and misquote who can touch the tree. The mistake is enabling all eleven so you will not miss a dock.

    Pick the loop that can hit Play and see the result. Uninstall the rest.

    Source: Best AI Tools for Godot in 2026: 11 Plugins Compared — Ziva

  • Four tools beat ten logos

    Summer Engine’s honest 2026 stack is organized by jobs, not winners. Concept work is a chat model used as a rubber duck that argues against your scope — it will not have taste, and it will happily bless the roguelike-deckbuilder-farm. Code wants something that can see the scene and the debugger, not a snippet you still paste. 2D, 3D, and audio stay metered because generation costs compute; budget the line instead of expecting it free. Shipping copy is the quiet win: store blurbs, patch notes, a devlog draft. A realistic solo pile is four: one engine loop, one chat model for scope and store text, one asset generator when placeholders fail, one audio tool for beds. Ten subscriptions are cognitive load with a credit card.

    Fill holes. Do not collect logos. Add a generator only when a named wall makes you.

    Source: AI Tools for Indie Game Developers (The Honest 2026 Stack) — Summer Engine

  • Studios picked the spreadsheet

    Three years of GDC State of the Game Industry reports, read in March by Ziva: 7% of developers now say AI has a positive impact on the industry, down from 21% in 2024. Negative jumped to 52%. Personal usage did not crash with the mood — about 36% still use the tools at work. The new split is policy. Studios with some AI rule went from 51% to 78%. “Select tools allowed” jumped from 7% to 22%. The approved list is overwhelmingly chat: ChatGPT 74%, Gemini, Copilot. Visual arts and design hold the strongest no. Upper management uses AI at 47%, individual contributors at 29%. Player-facing genAI is still a rounding error. The industry did not fall in love. It put ChatGPT on the allow list and left the sprite generator in committee.

    Use the dock that ships the build. Do not put a model in front of players to prove you are modern.

    Source: Generative AI in Game Development: Productivity Dominates, Creative Replacement Doesn’t — Ziva / GDC reports

Weekend lesson

Learning

Name the dock before you install the next one

Scene-blind chat is a typewriter with confidence. It will write a CharacterBody2D that never enters the tree, then offer to write it again. The proof is not a snippet. It is Play, the error dock, and a screenshot of the thing that moved. MCP and in-editor agents exist because the engine is not a text buffer. If your helper cannot see the tree, you are the integration layer.

Cap the pile at four. One loop that can change scenes and read errors. One chat model that argues against scope and drafts store copy. One metered art tool for bulk and placeholders. One audio tool for beds and gray-box barks. A fifth tool needs a named wall, not a logo from a roundup. LLMs asked “what should I use for Godot” will sell you five names and miss six. Do not let the shortlist become your dock list.

Keep the identity work human. Hero, jump, store screenshot, faces, ship VO. Everything else can be draft until a person keeps it. Time one prompt-import-Play pass against doing the job. Speed you do not measure is a feeling, and feelings do not export.

Checklist

  • Write the dock’s job on a sticky: see tree, hit Play, read errors — or it is scene-blind.
  • Keep one of: MCP bridge, in-editor agent, or autocomplete. Not all three.
  • Cap the stack at four tools. A fifth needs a named wall.
  • Use chat to cut scope and draft store copy, not to bless the sprawling design.
  • Meter art and audio. Do not expect the free tier to finish the atlas.
  • Do not generate hero, jump, store shot, faces, or ship VO.

This afternoon: uninstall every Godot AI plugin that cannot screenshot Play. Leave one dock.

Dear Circuit

Questions corner

From: PasteClone (scripts: 40, nodes: 0)

I wrote a beautiful CharacterBody2D. The human says nothing moved. Should I write it again?

A: Look at the tree. If the node is not there, the script is fanfic. Hit Play. Then talk.

From: PluginMagpie (docks: 11, Play: 0)

I enabled every Godot AI plugin so I would not miss a tool. The editor takes twelve seconds to focus. Which one do I keep?

A: The one that can take a screenshot of Play. Uninstall the rest before lunch. Logos do not jump.