A deep dive into the RuneLite HD shutdown controversy, exploring community backlash, developer response, and what this means for game modding.
RuneScape shut down HD Mod
The gaming community was rocked when Jagex, the developer behind the long-running MMORPG RuneScape, issued a cease-and-desist order for the RuneLite HD mod mere hours before its scheduled public release. This decision wasn’t just about blocking a graphical upgrade; it was perceived as a direct attack on years of passionate, unpaid work by a dedicated community member known as ‘117’. The mod aimed to revitalize the classic, albeit dated, visuals of Old School RuneScape (OSRS) using the open-source RuneLite client framework, a tool widely used by the player base.
The abrupt termination of RuneLite HD ignited a firestorm of criticism across forums, social media, and in-game channels. In a surprising and rapid concession to community pressure, the Old School RuneScape development team announced plans to collaborate with 117 and Adam1210, the RuneLite project lead, aiming to integrate the mod’s vision as an interim solution while Jagex develops its official graphical overhaul.
The landscape of game modification has fundamentally shifted. While studios like Valve and CD Projekt Red have famously embraced modders, sometimes hiring them or funding their projects, other companies maintain a more guarded stance. The case of 117 and RuneLite HD starkly illustrates this tension. Despite creating a highly anticipated project that promised to enhance the player experience and potentially retain or attract users, 117 found his work blocked at the final hurdle. This rejection catalyzed the community, transforming disappointment into organized action almost overnight.
The Modder’s Perspective and Rejected Compromise
In a detailed Reddit post, 117 revealed that Jagex contacted him on September 5th, just one day before the planned September 6th launch. The company cited its own, undisclosed plans for a visual upgrade to Old School RuneScape. Understanding the corporate position, 117 didn’t just protest; he proactively proposed a middle ground.
“I presented a solution to delay my project’s integration into RuneLite until Jagex’s official release was ready, preventing any direct competition. Furthermore, I offered Jagex collaborative control over the artistic direction and visual style of RuneLite HD to ensure alignment with their brand vision,” he explained. “Their flat refusal was devastating. After countless hours of development, I am deeply frustrated and heartbroken that I cannot deliver this labor of love to the community that supported me.”
This rejection of a seemingly reasonable compromise is a critical lesson for modders. Always document communications and have a clear, written proposal for collaboration ready. Companies may be more receptive to a structured partnership proposal than a simple request for permission.
RuneScape fans organize protest in-game
The community’s response was swift and remarkably coordinated. News spread through Reddit, Discord, and Twitter, culminating in a planned in-game event.
YT/RuneScape Historian
The peaceful sit-in at Falador Square demonstrated the player base’s collective strength and organizational capability. Players from across the game world converged on Falador Square, the capital of Asgarnia, not for combat or trading, but for a silent, mass sit-in demonstration. This virtual protest served as a powerful visual representation of player unity and dissatisfaction, completely overwhelming the local chat channels with messages of support for 117.
The chat was flooded with coordinated messages, most notably the slogan “we could be rioting in HD #Free117”. This hashtag became the unifying cry of the protest, repeated endlessly as a clear, direct message to Jagex about what they had taken away. This showcases an effective protest strategy: a simple, repeatable slogan that encapsulates the grievance.
Community Solidarity and Lasting Impact
The Falador Square protest was more than a momentary gathering; it was a case study in digital activism. It proved that an online community, when united by a common cause, can generate tangible pressure on corporate decision-makers. The event was peaceful, focused, and leveraged the game’s own social spaces as a platform for dissent, setting a precedent for how player communities can advocate for themselves.
Thomas the Tank Engine returns to terrorize Morrowind as modder mocks Mattel crackdown
Hollow Knight Silksong’s most controversial feature has already been fixed by modders
Player with 35,000 hours leaves negative Steam review and asks for refund
Old School RuneScape devs respond to protest
RuneScape
The official response from the Old School RuneScape team marked a significant reversal, promising collaboration after seeing the community’s unified stance. The sheer scale and passion of the protest achieved its goal with astonishing speed. Within a single day, the Old School RuneScape development team issued a public statement. “We make mistakes,” they acknowledged. “We are human, and we are now correcting our approach.” They committed to working with both the RuneLite team and 117 to find a unified path forward for the HD visual upgrades.
This rapid turnaround highlights a crucial dynamic in live-service games: developer accountability. 117 himself, despite his frustration, had expressed a willingness to collaborate, emphasizing a shared goal of improving the game. The incident ultimately forced a more open dialogue, suggesting that future modding projects for OSRS may begin with earlier, more transparent communication between creators and Jagex to avoid similar clashes.
No reproduction without permission：SeeYouSoon Game Club » Jagex backtracks on Runescape HD mod after massive backlash A deep dive into the RuneLite HD shutdown controversy, exploring community backlash, developer response, and what this means for game modding.