RuneScape developer Jagex has issued an apology after a promotional trailer for its upcoming Dragon Slayer 2 quest, unveiled over the weekend at its annual RuneFest event in Birmingham, England, was found to feature a player character rendered with six fingers and other telltale signs of generative AI. The controversy erupted almost immediately following the game’s keynote presentation, landing on Jagex just days after another generative-AI dispute had already drawn criticism toward the studio.
The trailer in question promotes Dragon Slayer 2 for RuneScape 3, one of the developer’s longest-running titles. During a segment of the RuneFest keynote, viewers noticed that the on-screen character displayed an extra digit along with what appeared to be a strange sneaker-like sole attached to otherwise armoured footwear—an inconsistency that quickly drew attention across social media and was widely identified as the output of generative AI tools.
The trailer is pulled while Jagex investigates
In response to the backlash, Jagex removed the video from public view. Alec ‘Mod Sween’ Sween, a lead on Old School RuneScape who stepped in to address the situation on the 2007scape subreddit, confirmed that an urgent investigation had been launched.
“We’re aware of the concerns raised about the Dragon Slayer 2 trailer and have taken it down, while we investigate this urgently. This trailer was produced by a trusted external partner who had explicitly confirmed that GenAI would not be used. But, among other things, there’s a sixth finger and, well, that’s pretty hard to explain away. For that we apologise.”
Alec ‘Mod Sween’ Sween, Jagex
Jagex reaffirms its opposition to generative AI
Sween reiterated the studio’s established position on the technology, drawing a parallel with an earlier incident involving the esports organisation 100 Thieves. He noted that this marked the second time in rapid succession that concerns about generative AI had emerged through partners Jagex trusted.
“Our position is clear at Jagex: we don’t use GenAI to create our games, artwork or creative assets, and will not knowingly allow it to be used on our behalf. This is the second time in quick succession that concerns about generative AI have arisen through partners we trusted, and for us that highlights an issue with our own processes which we must address.”
Alec ‘Mod Sween’ Sween, Jagex
The developer said it is now overhauling its review process to prevent similar oversights. In the interim, Jagex plans to work with and commission creators from within the community to ensure that the story of Dragon Slayer 2 is told “to the standard befitting of such an update.”
“We should have caught these things”
The incident has prompted questions about how a trailer so heavily marked by generative AI could pass through Jagex’s review pipeline. In its follow-up response, the studio acknowledged that it had fallen short.
“We should have caught these things… We didn’t do well enough and can’t simply place the blame elsewhere.”
Alec ‘Mod Sween’ Sween, Jagex
The six-fingered hand was one of several glaring anomalies visible even to casual viewers, reinforcing community frustration that such errors had slipped through. The timing has only sharpened criticism, with the Dragon Slayer 2 trailer arriving shortly after another generative-AI controversy involving Jagex’s own ecosystem.
Looking Ahead
Jagex has not yet provided a revised release window for Dragon Slayer 2 or a timeline for when an updated promotional video may be released. The studio says it will continue to commission community creators while its internal review overhaul is completed, and it has signalled that accountability measures within its partner-vetting process are expected to follow.
The episode underscores mounting scrutiny across the gaming industry over the use of generative AI in marketing materials, even when such assets originate from third-party studios. As Jagex works to restore confidence, players will be watching closely for how thoroughly the developer addresses both the immediate fallout and the broader process failures it has acknowledged.
1 comment