From 2459f5c17fa8165fb9056cd1983b79dcba0816fd Mon Sep 17 00:00:00 2001 From: VistaPOWA Date: Sun, 13 Apr 2014 19:18:16 +0200 Subject: [PATCH] Makes the nag message not activate if comms are not enabled This nag message should only come up when something has gone horribly wrong. --- code/modules/client/client procs.dm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/code/modules/client/client procs.dm b/code/modules/client/client procs.dm index 92b5aba183a..6256c3001df 100644 --- a/code/modules/client/client procs.dm +++ b/code/modules/client/client procs.dm @@ -130,7 +130,7 @@ var/next_external_rsc = 0 if(holder) add_admin_verbs() admin_memo_show() - if(config.comms_key == "default_pwd" || length(config.comms_key) <= 6) //It's the default value or less than 6 characters long, warn badmins + if(config.comms_key == "default_pwd" || length(config.comms_key) <= 6 && !config.comms_enabled) //It's the default value or less than 6 characters long, but it somehow didn't disable comms. src << "The server's API key is either too short or is the default value! Consider changing it immediately!" log_client_to_db()