There are multiple things I wanna talk about here. It's a pretty long post, so feel free to ignore.
I'll start by saying that I've a master's degree in computer science, and I've spent over 4 years doing professional work, mostly in web, mobile, and desktop development.
I got into UE development about 4 months ago, and ever since, I've been learning new concepts and figuring out how to use the editor, Blueprints, C++, and so on.
I've learned all of this through tutorials and free courses on YouTube. I've even paid for a few courses on Udemy.
Naturally, I ran into issues while following some of these tutorials for several reasons:
Most tutorials are over 2-3 years old.
I run into edge cases that the instructor hasn't covered.
Differences between UE versions.
Whenever I ran into these issues, I used AI to help me understand how to fix them. However, in 80-90% of cases, it would just waste my time and send me down a rabbit hole. I'd eventually either figure out the solution myself or find a tutorial made by someone a few years ago.
The issue nowadays is that there are fewer and fewer tutorials being created by actual developers. And when you do find something, it's mostly AI-related content or videos titled something like "How I Made a Whole Game with Fable and Claude."
A few days ago, I ran into an issue related to navigation. The NPC would open a door and get stuck running into it if the player was right behind the opened door. Instead, it should have gone around the door to catch the player.
Part of the issue was that navigation wasn't updating properly with the door's rotation. I was using a NavModifier component to switch the area class between Null and Default so that the NPC would know how to navigate around the door. However, for some reason, it wouldn't update properly when the door rotated.
Naturally, I asked AI how to fix the issue, and it kept suggesting things and workarounds that didn't actually solve the problem.
I'd argue that I would've saved time if I'd just Googled the issue and looked for tutorials made by developers instead of asking AI first.
Initially, it started recommending generic things to check that I'd already verified were working correctly, along with suggestions that weren't even related to the issue. Then it suggested calling the AI Move function again once the door opens. I told it that it doesn't make sense because the problem was with navigation itself, so calling AI Move again wouldn't solve it.
When I pointed that out, it responded with "Ah, you're right" and suggested using a box collision instead. I then asked why I'd need to do that when I could just use the mesh itself, since it already had simple collision. It responded with "Oh, you're right, there's no need for it."
We kept going back and forth for hours, and it still couldn't fix my issue.
Eventually, I looked it up online and found an old video of someone running into the exact same issue in UE4. He explained it perfectly and even demonstrated all the possible solutions.
One of the solutions he suggested was using a box collision and setting its area class to Null. Another was creating a separate Blueprint containing only the door and a NavModifier, then adding it to the parent Blueprint as a Child Actor, so that if the door rotates, the whole NavModifier would rotate with the door.
He didn't explain how to toggle between Default and Null area classes in the child Blueprint when the NPC opens the door or when the player closes it. I figured out the rest myself. However, he gave me the initial direction I needed to solve the problem.
So, what am I trying to say with all of this?
This post isn't about bashing AI. In fact, I think it can be useful when it comes to obtaining general knowledge about something. For example, asking "What's the difference between Dynamic and Dynamic Modifiers Only in navigation generation?" is perfectly reasonable.
My point is that people like that person who made the tutorial are becoming increasingly rare. Eventually, we're going to lose a lot of that accumulated knowledge and experience because fewer people will be putting in the effort to understand these systems deeply enough to explain them to others.
The other thing I wanna mention is that people just don't seem to care about code quality anymore.
I understand that AI can make you significantly faster at your work. I've tried using agentic AI in web development and other areas myself. But here's the thing: when you use AI agents, they can start generating tens of thousands of lines of code, and you simply don't have the time or ability to review all of it properly. So what do you do? Some people end up assigning another AI agent to review the code that the first one generated.
The problem is that you eventually stop knowing what's actually going on in your own project, and you become completely dependent on AI to do the work for you.
That's exactly why I've decided not to use AI during my game development process. I wanna have complete control over what's happening in my project. Also, I think game development is an art and art needs a human taste IMO. On top of that, I'm not like working in a company, so why would I use agentic AI for this? I get to enjoy that dopamine hit whenever I fix an issue, especially when AI itself doesn't know how to fix it.
You could argue that AI combined with an experienced engineer is much more powerful, and I wouldn't necessarily disagree. But here's the question: How does someone become an experienced engineer in the first place?
They make mistakes, run into problems, troubleshoot issues, and figure things out themselves.
I've learned a lot during my Unreal Engine learning journey, and a big reason for that is because I didn't just tell Claude to do everything for me.
Imagine if I had absolutely no knowledge of navigation or how any of these systems worked. What would I have done in this situation? Hand the entire problem over to AI, again and again, hoping it eventually spits out something that works?
And that's exactly what worries me about the future of game development.
We're making it easier to produce things without necessarily understanding how they work, while simultaneously making the people who actually understand these systems harder to find.
If this continues, I genuinely believe experienced developers will become increasingly rare over the next decade or so.