This guide is designed for users who wish to register channels on Techtronix. Techtronix staff highly recommends that you follow the user guide before reading this one, as it explains how to get set up on the network.
Registering a Channel
Registering a channel on Techtronix is very easy to do -- all you really need is a registered (and verified/confirmed) NickServ account. Join the channel you want to register by typing
/join #channelname, and then type
/cs register #channelname description, replacing #channelname with your channel's name and description with a description of your channel. This will be shown to users when they type
/cs info #channelname. The description is optional, but it is highly recommended as it can help users get more familiar with your channel. It might even attract more users
If the channel you join has more than just you, you will not be given the status required to register the channel. Furthermore, you cannot register channels that have already been registered or register channels that have been restricted by network services. If you run into issues registering your channels, please let network staff or otherwise Techman know.
When you're done registering your channel, you might notice that a "user" named ChanServ has joined your channel and has given itself operator
+o status. ChanServ is actually the core channel service on the network, and is the service that you'll mostly be using to manage your channel.
However, BotServ is a useful network service that is rarely given the respect that it deserves. BotServ allows you to set a custom service bot for your channel. ChanServ by default is the service bot given to newly registered channels. You can have any custom bot assigned to your channel. Available bots that you can assign to your channel right away are shown in
/bs botlist. As a new channel owner, you can actually request a custom bot be created as well. To assign a bot to your channel, type
/bs assign #channelname botnick, replacing botnick with the bot's nick. You should know what goes in the place of #channelname already, as it was used previously in the other getting started guide.
In addition to the network-provided default flood protection, the BotServ service itself also offers some more flood protection features, some of which are more out of the scope for the IRCd. However, some of these BotServ flood protections are redundant to the network-provided one (such as message floods). Techtronix staff recommends that you don't use BotServ protections that already are provided by the network's own server software
Of course, no full-featured interactive could be complete without Infobot! Infobot is a customized version of Cloudbot and is written in Python. If you wish to contribute code to the bot, you can contribute code to the main Cloudbot repository. Updates from them eventually trickle down to the network.
Techtronix prides itself in being one of the only networks to ever have something considered/called channel history. Channel history is basically what it sounds like: channel history. Based on parameters set for the channel mode, a certain number of lines per certain amounts of seconds are displayed to a joining user. An example is 15:120, which means that 15 messages will be shown to new users that join the channel, and those 15 messages will come from the past 120 seconds (2 minutes) of the channel's discussion. It's a prime feature for those that rely on users often joining from a web client. Here is an example on how to set the channel history configuration above:
/mode #channelname +H 15:120.