From 7019b27e591e0f5ce3727993e02198ae070885e9 Mon Sep 17 00:00:00 2001 From: Sadie Powell Date: Sun, 24 Nov 2024 23:56:57 +0000 Subject: Rework how guest nicks work. - Use the config setting as a string template instead of as a prefix. - Allow users of IRCds that have UIDs to use that as the guest nick. - Fall back to a UID before killing if a guest nick can not be found. --- data/nickserv.example.conf | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) (limited to 'data') diff --git a/data/nickserv.example.conf b/data/nickserv.example.conf index a62379053..4d2ef3af8 100644 --- a/data/nickserv.example.conf +++ b/data/nickserv.example.conf @@ -203,13 +203,17 @@ module releasetimeout = 1m /* - * When a user's nick is forcibly changed to enforce a "nick kill", their new nick will start - * with this value. The rest will be made up of 6 or 7 digits. - * Make sure this is a valid nick and Nicklen+7 is not longer than the allowed Nicklen on your ircd. + * When a user's nick is forcibly changed to enforce nickname protection their new + * nick will be based on this value. Any # in the value will be replaced with a random + * number. If your IRCd has support for unique identifiers you can also set this to an + * empty string to change a user's nick to their unique identifier. * - * This directive is optional. If not set it defaults to "Guest" + * Make sure this is a valid nick and that it is is not longer than the maximum nick + * length on your IRCd. + * + * This directive is optional. If not set it defaults to "Guest####" */ - guestnickprefix = "Guest" + guestnick = "Guest####" /* * If set, Anope does not allow ownership of nick names, only ownership of accounts. -- cgit