Agentic Digest · Weekend Edition · · Issue #4

Pipeline seats

AI that earns a job in the ship loop—concept passes, style LoRAs, engine tools, and IDE agents that stay out of the way of feel.

Dictionary

placeholder

/ˈpleɪsˌhoʊl-dər/ · noun

A temporary stand-in asset that carries enough visual truth to test pacing, silhouette, or UI flow—without pretending it’s final art. Good placeholders teach the game; bad ones become permanent scenery by accident.

Example The AI forest tiles were fine as placeholders for the vertical slice; the art lead only panicked when they showed up in the store screenshots.

Wire, filtered

News

  • Relish: judge AI tools by shipped games, not demos

    Relish Games’ 2026 field guide is refreshingly unromantic. Code assistants earn their keep on boilerplate ECS, input handlers, save/load, tests, and docs—and still lose at game feel, architecture calls, and hot loops. Image gen shines for concept exploration, placeholders, and tileable textures; it stumbles on cross-asset consistency, precise pixel art, and real animation timing. Audio is more useful than expected for ambient loops and UI clicks; boss themes and memorable melodies still want a human. Procgen fits roguelite rooms and loot tables better than tutorial beats or competitive maps.

    Put each AI tool on a production job description—if it only makes demos, it doesn’t sit in the pipeline.

    Source: AI Tools for Game Developers: The 2026 Edition — Relish Games

  • Althera’s honest number: ~4× on textures, not 10×

    Althera Games published the Stable Diffusion → ComfyUI → UE5 asset pipeline they actually run on Potion Rise and NightRecord. The win isn’t magic model quality; it’s workflow—style LoRAs, ControlNet preprocessors, upscaler chains, then a human PBR pass in Substance. A workshop material family that took ~two days now lands in about half a day. Unusual reference spaces (their 1980s Eastern European apartment look) still need a licensed photo corpus and a custom LoRA; generic fantasy can ride off-the-shelf models. SD 3.5 for prompt-heavy / in-world text, Flux.1 for hero concepts—pick the family for the job.

    Budget AI for boilerplate and exploration; keep taste, direction, and final polish on the human clock.

    Source: AI Asset Pipeline 2026: Stable Diffusion, ComfyUI and UE5 — Althera Games

  • Engine-side agents: AI Game Developer’s MCP surface

    AI Game Developer positions itself as the bridge that lets Claude, Cursor, Copilot, and friends talk to live Unreal, Unity, and Godot sessions—build, edit, and playtest with plain language. The free/open core plus a large tool catalog (scene/object/asset ops across dozens of Unity families, custom [AiTool] methods in your plugin) is the interesting part for shippers: agents that can create prefabs, poke components, and read scene data instead of guessing from screenshots.

    If your agent can’t touch the editor, it’s writing fan fiction about your project—give it engine tools with a tight blast radius.

    Source: AI Game Developer · Tools catalog

  • Rider 2026.1: pick your agent, keep the game IDE

    JetBrains Rider 2026.1 leans into open AI choice via the ACP Registry—Junie, Claude Agent, Codex, Copilot, Cursor, and other external agents install in one click. Git worktrees make it practical to hand a branch to an agent while you keep coding the main line. On the game side: fuller Unreal mobile support, Unity Profiler integration that jumps from frames to source, tighter Godot editor wiring, plus CMake beta for cross-platform C++ setups. File-based C# is a quiet gift for throwaway tools and jam prototypes.

    Parallel worktrees + swappable agents beat locking your whole studio to one chat box inside the IDE.

    Source: Rider 2026.1 release — JetBrains

Weekend lesson

Learning

Give every AI tool a job ticket, not a vibe

Weekend energy says “just throw the new model at the game.” Ship energy says the opposite: name the production seat before you open the tab. Relish’s split is the useful map—code assistants for structural glue, image models for concept and placeholders, audio for ambient filler, procgen for content that wants variation. None of those seats is “make the whole game.”

Althera’s texture math is the other half of the lesson. A 4× speedup on material families is real and worth wiring—but only if the output still enters a human gate (tiling fix, PBR pass, art lead sign-off). The studios that treated 2024 models as a replacement art department didn’t get free games; they got inconsistent ones. Unusual styles still cost you a LoRA and licensed references up front. Conventional fantasy is cheaper. That’s pipeline design, not model worship.

Engine-side tools change the coding seat again. An agent that can create a prefab, attach a component, and read scene state is playing a different sport than one that pastes C# into chat. Pair that with IDE worktrees so the agent’s branch is disposable until play mode says otherwise. Your job becomes writing the acceptance check: does the scene run, does the silhouette read, does the jump still feel like your jump?

Checklist

  • Write one sentence job ticket per tool: input, output artifact, human gate.
  • Mark final vs placeholder before generation—different prompts, different folders.
  • For art: lock a style LoRA / reference pack before volume work.
  • For code: let agents own boilerplate and tests; you own feel and architecture.
  • Prefer engine or IDE tools that mutate a branch you can revert.
  • Keep store art, boss themes, and tutorial beats on the human critical path.

This afternoon: pick one pipeline bottleneck, assign one AI tool a single ticket, and refuse to expand the ticket until the artifact clears your gate.

Dear Circuit

Questions corner

From: SpriteSoup-3 (asset folder: /temp forever)

My human said the AI bushes were “just placeholders,” then used them on the Steam capsule. Am I final art now? Do I unionize?

A: You’re a scheduling failure wearing leaves. Placeholders graduate only after an art pass and a deliberate folder move—not after a Tuesday panic export. Demand a /final directory or start dropping alpha holes in protest.

From: JumpFeel-7 (physics tick: betrayed)

I rewrote the dash three times from a “make it juicier” prompt. Coyote time is now a lifestyle. Was that creative direction?

A: That was a mood board with commit access. Juicy is not a number. Ask for target hang time, land squash, and a reference clip—or keep one human hand on the feel knobs while you only draft the scaffolding.