diff options
author | shennetsind <ind@henn.et> | 2013-10-27 18:28:15 -0200 |
---|---|---|
committer | shennetsind <ind@henn.et> | 2013-10-27 18:28:15 -0200 |
commit | 6c1996a050e03408e55333c1efa1034ae25b9a00 (patch) | |
tree | a75eaef4c25f97b5b0278ad8f7e8f57ad47dd400 | |
parent | 3a8837f924924ee5193d4a9b1d6da8d53cbba222 (diff) | |
download | hercules-6c1996a050e03408e55333c1efa1034ae25b9a00.tar.gz hercules-6c1996a050e03408e55333c1efa1034ae25b9a00.tar.bz2 hercules-6c1996a050e03408e55333c1efa1034ae25b9a00.tar.xz hercules-6c1996a050e03408e55333c1efa1034ae25b9a00.zip |
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 <ind@henn.et>
-rw-r--r-- | conf/battle/guild.conf | 6 |
1 files changed, 3 insertions, 3 deletions
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 |