Solved How can I configure login cooldown?

Discussion in 'Bukkit Help' started by Northern, Mar 17, 2012.

Thread Status:
Not open for further replies.
  1. Offline

    Northern

    Hi, I'm setting up a Bukkit server for couple of friends. There's currently some kind of 4-minute login cooldown, ie. when a player disconnects shortly after logging in and then tries to log in again, there's a message 'You must wait 4 more minutes before logging-in again.'.

    I know this is useful against lag griefing, but it can also be super annoying sometimes, because this also happens if a user is having connection problems. I'd like to know where can I configure the behaviour? I've tried searching the forums and Google but still have no clue.


    My server specs are:
    Code:
    Linux 2.6.32-39-server #86-Ubuntu SMP Mon Feb 13 23:15:11 UTC 2012 x86_64 GNU/Linux
    java version "1.6.0_31"
    Java(TM) SE Runtime Environment (build 1.6.0_31-b04)
    Java HotSpot(TM) 64-Bit Server VM (build 20.6-b01, mixed mode)
     
    CraftBukkit version git-Bukkit-1.2.3-R0.2-b2060jnks (MC: 1.2.3) (Implementing API version 1.2.3-R0.2)
    Minecraft Remote Toolkit R10 Alpha 12
     
    plugins:
    Essentials
    EssentialsChat
    EssentialsProtect
    EssentialsSpawn
    GriefPrevention
    Dynmap
    Dynmap-Essentials
    Dynmap-GriefPrevention
    Multiverse-Core
    Multiverse-Portals
    PermissionsEx
    Vault
    MinecraftRKitPlugin
    
    I think I found it: forced-restart-delay in Remote Toolkits config in toolkit/wrapper.properties.

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: May 24, 2016
  2. Offline

    drdanick

    The toolkit is not responsible for this behavior. Check your other plugins.
     
  3. Offline

    Swords761

    For those with this issue and are looking for the plugin causing the problem- it's GriefPrevention's spam protection setting, mainly the "cooldown" time set when it kicks for spam. Adjust that to your liking.
     
Thread Status:
Not open for further replies.

Share This Page