What AI Can Actually Do In Blender And Unreal

Most of what gets written about AI in game development is about generating things: concept art, textures, music, voices. I am leaving all of that out here, partly because it is the most argued-over part and partly because it is not where I have found the value. The part I use every week is quieter. It is an AI assistant working inside the tools themselves, Blender for modelling and Unreal Engine for the game, doing the fiddly, repeatable work between the creative decisions.

This is what that looks like in practice, where it helps, and where it does not.

How an assistant gets into the tools at all

Both Blender and Unreal can be controlled by script. Blender has had a Python interface for years, and almost anything you can click in Blender, a script can do. Unreal has its own scripting and, in its most recent version, an experimental built-in connection that lets an AI assistant talk to the open editor directly: list what is in a level, place and move objects, read settings back.

That connection is the important bit. Without it, an assistant can only tell you what to click. With it, the assistant can do the clicking, and then check what actually happened rather than assuming it worked.

Where it has genuinely helped in Blender

The clearest example I have is turning a concept sheet into a 3D model. A concept sheet is a drawing of an object from several angles. The traditional first step is to set those views up as reference images in Blender, lined up and at the right scale, before any modelling starts. That setup is slow, exact and dull, and it is exactly the kind of job an assistant does well.

From there, the assistant can block out the main shapes against the drawing, and I review it at set checkpoints before it goes further. I make the calls on proportion and style. The assistant does the repetitive construction and the housekeeping, like naming every part consistently, organising the scene, applying the same shading setup across a set of objects, and rendering preview images so I can compare them side by side.

None of this replaces knowing Blender. You still need to be able to look at the result and say what is wrong with it. What changes is how much of the day goes on the parts that need your judgement.

Where it helps in Unreal

Unreal is a much larger application, and the gains are more about understanding and checking than building.

• Explaining what is already there. Unreal's visual scripting system, called Blueprints, lets you build game logic by connecting boxes on a graph rather than writing code. An assistant that can read a Blueprint graph can explain what an inherited or half-remembered piece of logic actually does, which is useful when you come back to a project after a break.
• Planning before touching anything. Asking for a step-by-step plan, with the exact settings to change and how to check each one worked, before any change is made. Unreal settings are spread across a lot of menus, and a written plan is easier to review than a series of clicks.
• Checking an import. Moving a model from Blender into Unreal has a set of known snags: the model arriving at the wrong size because the two programs measure in different units, an extra bone appearing in the skeleton, animations quietly failing to play. An assistant can check for each of those systematically after every import, rather than me remembering to. (I cover those snags in more detail on the Blender to Unreal Engine 5 page.)

What it is not good at

I want to be straight about the limits, because they are real.

It cannot judge whether a game feels good to play. Timing, weight, the way a jump or a weapon feels under your hands, all of that has to be played and felt by a person.

It does not reliably see what you see. It can render a preview image or read back a number, but it can still be confidently wrong about how something looks. Every result needs checking with your own eyes.

It can make destructive changes. The Unreal connection I mentioned is currently marked experimental, runs only on your own machine, and has no password on it. Some of the tools it exposes can delete or overwrite assets. I keep version control on anything an assistant touches, take a copy of a project before trying anything new, and treat delete and overwrite actions as things I confirm by hand.

It also does not remove the need to learn the tools. If anything, it rewards knowing them better, because the quality of what you get back depends on how precisely you can describe what you want and how quickly you can spot what is wrong.

Who this is useful for

Mostly solo developers and small teams, where the same person is doing modelling, importing, setup and game logic in one afternoon. That is where the repetitive work between the creative decisions adds up, and where handing it off makes the biggest difference. A larger studio with dedicated technical artists will already have its own scripts and pipeline for most of this.

If the machine you are working on is the bigger worry, I have written separately about what AI does and does not change about running Blender and Unreal on a modest computer.