projects / irc / rqf / shadowircd.git / blame
| Commit | Line | Data |
|---|---|---|
| 212380e3 | 1 | ratbox-services compatibility documentation - Lee H <lee -at- leeh.co.uk> |
| 2 | ------------------------------------------------------------------------- | |
| 3 | ||
| 3911ef9b JT |
4 | Compatibility with ratbox-services is always enabled. Note that some or |
| 5 | all of this is also used by atheme-services and anope. It will add the | |
| 6 | following features to ircd: | |
| 212380e3 | 7 | |
| 8 | 1. Channel mode +r | |
| 9 | ||
| 10 | A simple mode taking no parameters, will require users are logged in | |
| 11 | with user services before they may join the channel. | |
| 12 | ||
| 13 | Gives numeric 477 to users who arent logged in: | |
| 14 | :<server> 477 <nick> <channel> :Cannot join channel (+r) | |
| 15 | ||
| 16 | 2. service block to ircd.conf | |
| 17 | ||
| 18 | Ability to specify the names of services servers in ircd.conf: | |
| 19 | service { | |
| 20 | name = "services.ircd-ratbox.org"; | |
| 21 | name = "backup-services.ircd-ratbox.org"; | |
| 22 | }; | |
| 23 | ||
| 24 | These must be specified for certain features to work. You may specify as | |
| 25 | many name entries as you wish, however you must define only one service | |
| 26 | block. | |
| 27 | ||
| 28 | Entries will be listed in stats U with the flag 's'. | |
| 29 | ||
| 30 | 3. Services protection | |
| 31 | ||
| 32 | Services will be protected from being deopped or kicked from a channel. | |
| 33 | ||
| 34 | 4. Username tracking through netsplits | |
| 35 | ||
| 36 | When users are logged in, the username they are logged in with will be | |
| 37 | preserved on a netsplit, so users will not have to relogin when the | |
| 38 | network merges together. | |
| 39 | ||
| 40 | 5. Username given on WHOIS | |
| 41 | ||
| 42 | When users are logged in, WHOIS will also give numeric 330: | |
| 43 | :<server> 330 <yournick> <targetnick> <loginname> :is logged in as | |
| 44 | ||
| 45 | Note this needs to be a remote whois to work when the target is | |
| 46 | on a different server. | |
| 47 | ||
| 48 | 6. Forced nick change | |
| 49 | ||
| 50 | When using nickname services and a client requests they regain a | |
| 51 | nickname, services can perform a forced nick change on the client. | |
| 52 | This forcibly changes the clients nickname to the one they requested | |
| 53 | they regain, ensuring they can always regain their nickname. | |
| 54 | ||
| 388ff36d JT |
55 | 7. User mode +R |
| 56 | ||
| 57 | This user mode will require users are logged in with user services | |
| 58 | before they may send private messages or notices to the user. | |
| 59 | ||
| 60 | As with user mode +g, IRC operators and accepted users can send even | |
| 61 | if they are not logged in. | |
| 62 | ||
| 63 | Gives numeric 486 to users sending a PRIVMSG who are not logged in: | |
| 64 | :<server> 486 <nick> <targetnick> :You must log in with services to message this user | |
| 65 | ||
| 212380e3 | 66 | # $Id: services.txt 6 2005-09-10 01:02:21Z nenolod $ |