Auto Register

What this is for

Use auto-register when the target server expects players to register or log in through chat commands after joining.

The current built-in behavior is simple:

if a chat message contains /register or /reg, SoulFire sends the configured register command
if a chat message contains /login or /l, SoulFire sends the configured login command
the command is sent after a random delay in milliseconds

This makes it a practical fit for AuthMe-style flows and similar chat-driven login plugins.

What it expects

This plugin works best when the server clearly tells the player which command to use in chat.

It is a good fit when the server displays prompts such as:

/register password password
/login password
/reg password password
/l password

It is a poor fit for:

GUI-based login systems
plugin flows that hide the command entirely
custom registration systems that do not expose standard chat prompts

Configure auto-register

Enable the plugin

Open Plugins and enable Auto Register.

Set the register command

Configure the exact command template used for registration.

The default is:

/register %password% %password%

Configure the exact command template used for login.

The default is:

/login %password%

Choose the password format

Set the password value SoulFire should substitute for %password%.

The current implementation uses one shared configured password string.

Configure the send delay

Set a min/max delay in milliseconds before the command is sent. That helps avoid sending the command at the exact same instant every time.

Test it safely

Start with one bot on one server.

You want to confirm:

the server actually shows a prompt containing /register, /reg, /login, or /l
the command template matches the server's expected syntax
the password format is what you intended
the server accepts the command after the chosen delay

Once that works, scale up.

Command examples

These are reasonable starting points. Do not assume every server uses the same syntax.

Common registration command

/register %password% %password%

Common login command

/login %password%

If the server uses a different alias

/reg %password% %password%

Delay guidance

The delay is not a cosmetic setting. It changes when the command is sent after the prompt arrives.

Keep the delay low if the server expects a fast response and the chat prompt is reliable.
Increase it slightly if the server, proxy, or chat pipeline is noisy and immediate responses misfire.
Do not push it arbitrarily high unless the server clearly needs it.

Security notes

Treat the configured password as sensitive.

Do not reuse an important real-world password here.
Assume anyone with access to the instance settings can see or reuse it.
Prefer a dedicated test password for bots.

This plugin does not prove that a server is safe to automate. It only automates a chat-command login flow that already exists.

Known limitations

It reacts to simple string matches in chat, not deep semantic understanding.
It does not currently support advanced per-bot password generation logic.
It will not help with non-chat registration systems.
It depends on the prompt reaching the bot in readable chat text.

Common failure patterns

Nothing happens after join

The server may not be using a prompt format this plugin recognizes, or the message may never reach normal chat.

The wrong command is sent

Your configured command template does not match the server's syntax.

The command is right, but registration still fails

Check whether the password format, alias, or timing is wrong for that server.

On this page