Register System

Run a verification flow on Fluxer: keep unregistered members limited, assign the registered role once they confirm, and manage names as they join.

Topics: register, verify, member, gate, k, registrar, channel, join automation

Gate your server behind a verified/unverified role flow, so new members get full access only after they're registered.

Overview

The register system manages two role states: an unregistered role held by new members, and a registered role granted once they're verified. New members can be limited to a landing area until they're registered, at which point they receive the registered role and full access.

There are two ways a member can become registered, and they can be used together:

Staff registration is always available. Self-registration is an extra layer you switch on top of it — turning it on never takes the manual commands away, so staff can still register, correct, and reverse registrations by hand.

The fastest way to set it up is the setup wizard (!register setup). You can also configure it on Dashboard → Register or with the register commands. Netrcol needs Manage Roles, and its role must sit above both register roles — see Permissions & Roles.

Roles

The registrar role is optional. If you leave it unset, anyone with Manage Roles (or Administrator) can still register members — the role only exists to extend that ability to staff who don't have the permission.

When a member is registered, the registered role is added and the unregistered role is removed. Unregistering reverses this.

Note: The dashboard and the chat commands share the same configuration, so changes in one place apply to the other.

Setup wizard

Run !register setup (or !register-setup with no arguments) to launch a step-by-step wizard:

1. Register channel — mention the channel where the welcome message is sent.
2. Registered role — the role given to verified members.
3. Unregistered role — held by members who haven't registered (type skip to leave it unset).
4. Registrar role — staff who can register members (type skip to leave it unset).
5. Self-registration — answer yes to let members register themselves with a button, or no for staff-only.

Type cancel at any time to stop. The wizard requires Manage Roles, validates each answer, and runs a health check when it finishes. Answering yes at step 5 also posts the register button for you.

Prefer a single line? Use !register-setup #channel @RegisteredRole [@UnregisteredRole] @RegistrarRole — the channel can be placed anywhere among the arguments.

Register channel & join automation

When join automation is on, a new (non-bot) member who joins:

• receives the unregistered role, if one is configured and assign on join is enabled;
• triggers a welcome embed in the register channel, mentioning the registrar role so staff can verify them.

You can customise the embed text with an optional welcome message supporting the placeholders {user}, {username}, {server}, {memberCount}, and {staff}.

Self-registration

Turn it on with !register-self on #channel, at step 5 of the wizard, or on Dashboard → Register. Netrcol posts a message with a Register button in the channel you name; a member who presses it receives the registered role immediately and gets a private confirmation. Members can also run !register with no arguments, unless you switch that entry point off.

Turn it off again with !register-self off, which removes the button and leaves staff registration untouched.

Safety limits

Self-registration grants access with no staff member in the loop, so it is gated:

• Minimum account age — accounts younger than the limit you set are refused. This is the single most effective setting against a raid, and it is 0 by default, meaning no gate. Set it deliberately.
• Cooldown — how long one member must wait between attempts.
• Already registered — a member who is already registered cannot register again.
• Burst ceiling — if a server takes an unusual number of self-registrations in a short window, self-registration pauses automatically until the burst passes. Staff registration keeps working throughout.
• Lockdown — while Anti Raid or Anti Nuke has the server in lockdown, self-registration is closed.

Every registration is recorded with who registered whom, when, and through which entry point, so a burst can be reviewed after the fact.

How it works

1. Set it up with the setup wizard (!register setup), the dashboard, or !register-setup.
2. A new member joins → they get the unregistered role and a welcome embed mentions the registrar role.
3. Either a registrar runs !register <user> — or the short alias !k <user> — or, if self-registration is on, the member presses the register button themselves.
4. If needed, !unregister <user> returns a member to the unregistered state.

Who can register

Anyone with Manage Roles (or Administrator), a configured moderator user, or the registrar role can run !register / !k / !unregister on another member. Configuring the system (!register-setup, !register-status, !register-self, !register-disable) still requires Manage Roles.

Turning it off

Run !register-disable to turn off join automation: new members are no longer auto-assigned the unregistered role and no welcome embed is sent. The saved roles are kept, so !register, !k, and !unregister still work manually. You can also toggle this with Join automation on Dashboard → Register.

To turn off only the member-facing half, use !register-self off instead.

Command status

From the dashboard you can see the command status for the register commands — confirming they're enabled and configured correctly.

Next steps

• Configure it on Dashboard → Register
• Browse the register commands
• Confirm Netrcol's permissions and role position

Related docs

• Register Commands
• Autorole
• Permissions & Roles

Browse all documentation