Change the default for <waitpong:sendsnotice> to false.

This message exists for an incredibly rare issue and just confuses
the vast majority of people.
This commit is contained in:
Peter Powell 2019-11-29 13:46:24 +00:00
parent df2a3d6fc4
commit 694c121908
2 changed files with 2 additions and 2 deletions

View File

@ -617,7 +617,7 @@
# killonbadreply - Whether to kill the user if they send the wrong # # killonbadreply - Whether to kill the user if they send the wrong #
# PONG reply. # # PONG reply. #
# # # #
#<waitpong sendsnotice="yes" killonbadreply="yes"> #<waitpong sendsnotice="no" killonbadreply="yes">
#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-# #-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#
# Channel cycle module: Adds the /CYCLE command which is a server-side # Channel cycle module: Adds the /CYCLE command which is a server-side

View File

@ -39,7 +39,7 @@ class ModuleWaitPong : public Module
void ReadConfig(ConfigStatus& status) CXX11_OVERRIDE void ReadConfig(ConfigStatus& status) CXX11_OVERRIDE
{ {
ConfigTag* tag = ServerInstance->Config->ConfValue("waitpong"); ConfigTag* tag = ServerInstance->Config->ConfValue("waitpong");
sendsnotice = tag->getBool("sendsnotice", true); sendsnotice = tag->getBool("sendsnotice", false);
killonbadreply = tag->getBool("killonbadreply", true); killonbadreply = tag->getBool("killonbadreply", true);
} }