ALL of the following commands work in the channel window whether or not Channel Service (X or CStar) is in channel.

Those commands requiring ops will still only work if you are opped:

Ignore:
/ignore nick

Unignore:
/ignore -r nick

Kick:
/kick #channel nick

Ban and Kick:
/kick #channel nick | /ban #channel nick

Moderate (+m):
/mode #channel +m

Un-Moderate (-m):
/mode #channel -m

voice (+v):
/mode #channel +v nick

devoice (-v):
/mode #channel -v nick

mult devoice:
/mode #channel -vvvvv nick1 nick2 nick3 nick4 nick5

Op another:
/mode #channel +o nick

De-Op:
/mode #channel -o nick

CTCP Finger:
/ctcp nick finger

CTCP Page:
/ctcp nick page

CTCP Ping:
/ctcp nick ping

CTCP Time:
/ctcp nick time

CTCP Version:
/ctcp nick version

DCC Send:>
/dcc send nick path & filename

DCC Chat:
/dcc chat nick

The following can be used in the status window for enquiry purposes...

names in a channel:
/names #channel

resolve a user's dns:
/dns IP to resolve

Here's one that only works with CStar & X... it is an amusing one added by the bots' owners, just for fun... Try it for a laugh :)

Descriptive Bit

IRC - Internet Relay Chat - has basic commands which can be implemented through your chat client. This little program is already designed to implement those which you may need - either as a guest in channel (which ops are whilst not 'opped up') or whether as an op with the @ symbol next to the nick.

Some of these IRC commands relating to ops are often referred to as 'X' commands; while X will execute those commands if it is there, the commands already exist in IRC.

CStar commands specifically commence with '/msg CStar' or '/msg CStar@cservice.starlink-irc.org'. We have a page of those commands which you may read.

X commands specifically commence with '/msg x' or '/msg x@channels.undernet.org'. We have a page of those commands which you may read.

So, if you are opped, you may ask the question 'what if one bot or both of them disappear?'

Simply, the answer is... if you are already opped and wish to remove or ban somebody, and neither bot is there, your chat client implements those commands on your behalf because it knows you are an op.

However, should you get lost in a netsplit and come back without there being a bot in channel, of course your chat program no longer knows you are an op, and you are unable to act as one until either

a bot which knows you returns,

or

someone who knows you is prepared to op you.

That too is an IRC command, not a bot command, of course. Why you cannot op up is because that is an inbuilt safety thingy in all chat programs.

When there is a bot in channel - whether it is a channel service one, or a private one like logos, then ops are easily controlled by the bot or bots (if there is more than one).

Of course, these basic IRC commands are very limited in scope, which is why we like to use bots as well.

While bots will allow people who they 'know' to op through them, there the similarity ends; their command structure is different, and this is explained in the next several pages.