Fantasy are in-channel commands beginning with !
ACCESS ADD will assign the given user to the given channel role.
Syntax: ACCESS ADD
!ACCESS ADD stitch VOP
ACCESS DEL will remove all channel access from a given user.
Syntax: ACCESS DEL
!ACCESS DEL stitch
ACCESS INFO displays what level of access a given user has in a given channel. It will display role, long-form flags and short-form flags along with the last date the user’s access was modified.
Syntax: ACCESS INFO
!ACCESS INFO nenolod
ACCESS LIST lists all users with channel access and their roles in the channel. It uses fuzzy matching so if a user does not exactly match any role, they will be listed as the closest role they match.
Syntax: ACCESS LIST
The AKICK command allows you to maintain channel ban lists. Users on the AKICK list will be automatically kickbanned when they join the channel, removing any matching ban exceptions first. Users with the +r flag are exempt.
Syntax: AKICK ADD
You may also specify a hostmask (nick!user@host) for the AKICK list.
The reason is used when kicking and is visible in AKICK LIST. If the reason contains a ‘|’ character, everything after it does not appear in kick reasons but does appear in AKICK LIST.
If the !P token is specified, the AKICK will never expire (permanent). If the !T token is specified, expire time must follow, in minutes, hours (“h”), days (“d”) or weeks (“w”).
Syntax: AKICK DEL
This will remove an entry from the AKICK list. Removing an entry will remove any matching channel bans unless the channel is set NOSYNC.
Syntax: AKICK LIST
This will list all entries in the AKICK list, including the reason and time left until expiration.
!AKICK ADD bar you are annoying | private op info
!AKICK ADD *!*firstname.lastname@example.org !T 5d
!AKICK DEL bar
The BAN command allows you to ban a user or hostmask from a channel.
Clear bans will remove all bans found in a specific channel. If your ircd supports other lists associated with a channel (e.g. ban exceptions), you can clear these by specifying the mode letters. Specify an asterisk to clear all lists.
Syntax: CLEAR BANS [types]
Clears ban list.
!CLEAR BANS eI
Removes all ban and invite exceptions (if your ircd supports them).
!CLEAR BANS *
Clears all lists
!CLEAR BANS +
Shows the possible letters.
CLEAR FLAGS will kick remove all flags from all users (or groups) with channel access on the channel specified except for users who are channel founders.
This command can only be used by channel founders.
Syntax: CLEAR FLAGS
Clear users will kick all users out of the channel, except you. The channel will be cycled (recreated) if you are not on it.
If a reason is specified, it will be included in the kick message.
Syntax: CLEAR USERS [reason]
CLOSE prevents a channel from being used. Anyone who enters is immediately kickbanned. The channel cannot be dropped and foundership cannot be transferred.
Enabling CLOSE will immediately kick all users from the channel.
Use CLOSE OFF to reopen a channel. While closed, channels will still expire.
Syntax: CLOSE ON|OFF [reason]
!CLOSE ON spamming
!CLOSE #channel OFF
This will give a count of how many entries are in each of the channel’s xOP lists and how many entries on the access list do not match a xOP value.
The second line shows how many access entries have each flag.
DROP allows you to “unregister” a registered channel.
Once you DROP a channel all of the data associated with it (access lists, etc) are removed and cannot be restored.
See help on SET FOUNDER and FLAGS for transferring a channel to another user.
FDROP allows dropping any registered channel, provided it is not set held (see help on HOLD).
Once you FDROP a channel all of the data associated with it (access lists, etc) are removed and cannot be restored.
The FFLAGS command allows an oper to force a flags change on a channel. The syntax is the same as FLAGS, except that the target and flags changes must be given. Viewing any channel’s access list is done with FLAGS.
Syntax: FFLAGS nickname | hostmask template
Syntax: FFLAGS nickname | hostmask
!FFLAGS foo AOP
- You can follow any responses to this entry through the RSS 2.0 feed.