From 6c1996a050e03408e55333c1efa1034ae25b9a00 Mon Sep 17 00:00:00 2001 From: shennetsind Date: Sun, 27 Oct 2013 18:28:15 -0200 Subject: Fixed Bug #7784 Since cooldowns are now persistent to logout, the meaning of the setting has changed (see description within changeset). http://hercules.ws/board/tracker/issue-7784-guild-skill-relog-delay/ Signed-off-by: shennetsind --- conf/battle/guild.conf | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'conf/battle') diff --git a/conf/battle/guild.conf b/conf/battle/guild.conf index e9b025adb..a40cbbe3a 100644 --- a/conf/battle/guild.conf +++ b/conf/battle/guild.conf @@ -16,9 +16,9 @@ guild_exp_limit: 50 // Maximum castles one guild can own (0 = unlimited) guild_max_castles: 0 -// Activate guild skills delay by relog? (Note 1) -// Official setting is "yes", otherwise allow guild leaders to relog to cancel the 5 minute delay. -guild_skill_relog_delay: yes +// Restart guild skills cooldown by relog? (Note 1) +// When "no", you relog with the same cooldown remaining as from when you logged out, "yes" restarts the cooldown upon login to its full duration. +guild_skill_relog_delay: no // Damage adjustments for WOE battles against defending Guild monsters (Note 2) castle_defense_rate: 100 -- cgit v1.2.3-70-g09d2