Competitive Clan Tools

A RuneLite plugin for the Competitive Old School RuneScape clan. It connects members'
clients to the clan's own Discord bot for three purposes: account verification, a two-way
clan chat mirror, and a live clan event (bingo) board.

Features

Discord verification
Acts as the plugin's login. The member clicks Generate Link Code in the panel; the plugin
requests a short code from the clan bot and displays it. The member runs /link <code> in
the clan Discord to tie their RuneLite account to their Discord account. The plugin sends the
name it is already logged in as, so identity cannot be spoofed by changing a Discord
nickname. Until verified, the panel shows nothing.

Two-way clan chat mirror
Clan chat is relayed to a Discord channel, and messages from that channel are shown in the
member's game chat. Inbound Discord messages are rendered as ordinary game (system) messages
for display only — they are never submitted as player input and cannot trigger any game
action. Clan broadcasts (drops, raids, collection log, quests, diaries, level-ups) are
forwarded so the Discord side can display them richly; what qualifies as a broadcast is set by
the clan's own in-game Loot broadcast setting, not this plugin.

Live event board
The clan's current bingo event is displayed in the sidebar panel and an optional overlay:
a board whose tiles fill in as they are completed, plus team rosters and standings. This is a
read-only view polled from the bot; the plugin does not detect drops itself or act on the game.

Safety and privacy

• No automation and no game interaction. The plugin sends no key presses, mouse input, or
  menu actions. It reads chat and clan data for display and relay only. It complies with
  Jagex's third-party client guidelines.
• Data leaving the client is limited and purposeful: the logged-in character name (for
  verification) and clan chat lines (which are already shared with the clan, and are relayed to
  the clan's Discord by design). Nothing else is transmitted.
• Single endpoint. The plugin only ever communicates with the clan's own bot; the address
  is compiled in and there is no user-supplied URL field.
• Credentials are never entered into the client. Verification is code-based via Discord.
  The resulting session token is stored locally through RuneLite's own configuration storage.
• Member controls. Settings allow toggling the event overlay, in-game Discord messages, and
  event tile alerts.
• No new dependencies. All libraries used (OkHttp, Gson) are transitive dependencies of
  runelite-client; no third-party dependencies are added.

Build

build=standard. Builds cleanly against latest.release; resources are loaded via
ImageUtil.loadImageResource (getResourceAsStream), not getResource.