Fluxer Moderation Bot
Netrcol gives Fluxer moderators ban, kick, timeout, warn, clear, lock and slowmode commands, plus 12 AutoMod rules for links, invites, spam, mass mentions, caps and more. Repeat offenders can be escalated automatically to a warning, timeout, kick or ban. A separate Security module adds anti-raid and anti-nuke limits, a minimum account age and a honeypot channel.
The most-voted bot on FluxerList (171 votes, all time) and on Fluxer Bot List (45 votes in October 2026), rated 4.8/5 from 5 FluxerList reviews.
Give your moderators a clear workflow
A growing community needs a consistent way to handle disruptive messages and member behavior. Netrcol brings manual moderation and automatic content filtering together so staff can intervene when judgment is needed and configure rules for recurring problems. Use it for a small community with a few trusted moderators or a busy server with separate staff responsibilities.
Explore moderation settingsAct with moderation commands
Use ban, kick, timeout and warning commands when an incident needs a staff decision. Message cleanup, channel locking and slowmode help moderators manage a conversation as it develops. Configure which commands are available to your server, and review the permissions each action needs before giving staff access.
See moderation commandsFilter recurring message problems
AutoMod checks messages against the rules you enable. Configure filters for unwanted links, invites, repeated mentions and other disruptive content, with thresholds and exceptions that fit your community. Escalating penalties can respond to repeated violations. Start with a small set of rules and verify their behavior before broadening enforcement.
Configure AutoMod rulesConfigure server protection separately
The Security module handles server-level events rather than ordinary message filtering. Anti-raid settings monitor bursts of joins; anti-nuke settings monitor dangerous administrative activity. These protections depend on the thresholds, actions and exceptions you configure. Log-only settings are useful when reviewing behavior before enabling enforcement; no bot can guarantee that every incident will be prevented.
Explore the dashboardKeep an understandable record
Send relevant activity to chosen log channels so staff can review events without mixing every category into one conversation. A practical setup is to choose a staff log destination, enable the rules you need, test a controlled example and inspect the resulting message. Logging and moderation remain independently configurable.
Read about server logsCheck permissions and role hierarchy
Netrcol can only perform actions permitted by Fluxer. Grant the permissions required for the enabled commands and log channels, and place its role appropriately above roles it must manage. Restrict staff access deliberately. Missing permissions or an unsuitable role position can prevent enforcement even when a rule is enabled.
Check required permissionsFluxer API: role hierarchy rulesDoes AutoMod act on moderators and administrators?
Never on the server owner or on members with the Administrator permission. Other staff can be exempted by role, and each rule can also skip chosen channels and categories.
Set rule exemptionsHow do escalating punishments work?
You add steps such as a 30-minute timeout at 3 violations and a ban at 5. Each step fires at 1 to 50 violations with a warning, timeout, kick or ban; a server can have up to 20 steps, and Netrcol caps a timeout at 28 days.
Configure automatic actionsWhat is the difference between AutoMod and the Security module?
AutoMod checks each message against its 12 rules. Security watches the server instead: bursts of joins, mass bans, kicks or channel deletions, accounts younger than a minimum age, and posts in a honeypot channel.
Explore the dashboard