The forks had to update the clients themselves and it seems now that jagex can detect these differences. Then Runelite had to be (partially!) closed-source in order to be compliant with Jagex's ruling and from there the forked clients started to differ with each update made from the closed-source section of RL. Which is true, but different from the forks the runelite plugin developers use today.īack when runelite was still open-sourced, many clients were created based on forked version of rl - they tweaked and edited certain things and basically created a different identity on the same code base. But so far, unless I missed something, Jagex has not made a statement on it. There are ways for Jagex to navigate this in a way that leaves honest devs alone while still banning waves of cheaters. I don't mean to present this as an impossible technical challenge. I've heard that RL doesn't let plugins do things like auto click, which is good if true, but there are still things that plugins can physically do but are against the rules. If the only criterion for client-based banning is an unmodified base client, cheat clients will just become the base client with cheat plugins added on. More importantly, cheat clients can again just do this too. If we end up in a situation where only official RL devs are allowed to do work on the base client, while everyone else is allowed to create plugins, well, it goes against FOSS principles which I feel very strongly about, but it wouldn't be the end of the world. The base Runelite itself needs dev work too, and that does require running a modified client. It's true that while developing plugins, the base Runelite is the same as the release version (albeit built locally). I saw some comments about Jagex detecting unmodified Runelite instances. After all, nothing is stopping a cheater from developing a cheat plugin and using it themselves, in the exact same process a good developer would use. I don't see how this blanket ban can apply to cheaters while keeping honest plugin devs safe. If your instinct is to say "just submit it to the Plugin Hub", it doesn't work that way - it can't be submitted to the Plugin Hub until it's made, and the development process unavoidably involves using it ingame. In order to create new plugins, developers must play the game using them. In order to ban them, Jagex would have to detect when players are using something other than the official release of Runelite. Here's why I'm worried:Ī lot of cheat clients are just unofficial versions of Runelite. My concern is that complete nobodies with plugin ideas (which is where most plugins on the hub come from) will be stifled due to the new client rules. This post does not concern people like Adam who are officially affiliated with Runelite. Runelite is open source, which means anyone can download the source code and contribute to development. For more information about account bans, click here. Feel like sharing? Please censor names wherever possible. Report abuse in game and contact Jagex for serious issues. This is not the place to accuse players of wrongdoing. No "Advice Animals" or other image macros. The body of your submission must be related to Old School RuneScape.ĭon't break or promote breaking Jagex/OSRS T&C. The mods here at /r/2007scape aim to make this the number one place to have fun, meet friends, and create memories! Rules of the land Welcome to /r/2007scape, the place to discuss Old School RuneScape! Submit a link Submit a text post Submit a game suggestion
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |