On 30 September 2019, Jagex published another news post regarding third party clients, outlining the features within a third party client that would be unacceptable and could result in a player being banned from RuneScape. We cannot allow for botting to become an even easier pursuit with our code in opensource, without our permission.Īn update to the news post later that day stated that Jagex had temporarily paused legal action against RuneLite after the developers agreed to make parts of the RuneLite client, specifically those relevant to de-obfuscating the RuneScape client code, closed-source. Whilst this may seem heavy handed, if ignored it's entirely plausible that this code could make its way into the hands of developers seeking to adapt it to create botting scripts, or developers who would implement game-breaking features. Specifically, the sharing of tools used to deobfuscate Old School RuneScape code, and then re-publishing said code. We did this because we believe RuneLite was and is infringing Jagex's IP rights and damaging the game which goes against our commitment to our community to maintain the integrity of the game. On 16 May, Jagex published a news post about RuneLite, stating:ĭuring a pre-arranged meeting with the RuneLite developer we outlined our concerns with the nature of the client and asked for its immediate closure without the need to escalate any legal action against a dedicated Old School player.
In 2018, Jagex approached the main RuneLite developers regarding alleged copyright infringement, requesting that the client be taken down by the end of the week commencing 14 May. As RuneLite is open source, it has allowed community developers to contribute their own plugins and improvements to the client over many years, as opposed to the closed source development of the official game client. Development on RuneLite began in 2014, with an initial version being released in May 2016.
0 kommentar(er)
