Add Final Boss clan plugin

[orgonag]

Plugin: Final Boss

Clan tools for the Final Boss OSRS clan.

Features

• Clan Verification — Verifies membership via the Wise Old Man API (Group 1055)
• Drop Logging — Logs valuable drops (1M+ GP) to a shared Supabase database with Row Level Security
• Discord Notifications — Optional webhook for drop alerts in Discord
• Looking For Group — Find clan members to group up with (8 activity types, list/grouped views)

Technical Details

• Uses injected OkHttpClient for all HTTP calls (WOM, Supabase, Discord)
• All network calls run on background threads via ScheduledExecutorService
• No reflection, no raw threads, no internal API access
• Supabase anon key is intentionally public — protected by RLS policies
• BSD 2-Clause license

Repository

https://github.com/orgonag/fbclan-plugin

[runelite-github-app]

New plugin fbclan-plugin: https://github.com/orgonag/fbclan-plugin/tree/4a4a3c285ef592c7884ae6d40844ab1d3c2689d4

[runelite-github-app]

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

[riktenx]

Please add build=standard to runelite-plugin.properties.

[orgonag]

Added build=standard to runelite-plugin.properties and updated the commit hash. Thanks for the review!

[orgonag]

what would be required in order to get the 3rd party database to be reviewed by runelite to drop the warning? There are folks in my clan that would likely not use the plugin because of the warning; wondering if there is 1. a process for review of the 3rd party datavase or 2. any other way to rewrite the plugin with the lfg functionality intact. i dont know how that would even be possible without writing data somewhere

[riktenx]

There is no such process, because as the warning states, the server is not controlled by us. Reviewing the database (not sure what that means in this context, if you're talking about the code, verifying the state of the deployment, etc.) does not convey any sort of verification because we don't have sole control over the server and what it's doing at all times.

Essentially the only way to not have that warning is for your plugin to not have that functionality.

[riktenx]

FYI I reviewed the rest of your plugin and it was fine but given your question above I'm not sure if you intend to proceed or not, so I'm holding off on merging for now.

[orgonag]

I understand what you have said; that lfg functionality is important but the warning always sours some people. its not a deal breaker thought

I would like to still progress with the merge. thank you