Instead Jagex may get more involved with runelite and choose a Microsoft style solution to open source development.
I do not think they'd necessarily need to OSRS gold manually accept plugins should they design the new customer appropriately. WoW has had a mostly unregulated add-on community (which are effectively the wow equal of Runelite plugins) because the very early days and Blizzard has just needed to manually break add-ons on a small number of occasions.
There is a huge difference between the addon API that WoW supports along with the"api" that's accessible through the runescape client.
The former has specific actions that addons are and aren't permitted to take, activities that need hardware events (e.g. a click/button press), etc.. Runescape, on the other hand, is that the wild west. Anything goes. It is all potential. That is the reason why manual approval will likely always stay necessary, at least until Jagex invests a couple million to an addon framework.
Well stated, even if the runescape'api' may be more tightly locked down - they'd soon run into precisely the same problem blizzard experiences. Lets say you want to prevent plugins that auto-draw on the Buy Runescape gold floor during boss fights, however also the'draw on x tile' API can also be used re - you can't simply remove the API callback without breaking, let us say manual ground markers.
Blizzard haven't really ever prohibited addons, with the exception of some addons that were attempting to conceal behind a subscription based cover wall. Short of writing anti-virus like code inside the sport which finds banned source code, theres nothing they can do except split the API.
Instead Jagex may get more involved with runelite and choose a Microsoft style solution to open source development.
I do not think they'd necessarily need to OSRS gold manually accept plugins should they design the new customer appropriately. WoW has had a mostly unregulated add-on community (which are effectively the wow equal of Runelite plugins) because the very early days and Blizzard has just needed to manually break add-ons on a small number of occasions.
There is a huge difference between the addon API that WoW supports along with the"api" that's accessible through the runescape client.
The former has specific actions that addons are and aren't permitted to take, activities that need hardware events (e.g. a click/button press), etc.. Runescape, on the other hand, is that the wild west. Anything goes. It is all potential. That is the reason why manual approval will likely always stay necessary, at least until Jagex invests a couple million to an addon framework.
Well stated, even if the runescape'api' may be more tightly locked down - they'd soon run into precisely the same problem blizzard experiences. Lets say you want to prevent plugins that auto-draw on the Buy Runescape gold floor during boss fights, however also the'draw on x tile' API can also be used re - you can't simply remove the API callback without breaking, let us say manual ground markers.
Blizzard haven't really ever prohibited addons, with the exception of some addons that were attempting to conceal behind a subscription based cover wall. Short of writing anti-virus like code inside the sport which finds banned source code, theres nothing they can do except split the API.