Divinity fan decodes hidden Elder Futhark runes in Larian's trailer - and may have found the game's villain

We need answer user. Need produce revised article? Let's understand context. The conversation contains a system/developer chain? We have "Current Draft:" then "Editorial Feedback:" then "Original Plan:" with content. Wait the user message shows a big block that starts with "Current Draft:" and includes the draft/plan? Let's parse. The user's actual latest message appears to be a task: "The user wants me to write a complete article for SinfulShadows based on the provided plan and research. Let me carefully review all the requirements: ..." then lists requirements, key facts, then "Now let me draft the article." with an unfinished draft, then "Editorial Feedback:" with a confusing "Reviewer Role" note, then "Original Plan:" with detailed plan. So this is a single user message containing an in-progress draft? Actually it looks like an attempted assistant response? But user is asking to write article. The instruction says "Your task is to improve the article based on editorial feedback" originally? Wait the system prompt says we are an expert gaming journalist revising an article based on editorial feedback. There is a system prompt "System: You are an expert gaming journalist revising an article based on editorial feedback. Your task is to improve the article while maintaining its core content and voice." Then guidelines. Then "CRITICAL: Output ONLY the revised article text..." So indeed the task is to revise an article. But the user message contains "Current Draft:" and then a draft, "Editorial Feedback:" and then some editorial feedback? Actually the "Current Draft" section contains the start of an article with title and intro, then "Editorial Feedback:" section contains "The user has provided a set of instructions ... However, there's a key issue: ..." This seems like meta-commentary, not actual feedback. Then "Original Plan:" contains the article plan. Maybe the intended workflow: The user pasted a draft and wants us to revise it according to editorial feedback. But the "Editorial Feedback" block is strange: it says "The user has provided a set of instructions for me to write a complete article... However, there's a key issue..." It reads like an AI's reflection. There is no actual editorial feedback with specific points. Let's re-read everything carefully. The user message begins: "Current Draft: The user wants me to write a complete article for SinfulShadows based on the provided plan and research. Let me carefully review all the requirements: 1. Length: 800-1200 words ... Now let me draft the article. Draft:, - # Divinity fan decodes hidden Elder Futhark runes in Larian's trailer - and may have found the game's villain When Larian Studios took the stage at The Game Awards 2025, it did not come to explain. It came to show. The world-premiere trailer for Divinity, the studio's return to its own long-running series, offered no gameplay, no narrator, and no answers. Instead, viewers watched a bound figure burn alive inside a towering wooden effigy while a silent crowd looked on. It was brutal, cryptic, and unmistakably Larian. What almost no one noticed at the time was that the trailer was hiding a message in plain sight. Seven months later, a devoted fan has translated the Elder Futhark runes visible in that" Then "Editorial Feedback:" with "The user has provided a set of instructions for me to write a complete article for "SinfulShadows" based on the provided plan and research. However, there's a key issue:..." and then it discusses the reviewer role vs writing. Then "Original Plan:" with the full plan. This is bizarre. It seems like the "Current Draft" is actually a partial draft that I (assistant) was generating, and the message got cut off. Then someone appended "Editorial Feedback" as if there is feedback. But there's no actual feedback about the article content, just meta commentary about conflicting instructions. Given the system prompt tells us to revise an article based on editorial feedback, and the user message contains a "Current Draft" and "Editorial Feedback" section, perhaps we are to treat the "Editorial Feedback" as the feedback to address. But the feedback text doesn't provide article-specific suggestions; it says there's a key issue with instructions. Hmm. Alternatively, the user wants us to ignore the confusion and write the complete article. The "Original Plan" is the plan to follow. The "Current Draft" is incomplete. The "Editorial Feedback" might be an error. The user's final instruction embedded in "Current Draft" says "The user wants me to write a complete article for SinfulShadows based on the provided plan and research." That is the primary task. Thus, our output should be the completed article, not meta commentary. We should not mention the feedback or the reviewing process. The system prompt says output ONLY the revised article text, no preamble. So we should produce the article. Need decide content. We have the plan and key facts. Need write an article 800-1200 words, markdown, no em dashes, no naming other news sites, keep creator anonymous, embed videos. Let's construct a polished, complete article. Need choose title. Use hyphen with spaces. Title: "Divinity fan decodes hidden Elder Futhark runes in Larian's trailer - and may have found the game's villain". That's fine. Need include headings. Let's plan with maybe 4-5 sections plus intro and conclusion. Need not strictly follow the plan numbering but should cover all. Let's outline: Introduction: Hook with TGA 2025 reveal, brutal ritual, no gameplay, hidden runes, translation, Lord of Chaos. Section 1: The trailer that launched a thousand theories - Divinity seventh game, teased with hellstone statue in Mojave Desert. - Three-minute cinematic trailer, no gameplay, bound figure burned in wooden effigy. - Strong reaction, Larian says not Baldur's Gate 4. - Embed trailer video. Section 2: A message hiding in plain sight - Content creator translated Elder Futhark runes. - Explain Elder Futhark, ancient runic alphabet. - Whistleblower? Actually keep anonymous. - Mention trailer crafted by UNIT IMAGE in collaboration with Larian, BTS on 80.lv. - Embed the other video perhaps. Section 3: The Lord of Chaos, explained - Lore: creator of demons, trapped in Tartarus. - Fan theory: likely antagonist, story of escape/demonic invasion. - No official confirmation. Section 4: Larian's love of hidden secrets - Baldur's Gate 3 hidden details, community detective work. - Signature moment, but skeptical note: could be flavor, but "Lord of Chaos" specificity makes coincidence unlikely. Conclusion: Framing as best lead, community's hunt continues, Divinity's story has already begun in players' minds. Need include quotes or statistics from research. We have facts: three-minute trailer, seven months later, seventh game. Could include "roughly seven to eight months later" from plan. Use that. Also "80.lv" behind-the-scenes breakdown. Good. Need hyperlinks: 80.lv article URL (https://80.lv/articles/take-behind-the-scenes-look-at-creation-of-larian-s-divinity-trailer) from research. The YouTube links: https://youtu.be/AUjRhUnNGzo and https://www.youtube.com/watch?v=VxzyVeAG00w. Embed as markdown links on their own lines. Need decide titles/labels. The system says "Embed relevant YouTube videos using markdown link format on its own line." Could just write links with descriptive text, like "[Watch the Divinity trailer](https://youtu.be/AUjRhUnNGzo)". That should be fine. Maybe label one as trailer and one as deep dive. But if uncertain, we can use generic: "[Watch the footage that started the hunt](https://youtu.be/AUjRhUnNGzo)" and "[A closer look at the rune decode](https://www.youtube.com/watch?v=VxzyVeAG00w)". Hmm. The system says "The publishing system will convert these to proper embeds" so the link text doesn't matter much. Use natural phrasing. Need not name WolfheartFPS. Keep anonymous. Avoid "widely suspected" maybe? The plan says note identity caveat. We can say "The creator behind the translation has not been officially identified" or "A Divinity content creator" without name. We could mention "some observers have speculated about the translator's identity, but Larian has not confirmed anything" but that might be unnecessary. Better keep it clean and focus on substance. Need avoid em dashes. Use commas, semicolons, colons, or spaces-hyphen. Ensure no ", " or ", ". Also avoid double hyphens. We'll use " - " for title only? That's a hyphen with spaces. Fine. Need no naming other news sites. We won't. Need "write like a human journalist" with engaging style. Use short paragraphs. Let's draft the article now. Word count target around 900-1100. Let's write carefully. Draft article: # Divinity fan decodes hidden Elder Futhark runes in Larian's trailer - and may have found the game's villain When Larian Studios took the stage at The Game Awards 2025, it did not come to explain. It came to show. The world-premiere trailer for Divinity, the studio's return to its own long-running series, offered no gameplay, no narrator, and no answers. Instead, viewers watched a bound figure burn alive inside a towering wooden effigy while a silent crowd looked on. It was brutal, cryptic, and unmistakably Larian. What almost no one noticed at the time was that the trailer was hiding a message in plain sight. Seven months later, a Divinity content creator has translated the Elder Futhark runes visible in that footage, and the phrase they reveal has electrified the game's lore community: Lord of Chaos. [Watch the trailer that started the hunt](https://youtu.be/AUjRhUnNGzo) ## The trailer that launched a thousand theories Divinity is the seventh mainline game in the series that first put Larian on the map. It arrives after a long detour through the Forgotten Realms, and the studio has been clear that this is not Baldur's Gate 4. This is a return to Larian's own universe, and the reveal was designed to make that distinction felt. The teaser campaign was as cryptic as the trailer itself. Before the stage show, a hellstone statue appeared in the Mojave Desert, photographed and shared across social media with no official explanation. Then came the world premiere: a three-minute cinematic feast of medieval dread. A bound figure is dragged toward a towering wooden effigy and burned alive as a crowd watches. There are no characters to root for, no dialogue to parse, only ritual, fire, and dread. The internet reacted with the usual mix of excitement and confusion. Fans picked apart every frame, searching for clues about the setting, the characters, and the threat at the heart of the story. Most came away empty-handed. The trailers that followed offered more atmosphere but still no answers. For seven months, the biggest question in the Divinity community went unanswered: who, or what, is the villain? ## A message hiding in plain sight The answer, it turns out, was in front of everyone the whole time. A Divinity content creator, whose identity has not been officially confirmed, decided to take a closer look at the runes carved into the trailer's environment. Using the Elder Futhark alphabet, one of the oldest known runic systems, they translated the markings and found three words: Lord of Chaos. Elder Futhark is not a decorative cipher that happens to look ancient. It is a real alphabet with clear correspondences to modern letters, and its use here is a deliberate design choice rather than random set dressing. That matters, because the trailer was produced by UNIT IMAGE in collaboration with Larian, and a behind-the-scenes breakdown on 80.lv shows the level of craft that went into every detail of the short film. These runes were not an accident. [A closer look at the rune discovery](https://www.youtube.com/watch?v=VxzyVeAG00w) For fans of the series, the translation landed like a thunderbolt. In established Divinity lore, the Lord of Chaos is not a minor figure. He is the creator of demons, a primordial being of immense power who was ultimately sealed away in Tartarus, the setting's version of hell. Naming him in the reveal trailer is the strongest hint yet that he plays a central role in the new game. ## The Lord of Chaos theory, explained The lore fits the trailer's tone almost too well. The burning effigy, the grim ritual, the looming sense of apocalypse: these are the visual language of a demonic threat. For months, fans have speculated that the new game would deal with the Lord of Chaos breaking free of his prison, or with someone trying to release him. The rune translation adds a layer of evidence to that theory, but it is not proof. Larian has made no official statement about the meaning of the runes, and the studio has a long history of planting red herrings alongside genuine secrets. Still, the specificity is striking. If the runes were meant to be atmospheric flavor, the chance of them spelling out precisely "Lord of Chaos" would be astronomical. The more plausible reading is that Larian seeded the reveal trailer with a clue for the most dedicated members of its community, trusting them to find it and start the conversation. ## A pattern of hiding secrets in plain sight That trust is part of Larian's DNA. Baldur's Gate 3 was filled with hidden details, obscure interactions, and environmental storytelling that rewarded the most obsessive explorers. The studio has built its reputation on burying secrets that players can uncover together, and a runic message in a cinematic trailer fits that philosophy perfectly. The Divinity community, meanwhile, has already turned the decode into a collaborative project. Since the translation surfaced, lore-focused fans have scoured every frame of the trailer and the 80.lv breakdown for additional markings, symbols, and references. If there are more secrets to find, the hunt is well underway. There is, of course, a skeptical note to strike. Without official confirmation, the Lord of Chaos remains a strong fan theory rather than a confirmed plot detail. Larian could reveal that the runes were decorative, or that they point to something entirely different. But in a game series where names hold power, "Lord of Chaos" is not the kind of phrase you scrawl onto a set piece by accident. ## The story has already begun The decode has done what Larian presumably intended: it has turned a seven-month wait into an active investigation. The Lord of Chaos theory makes narrative sense, fits the trailer's apocalyptic imagery, and aligns with the studio's love of hiding secrets for fans to find. It is the best lead yet into Divinity's cryptic next chapter. But with Larian staying silent, the community's work is not finished. The next clue could be hiding in the next trailer, in a piece of concept art, or in a detail nobody has noticed yet. Whether or not the Lord of Chaos turns out to be the true villain, one thing is already certain: Divinity's story has begun in its players' minds. Need check word count. Let's estimate. The article is roughly maybe 1000 words. Let's count? Not necessary but should be within 800-1200. Need check for em dashes. Use " - " in title. No em dashes. Need check text for " - " only as hyphen. Also no ", ". Good. Need ensure "Elder Futhark alphabet" is accurate. The plan says "ancient runic alphabet." Good. Need maybe include "roughly seven to eight months" instead of "seven months". The plan says seven to eight months. The user facts say "Seven months later." I'll use "roughly seven months later" or "seven months later". Fine. Need mention "seventh game in the series" - yes. Need mention "hellstone statue in the Mojave Desert" - yes. Need mention "not Baldur's Gate 4" - yes. Need mention "UNIT IMAGE and 80.lv" - yes, with hyperlink to 80.lv? We should hyperlink it. We currently wrote "a behind-the-scenes breakdown on 80.lv" without a link. The instruction says "write as original coverage. Only exceptions: official sources, petitions, storefronts, community platforms. Hyperlink them." 80.lv is a behind-the-scenes craft community platform, probably acceptable. Let's hyperlink to the specific article. URL from research: https://80.lv/articles/take-behind-the-scenes-look-at-creation-of-larian-s-divinity-trailer . We'll use that. Need embed the two videos. We have one after intro, and another in Section 2. That's fine. Ensure each is on its own line. Good. Need maybe not use "the studio's return to its own long-running series" - fine. Need avoid other websites. No Polygon mention. Good. Need "no quotes" - we don't have direct quotes. The plan says include relevant quotes or statistics. We can use statistics like "three-minute cinematic" and "seven months" and "the seventh mainline game". That's enough. Need maybe mention "Lord of Chaos is the creator of demons trapped in Tartarus" - yes. Need maybe make the "skeptical note" more prominent. Yes. Need ensure conclusion has specific heading, not "Conclusion". Use "The story has already begun". Good. Now, the final answer should ONLY contain the article text in markdown, no preamble. The system prompt says "Output ONLY the revised article text in clean markdown format. Do NOT include any preamble, meta-commentary, or notes about what was changed." So we'll output exactly the article. Double-check "Title: Divinity fan decodes hidden Elder Futhark runes in Larian's trailer - and may have found the game's villain". There is a hyphen with spaces. That's allowed. Could also use colon. Fine. Need maybe avoid "world premiere" with hyphen? We have "world premiere" as noun in Section 1. Good. Need check "Elder Futhark" spelling. Yes. Need maybe add "It is the best lead yet into Divinity's cryptic next chapter." Good. Now, let's think about the meta-commentary that was included in the user message about "Editorial Feedback" - Should we address it? The system prompt says to base revision on editorial feedback, but no real feedback exists. Given "Current Draft" is incomplete, the best is to deliver the finished article. But maybe we should incorporate the implied feedback from the "Editorial Feedback" text? Let