Awesome Fluxer

​

Source

• awesome-fluxer/awesome-fluxer

​

Why keep a local copy

The external list is useful both for developers building on Fluxer and for support staff answering “is there a library or tool for this?” questions. Keeping a copy in the docs gives self-hosted and offline operators a stable starting point.

​

Snapshot categories

The upstream list currently groups projects into:

• libraries
• bots
• tools
• bridges
• theme tools

​

Libraries

The community list includes SDKs and wrappers across several languages:

• Python: Fluxer.py
• C#: Fluxify, Fluxer.NET
• JavaScript and TypeScript: Fluxer.JS, Fluxer.ts
• Go: FluxerGo, Lightning
• Rust: fluxer-rust, Fluxer.RUST, fluxer-neptunium
• Dart: official Dart SDK

For bot development, the most directly useful entries are the JavaScript, TypeScript, Python, Go, and Rust libraries that already model the API and gateway.

​

Bots

The upstream list also tracks notable public bots, including examples in moderation, FAQ, counting, music, and community management. Examples from the current snapshot include:

• Fluxy
• Bloo
• Nevi
• Tags
• Counting Bot
• flux.fm
• Remix
• Vinto
• Functious

These are useful references for command design, onboarding, permissions, and how people are already using Fluxer bots in the wild.

​

Tools

Notable tools currently listed include:

• Fluxbase for discovery
• Reaper Tool for Discord-to-Fluxer migration
• fluxer-rpc for status mirroring
• BetterFluxer and Reflux for client customization

For support and docs work, migration and discovery tools are especially worth surfacing.

​

Bridges

Bridge projects in the upstream list include:

• Fluxcord
• Bifröst
• Bolt

These matter if your users are migrating from Discord gradually rather than all at once.

​

Theme tools

The current list also includes theme tooling such as:

• fluxer-snippets

​

What is most relevant for the support bot

For the bot itself, the most useful categories are:

• libraries, because they may reduce the amount of Fluxer-specific transport code you need to maintain
• bots, because they show established command patterns and common community expectations
• tools, because the bot can point users to migration or discovery tooling
• bridges, because users often ask how to run Discord and Fluxer side by side during a transition

​

Recommended bot-facing uses

If you want the support bot to make practical use of this ecosystem data, the best starting points are:

• link users to the local docs page for community ecosystem references
• link operators to bridge and migration tools during onboarding
• link developers to SDK pages when they ask how to build Fluxer bots

​

Canonical upstream list

• awesome-fluxer/awesome-fluxer