Source: RuneScape (Jagex). Verified against multiple sources; datamines and reports are labelled as such, not stated as fact.
Jagex Made the Fan Tools Official
Quest Helper becomes an officially supported plugin, built jointly by the three authors of the competing fan versions.
Every MMO eventually has to decide whether players get to build tools on top of its client. Jagex answered yes, then went further and put the authors of the three competing fan versions on the same team.
On 6 August 2026 Jagex published "API Plugin Previews & Quest Helper" on the official RuneScape news site, the second public checkpoint for the RuneScape API Project it first outlined in June 2026. Quest Helper leads it. Jagex calls it one of the most requested quality-of-life features from RuneScape players for years, and it will ship as an officially supported plugin.
The build team is the part worth staring at. Zoinkwiz wrote the OSRS Quest Helper, JosTheFarmer wrote BOLT's Quest Helper, Techpure wrote Alt1's Quest Helper, and all three are now building the official one together. Jagex describes the goal as keeping quest guidance inside the game instead of on a second monitor.
Seven more plugins are in preview: Tile Markers, Menu Entry Swapper, Agility Helper, Home Planner, Farming Timers, Fairy Rings and Runic Attune. Jagex says they are still in progress, feedback is running through dedicated Reddit and Discord discussions, and it reported progress on submission guidelines and moderation for the API alongside closer work with plugin creators.
Read the screenshots instead of the announcement. Farming Timers pins live countdowns over the herb patches at Manor Farm, so a fly trap reading 3:18:04 sits in the world rather than in a spreadsheet. Fairy Rings turns the teleport network into a searchable panel with favourites, number-key binds and a 47/58 discovered counter. Runic Attune stands at the Soul altar and does the money: 1035gp profit per rune, a 1000.00gp baseline against 3194.77gp boosted, plus a prompt telling the player to charge one essence so they reach the 50th trip faster.
On SteamRuneScapeTrailer, screenshots, and the full store pageRiot's Answer, Nine Days Earlier
On 28 July Riot Developer Relations closed League Classic data to the Riot API and asked trackers to stand down.
Riot's most recent public decision on the same question went the other way. On 28 July 2026 Riot Games Developer Relations posted that League Classic match history data will not be available via the Riot API, and asked that League Classic data not be aggregated or displayed to users in any form, to preserve the spirit of the mode.
It was not a blanket shutout. The same post said League Classic would be supported as a valid map type in Riot's Tournament API, so community-run tournaments keep their endpoint. Organised play gets served. The op.gg-shaped layer does not.
The post has been viewed more than 1 million times, which is a lot of attention for a developer-relations note about an API field. It is a decent proxy for how much people care about the tooling layer, right up until the moment it disappears.
| The question | Jagex, RuneScape | Riot, on the record |
|---|---|---|
| Fan tools in the client | Officially supported. Quest Helper ships as a sanctioned plugin, with more still in preview. | League Classic match history data will not be available via the Riot API. |
| Who writes them | Zoinkwiz, JosTheFarmer and Techpure, three rival authors, building one version together. | Riot asked that League Classic data not be aggregated or displayed to users in any form. |
| Where third parties still fit | Feedback on the previews runs through dedicated Reddit and Discord discussions. | League Classic is supported as a valid map type in Riot's Tournament API for community-run tournaments. |
| Moderation | Jagex reports progress on submission guidelines and moderation for the API. | Not revealed |
Neither studio is being lazy about this. Jagex is taking on a moderation cost it could have avoided, and Riot is protecting a mode it thinks aggregation would flatten. What actually differs is where the tooling ends up living: inside the product behind a submission process, or outside it in an overlay scene the developer cannot see or design around.
What This Means for the Riot MMO
Two live answers to the same question, and the Runeterra MMO has not given its own.
The Runeterra MMO inherits this question, and it lands harder there than it does in League. A MOBA's third-party layer is mostly post-match: builds, win rates, a scoreboard you read afterwards. Raid-scale PvE is live. Timers and callouts are not analysis, they are input, and they arrive while the fight is still happening.
World of Warcraft settled this by accident and has been living with the result ever since. DBM and WeakAuras did not make raids easier. They moved the floor, and encounters got tuned to the new floor. Anyone who has been asked to import a WeakAuras string before a first pull knows how long ago those tools stopped being optional.
That is the trap in front of Riot. You tune for players who have timers and callouts, or you tune for players who do not. You cannot tune for both, and the call has to be made before the encounter team writes its first boss.
You tune for players who have timers and callouts, or you tune for players who do not.
- Riot has to pick a side eventually: sanction an addon API and staff the moderation, or lock the client and accept an unofficial overlay scene it cannot see.
- Runic Attune is the exact failure mode Riot named for League Classic, running in a different game: a fan plugin computing optimal gp per hour live inside the client.
- Jagex's route turns the strongest community tool authors into collaborators. Riot's July stance turns the equivalent people into a compliance problem.
- Encounter design is downstream of the answer. Tune for players with timers and callouts, or tune for players without them.
- An official API is a staffing line, not just a technical one. Jagex is publicly working on submission guidelines, which is the part a locked client never has to pay for.
The Runic Attune preview is the thing Riot named in July, wearing a different game's UI. A community plugin computing optimal gp per hour live inside the client is the RuneScape version of data "aggregated or displayed to users in any form". Jagex looked at that screen and shipped it with its own name on it.
Riot has also been recruiting from the end of the genre where the overlay is assumed. We covered the studio handing traversal work to a WoW veteran, and RuneScape has already set a bar Riot will be measured against on player housing. People bring their instincts with them, and those instincts were formed in a game where everyone raids with a second UI layer running.
Here is the encounter, if you want to look at one. Riot has already filmed a Runeterra fight at the scale a raid tier would need.
Ruination, the Season 2021 cinematic, plays like an encounter storyboard. The Black Mist takes a coastline in one shot. A war party forms up in front of a citadel that is already burning. Nothing in frame is a solo problem, and every beat in it is a mechanic somebody would want a timer for.
The canon underneath it is already shaped like content. 
Viego forced his way into the Vaults of Helia to reach the Waters of Life, the breach loosed the Black Mist, and the Blessed Isles became the Shadow Isles. 
Thresh was one of the keepers of that vault before the artifacts he guarded finished with him. A wing, a boss, an add and a reason, written years before anyone asked whether the fight needs a timer bar.
None of that is a claim about the game. Riot has confirmed exactly one thing about the MMO: it is set in Runeterra. Which regions, how much of the map, what era, which platforms, how it is sold, all unrevealed. The map below and the crests under it show the fiction Riot is drawing on, not a starting area.
Those three crests are a fair sample of the problem. Bilgewater is a harbour town run by 
Gangplank money and 
Illaoi's faith. Mount Targon's summit is an impossible climb that few who attempt it survive. The Shadow Isles are the Mist itself. Different encounter grammar in each, and one addon policy has to hold across all of them.
Studios that publish their reasoning tend to get better arguments back. ArenaNet did it when it published the exact reason a fifth playable species did not make Guild Wars 3. Jagex is doing it now by shipping unfinished previews and asking for notes. Riot's July post came from the same instinct pointed the other way: it explained itself, and then it closed the door.
Your Take
Should Riot's MMO ship an official addon API, or keep the client locked the way League is?
What's Next
The next answers to the same design questions are already in our coverage.
Reported from RuneScape (Jagex) and corroborating coverage. The MMO read is ours and clearly speculative. Analysis by RuneGrove.
