On AustNet, network policy and the Acceptable Use Policy (AUP) require that all automated clients and bots must clearly identify themselves by setting user mode +B upon connection.
Setting this mode ensures that network operators, channel administrators, and automated metrics can transparently distinguish between human chatters and automated scripts.
How User Mode +B Works
- The Flag:
+Bis a standard InspIRCd user mode that flags a connection as a bot/service drone. - Manual Setting: If you connect a script or client manually, you can apply the mode via raw command immediately after authentication:
Plaintext
- Why It Matters: Failing to set
+Bon automated scripts can result in automated filtering or network staff flagging the connection for policy non-compliance.
Setting Mode +B in Common Bot Frameworks
Most robust bot frameworks allow you to send raw commands or configure automated mode-setting routines upon successfully completing the connection and registration handshake (the 001 numeric or WELCOME event).
1. Eggdrop (Tcl / C)
In your Eggdrop configuration file (eggdrop.conf), you can configure the bot to issue modes upon startup using the chat-mode or standard startup triggers, or handle it via a bound event:
Tcl
2. Node.js (irc-framework)
If you are using Node.js with irc-framework, you can listen for the registered event, which fires as soon as the client successfully connects and authenticates:
JavaScript
3. Python (irc library or custom async loops)
For Python scripts using standard client loops or event-driven connection handlers, trigger the mode change inside the on_welcome (numeric 001) callback:
Python