– RuneScape developer Jagex pulled a new trailer after a six-fingered knight led to allegations of generative AI usage from fans.
– There were ups and downs for RuneScape players over the weekend
– Started with a string of big reveals from RuneFest 2026
– Ended with social media users voicing concern that generative AI had been used to make new trailer for RuneScape 3‘s Dragon Slayer 2 quest.
– Backlash loud enough that Jagex stepped in – released official response AND pulled the trailer while investigating “urgently”
– Statement posted on Reddit by social media manager Alex Sween (via Kotaku)
– Statement acknowledged concerns including knight with six fingers
– Quote: “Hello, it’s me, again, talking about Gen AI, again,” referencing separate recent incident involving 100 Thieves and OSRS
– Team took “hard line stance” against generative AI earlier this year (bağlantı)
– Quote continues: “We’re aware of the concerns raised about the Dragon Slayer 2 trailer and have taken it down, while we investigate 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.”
– Team made position clear: “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.”
– Second instance of AI suggests deeper problem for MMO developer
– Jagex plans to address approach to working with partners going forward
– Then today, Jagex decided to use AI in a trailer – knight has 6 fingers and boots look like modern sneakers (this seems to be from a tweet)
– Quote: “Immediately following RuneFest we’re overhauling our review processes,” continued statement, “and we’re going to work with and commission creators from the community to make sure that the story of Dragon Slayer 2 is told to the standard befitting of such an update.”
– Six-fingered knight feels like smoking gun, another bizarre piece of art – fully-armored knight wearing what seemed to be regular tennis shoes raised eyebrows too
– In follow-up replies, Sween acknowledged it’s something Jagex “should have caught,” adding “We didn’t do well enough and can’t simply place the blame elsewhere.” (bağlantı)
– As Jagex refines processes, still working on other projects. RuneScape 4 is one of these new projects, with an animated adaptation also in the works with YouTuber MoistCr1tikal.
Media tags to preserve: , ,
Link tags to preserve: RuneScape, a string of big reveals from RuneFest 2026, RuneScape 3, posted on Reddit, Kotaku, involving 100 Thieves and OSRS, took a “hard line stance” against generative AI, acknowledged, one of these new projects, with an animated adaptation also in the works
Actually, looking more carefully:
– The weekend events: RuneFest 2026 reveals → new trailer for RuneScape 3’s Dragon Slayer 2 quest → fans spot six-fingered knight → allegations of GenAI → Jagex pulls trailer and responds
– Then “today” – it seems there might be confusion. Let me re-read the tweet: “Then today, Jagex decided to use AI in a trailer for an upcoming quest, the knight in video has 6 fingers and boots in a another frame look like modern sneakers.”
Hmm, this is a bit confusing. It could be that after pulling the first trailer, they released a new one which also had issues. Or it’s describing the same trailer. Let me interpret this as: Jagex pulled the original trailer, but then there appears to have been confusion where another version surfaced with similar problems (six fingers, sneakers). Actually, I think the tweet is commenting on the situation – that despite pulling it, a new trailer appeared with the same issues.
Actually, re-reading more carefully, I think this might be describing events over multiple days:
1. Weekend: RuneFest 2026 reveals
2. Then: New Dragon Slayer 2 trailer for RS3 released
3. Fans spot six-fingered knight → GenAI allegations
4. Jagex pulls trailer + responds/apologizes
5. “Then today” – a new/updated trailer appears with the same problems (six fingers, sneakers)
TITLE options:
– “RuneScape Developer Jagex Pulls Trailer After Six-Fingered Knight Sparks AI Concerns”
– “Jagex Rettracts RuneScape 3 Trailer Following Generative AI Allegations Over Six-Fingered Knight”
– “Six Fingers and Sneakers: Jagex Pulled Its RuneScape 3 Trailer Amid GenAI Backlash”
Let me go with something punchy.
Draft lead:
“British MMO developer Jagex has withdrawn its newly released promotional trailer for RuneScape 3’s long-awaited Dragon Slayer 2 quest after members of the community spotted what appeared to be generative AI artifacts—including a knight rendered with six fingers—prompting an urgent investigation and one of the studio’s most candid public apologies yet.”
Let me refine:
“Over the course of a turbulent weekend that began with excitement over RuneFest 2026’s reveals, British game studio Jagex found itself on the defensive after fans spotted generative AI anomalies in its freshly minted trailer for RuneScape 3’s Dragon Slayer 2 quest. The backlash forced the developer to pull the video and launch an urgent investigation—and issue one of its most candid public apologies yet.”
That has who (Jagex), what (pulled trailer, investigating), when (this past weekend), where (RuneScape community/social media), why (GenAI anomalies like six-fingered knight), how (fans spotted it). Good.
Now let me build out the rest following the template structure.
I’ll integrate the media and link tags naturally. Let me place after the lead perhaps, or somewhere appropriate. The links need to be woven in grammatically.
For subheadings:
– Subheading 1: Something like “A Trailer Pulled Amid AI Concerns” or “The Six-Fingered Knight That Sparked a Firestorm”
– Then Looking Ahead section as specified in template
Actually the template specifies:
[Story-Specific Subheading 1]
…
…
…
[Looking Ahead]
…
So I need one story-specific subheading and then “Looking Ahead”. Let me use those.
Draft:
Jagex Pul Its RuneScape 3 Trailer After Six-Fingered Knight Triggers Generative AI Backlash
Join the conversation