Epic Games reportedly goes "AI first": no more hand-written code
According to an Ars Technica report dated 12 October 2026, Epic Games is moving to an "AI first" development model. The article's headline and subheadline point to a "no hand-written code" principle and a non-AI art option for a delayed shooter set in the Marvel and Star Wars universes. The available data contains no official confirmation from the company, and no figures on timelines or budgets. • Epic is reportedly making AI its core development tool. • Hand-written code is in question. • A non-AI option is being discussed for the art.
AI-processed from Ars Technica; edited by Hamidun News
According to Ars Technica on 12 October 2026, Epic Games is steering game production toward an "AI first" model. The available data shows two things: developers are allegedly told to stop writing code by hand, and a non-AI art option appears for a delayed shooter based on the Marvel and Star Wars licenses. This is still a rumor, not a company statement, and we have no concrete numbers (timelines, budgets, share of the team).
What exactly is being reported
The source describes a shift in approach at the studio behind Fortnite and Unreal Engine. The phrase "no hand-written code" means engineers must write programs through AI assistants and agents rather than type them out themselves. In this setup, the human defines tasks, checks the results and stays responsible for the architecture.
If the report is accurate, this is a hard rule, not a recommendation. Many studios allow Copilot and similar tools as an option. A requirement to go through AI by default changes roles, review processes and even hiring criteria.
A separate detail concerns the art. Judging by the subheadline, a version without AI generation is possible for the delayed shooter. The article does not explain why. Licensors such as Disney are typically cautious about generative models because of rights to likenesses and training data, but that is our own assumption, not a fact from the publication.
What is known for certain
- Source: Ars Technica, published 12 October 2026, in the "reportedly" format.
- Claim 1: a shift to an "AI first" development model.
- Claim 2: no more hand-written code.
- Claim 3: a non-AI art option for the delayed Marvel and Star Wars shooter.
- The available text contains no official comment from Epic.
- There are no metrics on speed, cost or team size.
Why this looks like a logical move for Epic
Tim Sweeney, Epic's CEO, has long advocated broad use of AI. He publicly objected to AI labels in game stores, arguing that neural networks will soon be part of almost every production process. In May 2025, Fortnite added an AI version of Darth Vader with a voice recreated from James Earl Jones. The SAG-AFTRA union then filed an unfair labor practice charge.
There is also an economic backdrop. In September 2023, Epic laid off about 830 people, roughly 16% of its staff. When AAA projects get more expensive and schedules slip, cost pressure only grows. The delayed shooter illustrates exactly this problem: big licenses demand quality and release dates, not experiments.
Risks that won't go away
Code written by a model still has to be read, tested and maintained. In Fortnite's engine and netcode, mistakes are costly. If the output is batches of generated patches instead of hand-written code, the load shifts to reviewers and QA, and quality debt quietly piles up.
The second risk involves people. A ban on writing code by hand irritates strong engineers, and junior developers lose their usual growth path. The third risk is legal: licensed franchises sit poorly with the unclear legal status of AI-generated content. That is why the split of "code through AI, art without AI" looks like a deliberate compromise, although there is no confirmation of this yet.
What to watch next
First: whether Epic issues an official statement or Sweeney comments. Second: how the release timeline of the delayed shooter changes, and whether its date is confirmed. Third: whether the policy will affect Unreal Engine and external partners.
For studios, the practical takeaway is simple. If you are adopting AI coding, first lock down your review rules, test coverage and accountability for generated code. For art built on third-party licenses, agree in advance with the rights holder on what is permitted. For developers: skills in directing agents, reading other people's code and debugging are becoming the main working tools, whether or not the story about Epic turns out to be true.
Build & Ship Production AI Apps with Vibe Coding
Join Zhemal Khamidun's hands-on Vibe Coding Intensive at hamidun.com/vibecoding — master Claude Code, Cursor, and autonomous agentic workflows.
The AI world, distilled — once a week
Seven stories that actually mattered, hand-picked. No noise, no reposts, no press releases.
Done! Check your inbox for a confirmation.