Bundled plugins

These plugins are included in the build’s catalog. Install and enable them from Fluxer Settings → FluxPlugs → Plugins. They are initially disabled.

Outlines

Highlights interface element borders and provides a configurable keyboard toggle. Use its settings to adjust the feature, then disable it to remove its interface effects.

NekoSkins

Changes the sprite sheet used by Fluxer’s existing Neko cat. Enable the cat in Fluxer first, then set Custom Neko sprite URL in the plugin’s settings.

Use a public HTTPS PNG sprite sheet accepted by the image service. Clear the URL or disable the plugin to restore the default skin. NekoSkins requests settings, UI, image, and styling permissions.

Virus Check

Adds FluxPlugs → Virus check to posted file-card context menus. After a disclosure, it opens a VirusTotal URL lookup in your default browser.

The full attachment URL is shared with that website and may contain access parameters. The plugin does not download or upload the file, and opening a report does not guarantee a scan or a safety verdict. Inline media and unsent uploads are unsupported.

SheriffBadge

Shows staff badges (Owner, Admin, Mod, Helper, Dev) next to names in communities: in chat, the member list and its role groups, profiles, and a community’s role settings. It recognises staff roles by name (“Mods”, “Head Admin”), by colours you list, and by permissions such as Administrator or Ban Members.

By default each person gets only their highest badge. Set Badges per person to show up to five. Each tier’s label, icon, colour, name patterns and colour patterns are configurable, and Show in … settings pick where badges appear.

To give everyone the right badges, FluxPlugs asks Fluxer for the roles of people on screen with your account, a few at a time. Turn off Look up members’ roles to rely on what the page shows instead: member-list groups, profiles you open and name colours. SheriffBadge requests settings and badges permissions.

Fluxlation

Translates messages. Right-click a message and choose Translate: a section below the message shows Translated from the language and provider, the translation, and a Hide button. The original message stays as it is. If a translation fails, the section says why and offers Retry.

Translation provider picks the service:

• google (the default) and mymemory work without an account. Google uses an unofficial Google Translate endpoint and may rate-limit you. MyMemory allows more translations a day if you set MyMemory email. When one of the two is rate-limited or unreachable, Fluxlation tries the other.
• deepl, google-cloud, microsoft and libretranslate need your own API key. DeepL free keys (ending in :fx) work too. For Microsoft, also set Azure region unless your resource is global. LibreTranslate means libretranslate.com; self-hosted servers aren’t supported, because a plugin can only reach the servers listed in its manifest. Without a key, Fluxlation uses Google and tells you once.

Translate into takes a language code such as en, es or pt-BR; leave it empty to use your system language. Long messages are translated in part: roughly the first 1,500 characters, and the shown translation ends with “…” when it’s cut to fit.

Auto-translate is off by default. When on, it translates every message from others that you view and that isn’t in your language. The first time, it asks you to confirm: it sends the text of every message you view to the provider, and it can use up free quotas or get you blocked for a while. Declining turns the setting off. Fluxlation sends at most 20 requests a minute to free providers (60 with an API key), two at a time, and pauses for a minute, up to ten, with a notice when a provider starts refusing.

The API key is hidden on screen but stored unencrypted on your computer. Translated text goes to the provider you picked. Fluxlation requests settings, storage, UI, decorations, message text and network permissions, and connects to the translation services listed in its permission prompt.

FluxTime

Shows your Fluxer usage stats: active time today and in total, voice time and your top five voice channels, messages sent, the last 14 days as a chart of active and voice time, your busiest hours, your current and best streak of days with at least a minute of activity, and your longest session. Open it from Fluxer Settings → FluxPlugs → Usage stats, or right-click yourself and choose Usage stats. Fluxer’s user area at the bottom left has no right-click menu, so right-click your name on one of your messages or in the member list.

Only time Fluxer is actually in use counts as active: it must be the focused window, shown rather than minimized or closed to the tray, and you must have pressed a key, clicked, scrolled or moved the mouse in it within Idle after (minutes): 5 by default, 1 to 60. The idle wait itself isn’t counted, and a gap such as the computer sleeping adds at most about half a minute of active time. A session is active use with breaks shorter than the idle time.

Voice time counts while Fluxer shows you connected, even when Fluxer is hidden. Messages are counted as they appear on screen right after you send them: ones you send from another device count while that channel is open in Fluxer, and ones sent elsewhere don’t. Channel and community names show once you’ve opened that community in this session; until then you see ids.

Everything stays on your computer, and FluxTime makes no network requests. Reset stats, at the bottom of the page, erases everything after a second click. FluxTime requests settings, storage, UI, activity, voice, decorations and community data permissions. It draws no decorations; it uses them to notice your messages.

See developer examples for source links and implementation lessons.