From e6b471dc01c7473d14f512dea6cb7c5cdb075718 Mon Sep 17 00:00:00 2001 From: Rasmus Karlsson Date: Sun, 5 Jul 2026 09:01:13 +0200 Subject: [PATCH] document minimal changes that maybe done in plugin takeover policy --- Plugin takeover policy.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Plugin takeover policy.md b/Plugin takeover policy.md index 321e61a..138776b 100644 --- a/Plugin takeover policy.md +++ b/Plugin takeover policy.md @@ -14,6 +14,7 @@ Becoming a collaborator on an existing plugin is preferred over having the plugi 2. If the author is unavailable, after 7 days send a pull request to the pluginhub changing the plugin to your repository, but *don't change the commit hash*. You can accomplish this via forking the old repository. Mention in the pull request description that you would like to takeover the plugin. We will attempt to contact the author via GitHub, and if they are unavailable, assign the plugin to you after a period of 2 weeks.\ \ -Also make sure you've enabled issues for your fork of the plugin, so users can report problems with the plugin you've taken over. This can be done via the `Settings` tab at the top of the repo, and then scrolling down to the `Features` section, and checking the `Issues` box. +Also make sure you've enabled issues for your fork of the plugin, so users can report problems with the plugin you've taken over. This can be done via the `Settings` tab at the top of the repo, and then scrolling down to the `Features` section, and checking the `Issues` box. +If the plugin fails to build, you may update the commit hash to make the minimally required changes for the plugin to function again. 3. As a special exception, plugins which have been deleted, disabled, or incompatible for more than 60 days may be immediately claimed. We have source archives of pluginhub plugins, if you need access to the source of a deleted plugin, make a post in `#runelite` on Discord and someone will be able to fetch it for you.