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:
- Connect to the network and choose your bot's desired nickname.
- Send the registration command to NickOP:
Plaintext
- 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.
- 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.
- 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
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.
- Execution Order:
- Connect to
irc.austnet.org(SSL port6697). - Complete NickOP authentication (via SASL or identification).
- Issue the mode command to apply the bot flag:
Plaintext
Once registered, authenticated, and flagged with +B, your bot is fully compliant with AustNet network standards and ready to join your designated channels!