Guides, policies, and troubleshooting help

Browse articles covering connection issues, IRC client setup, network rules, and account management - or search for exactly what you need.

Good first checks

  • Search by the exact error text if your client shows one.
  • Open a category first if you are not sure what terms to search for.
  • Read the relevant guide before opening a ticket whenever possible.
  • Include the guide steps you already tried when you do need support.

Matching articles

Bots & Scripts

Approved uses for bots on AustNet

Bots & Scripts

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

Cloning policy and bots: connecting multiple clients

Bots & Scripts

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

Popular bot frameworks for IRC

Bots & Scripts

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

Registering your bot nickname with NickOP

Bots & Scripts

Register your bot's nickname just like a regular user. How to identify on connect and set the +B bot mode automatically.

Reporting a rogue or abusive bot

Bots & Scripts

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

Running a bot on AustNet: rules and requirements

Bots & Scripts

Bots must be registered with NickOP, marked with +B mode, and must not flood channels or perform mass messaging. Full requirements.

Setting bot mode (+B) on your connection

Bots & Scripts

All bots on AustNet must set user mode +B to identify themselves as automated clients. How to set this in common bot frameworks.

Using ChanOP instead of a custom bot

Bots & Scripts

ChanOP already provides auto-op, access lists, topic lock, and flood control. Before running a bot, check whether ChanOP already does what you need.