Knowledgebase · Bots & Scripts

Registering your bot nickname with NickOP

Updated 22 Sep 2026 Support Operations

Just like human users, all automated scripts and bots on AustNet should have their own registered identities. Registering your bot's nickname with NickOP ensures that its name is permanently reserved, protects it from being hijacked, and allows secure authentication upon connection.


1. Registering the Nickname

Before deploying your bot script permanently, connect manually with your client to register the chosen nickname:


  1. Connect to the network and choose your bot's desired nickname.
  2. Send the registration command to NickOP:

Plaintext

/NickOP REGISTER <password> <email>
  1. Check your email for any verification instructions or completion notices required by network services.

2. Automating Authentication on Connect

To prevent your bot from getting stuck or failing to claim its name on restart, configure your bot framework to authenticate immediately upon joining the network.


  1. Using SASL (Recommended): Configure your bot's connection profile to use SASL PLAIN or EXTERNAL authentication. This logs the bot into NickOP before it fully enters the network, ensuring its nickname is secured instantly without race conditions.
  2. Using Post-Connect Commands: If SASL is not used, program your bot to send the identification command as soon as the connection event triggers:

Plaintext

/NickOP IDENTIFY <password>

3. Setting the +B Bot Mode Automatically

As covered in network policy, every bot must identify itself as an automated client by setting user mode +B. This must happen right after registration and identification are complete.


  1. Execution Order:
  2. Connect to irc.austnet.org (SSL port 6697).
  3. Complete NickOP authentication (via SASL or identification).
  4. Issue the mode command to apply the bot flag:

Plaintext

/mode YourBotNick +B

Once registered, authenticated, and flagged with +B, your bot is fully compliant with AustNet network standards and ready to join your designated channels!


Approved uses for bots on AustNet

Bots may be used for channel management, trivia, logs, and legitimate services. What is not permitted: mass messaging, cloning, and flooding.

Open article

Cloning policy and bots: connecting multiple clients

AustNet permits a maximum of two simultaneous connections from one IP. Bots count toward this limit - request an exemption via #ASD if needed.

Open article

Popular bot frameworks for IRC

Overview of common IRC bot frameworks - Eggdrop, Limnoria (Supybot), Sopel, and custom Python/Node.js bots - and getting started.

Open article

Reporting a rogue or abusive bot

If a bot is flooding, spamming, or behaving maliciously, how to report it to network staff and what information to include.

Open article