revenge-plugins/README.md

revenge-plugins

A collection of plugins for Revenge, the Discord Android client mod.

Installing a plugin

1. Open Discord with Revenge installed, go to Settings → Plugins.
2. Tap the + button and paste the plugin's install link (see below).
3. Enable it.

Plugins

Moderation & appearance

Plugin	Status	Description	Install link
Staff Tags	Rebuilt	OWNER/ADMIN/STAFF/MOD-style tags next to members, computed from real server permissions. Per-tag text, colors, gradients, and visibility.	https://everestmcarthur.github.io/revenge-plugins/staff-tags/
RoleColorEverywhere	Revived	A member's top role color shown in mentions, the typing indicator, voice channel names, member list role headers, and optionally message text.	https://everestmcarthur.github.io/revenge-plugins/role-color-everywhere/
PronounDB	Revived	Shows a user's pronouns in their profile, if they've set them at pronoundb.org (nothing to configure in the plugin itself).	https://everestmcarthur.github.io/revenge-plugins/pronoun-db/

Productivity

Plugin	Status	Description	Install link
Message Snippets	New	Save reusable text and send it with /snippet <name>. Manage snippets in-app or with /snippet-save, /snippet-delete, /snippet-list.	https://everestmcarthur.github.io/revenge-plugins/message-snippets/
Reminders	New	/remind 20m Walk the dog - fires while Discord is running. Can't wake the app from fully closed (no native notification access from a JS plugin).	https://everestmcarthur.github.io/revenge-plugins/reminders/

"Revived" means the plugin previously existed elsewhere, stopped working after a Discord/API update, and has been rebuilt here. "Rebuilt" means it's a from-scratch reimplementation of a previously-broken plugin with expanded features. "New" means it didn't exist anywhere in the Revenge/Vendetta plugin ecosystem before.

Why some of these broke before, and what's different now

Both Staff Tags and RoleColorEverywhere previously failed completely (not just partially) when a single internal Discord component got renamed - one bad lookup threw during setup, which crashed the plugin's onLoad before it could apply any of its other patches. Every rebuilt/revived plugin in this repo isolates each patch surface behind its own guard, so if Discord changes one internal again, only that specific surface goes quiet instead of taking the whole plugin down. PronounDB's break was simpler: its old data source was a PronounDB API version that Discord had nothing to do with - PronounDB itself shut it down (HTTP 410) - so it's been migrated to their current v2 API.

Building locally

npm install
npm run build

Output is written to dist/<plugin>/.

Contributing

Issues and PRs are welcome, especially if a Discord update breaks a lookup a plugin relies on - findByName / findByProps targets can and do change without notice.