newnick
no way to compare when less than two revisions
Differences
This shows you the differences between two versions of the page.
| — | newnick [2007/02/27 04:57] (current) – created - external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | # $EPIC: newnick.txt, | ||
| + | ======Synopsis: | ||
| + | [[load]] newnick \\ | ||
| + | [[set]] auto_new_nick ON|OFF|TOGGLE \\ | ||
| + | [[set]] auto_new_nick_char < | ||
| + | [[set]] auto_new_nick_list < | ||
| + | [[set]] auto_new_nick_length < | ||
| + | |||
| + | ======Description: | ||
| + | This script implements the nickname fudging facility that previously was | ||
| + | built in to the client. | ||
| + | |||
| + | Whenever the client requires of you a new nickname, if set auto_new_nick | ||
| + | is OFF, then you will be prompted for a new nickname. | ||
| + | the next nickname in set auto_new_nick_list will be selected. | ||
| + | is empty or all of the nicknames have been exhausted, then the nickname is | ||
| + | mangled by adding the single character of set auto_new_nick_char. | ||
| + | that nickname reaches set auto_new_nick_length characters, it is rotated, | ||
| + | by moving the final character in the nick to the start. | ||
| + | |||
| + | Eventually, the script will find a nickname that isn't in use, without | ||
| + | requiring any manual intervention. | ||
| + | |||
| + | ======History: | ||
| + | The auto-new-nick feature first appeared in epic2pre3. | ||
| + | This script was written by blackjac and first appeared in epic5-0.0.6. | ||
| + | |||
newnick.txt · Last modified: 2007/02/27 04:57 by 127.0.0.1
