-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Create one-shot #9794
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
base: master
Are you sure you want to change the base?
Create one-shot #9794
Conversation
|
This plugin requires a review from a Plugin Hub maintainer. The reviewer will request any additional changes if needed. Internal use only: Reviewer details Maintainer details |
|
Not a full review but: |
|
Regarding dink plugin, we're not using it for a few reasons
Regarding the scouting feature, i'm not sure if it's breaking terms |
Dink supports this
Dink supports this
Dink supports this |
There are ways for this feature to be abused outside of your intended use case. |
|
@Felanbird HCIM status loss vs. generic death events Custom screenshot timing and payloads Custom embed metadata (e.g., clan rank icons) Centralized webhook handling and abuse prevention Because of these limitations, the linked documentation doesn’t demonstrate how Dink can be used to achieve the same behavior without either changing the requirements or re-implementing significant logic outside of Dink. I’m very open to making changes if there are specific policy or technical constraints that need to be met, I just need clarity on what those are. @tylerwgrass
Thank you in advance |
|
Leaving edge cases will make it much harder for us to verify that it can't be used for scouting than just having it removed. You should assume that anyone who installs this would have access to all the features. From a non-rules enforcement perspective, you would kinda be shooting yourself in the foot by allowing any player to easily find HCIMs. |
|
It's as @tylerwgrass said above, there's no reasonable restriction on this functionality that we can enforce because edge cases will always be abusable (e.g., if you disable wilderness, people will just park at the ditch and scout HCIMs going in) or Jagex will add new content that the restrictions don't immediately cover etc. As submitted we cannot accept this due to the scouting feature. If you are not willing to remove the scouting feature we will need to close this PR. |
will remove it then, thanks for reply |
removed hcim scout function
removed unnecessary imports
|
@tylerwgrass @riktenx |
|
This plugin uses reflection, which is not permitted on the pluginhub. Please remove your use of reflection. |
removed use of java.lang.reflect.*
|
@Adam- I’ve removed all direct uses of java.lang.reflect.* from the plugin and reviewed the codebase to ensure no reflection is being used. The only remaining reflect import is com.google.gson.reflect.TypeToken, which is used solely for JSON deserialization via Gson and does not involve runtime reflection against RuneLite or client internals. If there’s a specific class, method, or commit that still appears to use reflection, I’d really appreciate a pointer so I can address it promptly. |
|
Hello, is there anything else I need to modify? |

one shot clan plugin
contains integration with hiscores, wiseoldman and cloudflare for discord webhooks
main functions are clan rankings on hiscores, discord embeds with new collection logs, achievements, etc, and mod tools for clan management