A Hilarious Glitch Adds a Surprise Power to Mimir in God of War Ragnarok's Valhalla DLC

God of War Ragnarok, celebrated for its 2022 release with over 15 million copies sold, introduced the Valhalla DLC, a free expansion announced by Sony at The Game Awards. Taking inspiration from the roguelite genre, Valhalla features Kratos battling diverse enemies and acquiring both temporary and permanent buffs. However, players have stumbled upon an amusing glitch in the DLC, giving Mimir an unexpected new power.

Reddit user dazavstark shared a video showcasing this entertaining mishap in the Valhalla DLC for God of War Ragnarok. In the footage, Mimir stands up independently and engages in conversation with Kratos, seemingly unaffected by the need for external support. The clip does exhibit other anomalies, such as muted dialogue, with Freya and Mimir's voices absent. Despite the absence of spoken words, the video maintains clear sound effects, prompting dazavstark to exit to the main menu in an attempt to resolve the issue.

reddit_https://www.reddit.com/r/GodofWar/comments/18jo3dq/didnt_know_mimir_could_do_that/

This quirky occurrence seems to be a shared experience, as multiple players on Reddit have reported encountering the same problem. One user narrates that the glitch occurred after their first death in God of War Ragnarok Valhalla, while another mentions struggling to watch the cutscene despite repeated console restarts. Some resorted to viewing the scene on YouTube, but others did manage to witness it after restarting God of War Ragnarok. Evidently, this bug appears to be widespread, affecting several gamers during their Valhalla DLC gameplay.

Santa Monica Studio, the developer, released a post-launch update for God of War Ragnarok Valhalla, addressing various bugs within the DLC and implementing general improvements and balance changes. These fixes include instances where Kratos would fall through the game world, texture loading issues, and audio discrepancies during specific cutscenes. Given that the footage was likely captured before this update, it suggests that the issue may have already been resolved in the latest version.