-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Share quests and stats to local API (Like RS3 Runemetrics) #8358
Comments
I dont think we should do anything else other than exposing local api to cover this, sending non-anonymized data to 3rd party do not sounds very reasonable. |
Yeah, the local API is probably the more reasonable answer. |
I just updated the post to have more of a focus on the local API |
+1. Just being able to export the quest list as JSON would give me enough value. |
I added a local api plugin on the pluginhub awhile ago which export stats, if you want to use that/expand on it. |
The wiki people have developed |
I believe this is sufficiently covered by the previous comments. Any further coverage should be supplied via hub plugin. |
Is your feature request related to a problem? Please describe.
Some RS3 wiki pages (Quest guides & Calculators) have an option to automatically import user data about quests completed, allowing Javascript on the wiki to check off completed quests and required levels automatically. It's a small convenience that goes a long way.
Example pages can be found below.
Describe the solution you'd like
Players would be able to opt-in to share their data to an API, like the Runemetrics API, the wiki guys (and other services) could then use that data instead.
Describe alternatives you've considered
A way to link a Runelite account to a oldschool.runescape.wiki account, either within the existing wiki plugin or as a new plugin. This plugin would read player stats; quests; and diary status from the client and then pass them to the wiki, where the wiki devs would handle the data on their end.
This would require collaboration with the wiki developers and be more restrictive.
Additional context
The text was updated successfully, but these errors were encountered: