BEYOND THE PROMPT: AI COMES TO UNREAL ENGINE
As AI moves beyond code generation and into the Unreal Editor itself,
Tanglewood Games CTO Terence Burns explores the tools, opportunities and considerations facing developers today
A
I and Unreal Engine have been a hot topic recently, but Tim Sweeney’s comments in October weren’t news to us. At Tanglewood
Games, we work with a number of AAA developers, giving us a good view of how AI is being adopted across their projects. As recently as summer 2025, none of the eight projects we were involved in were using AI for any serious part of development. Today, that’s risen to three quarters. I’m sure the others are evaluating its place in their pipelines.
AI IN EVERYDAY ENGINEERING AI-assisted coding has been around for a while now. Most major IDEs support coding assistants, and generating code is only part of what they’re good for. They can help developers understand unfamiliar code, work through problems and review changes before another engineer needs to look at them. But we’re also seeing more sophisticated applications across the projects we support. One particularly interesting example is the automated processing of crash reports. AI can analyse and categorise incoming crashes. Some of our clients are taking this further by using AI to investigate and even propose fixes before an issue reaches Jira. The result can be a shelved changelist ready for a senior engineer to review, rather than another ticket waiting in the backlog.
We’re seeing clients do considerably more with AI
than simply asking questions and generating code snippets. We’re now looking at developing AI agents and repeatable workflows that can interact directly with development environments, rather than simply suggesting what a developer should do next. The good news is that much of this is already possible with Unreal Engine today. There’s no need to wait for Unreal Engine 6, but understanding the tools, their limitations and where they fit into your development process is important.
40 | MCV/DEVELOP November/December 2026
BEYOND THE IDE Arguably, the biggest impact on developer workflows
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44 |
Page 45 |
Page 46 |
Page 47 |
Page 48 |
Page 49 |
Page 50 |
Page 51 |
Page 52