Server Kicking: disconnect.spam

Discussion in 'Bukkit Help' started by iMattu, Feb 16, 2013.

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

    iMattu

    Hello Bukkit Community,

    I'm experiencing some issues with my server. After typing in some commands, or more the server kicks players including myself (the admin) with the message: disconnect.spam

    I have uploaded a list of my plugins.

    I would really appreciate some help since this problem is really annoying me!

    Thanks a lot
    - iMattu
     

    Attached Files:

  2. Offline

    TnT

    This is a Minecraft feature. No way to disable it.

    Just slow down how often you type the same command/text repeatedly.
     
  3. Offline

    mbaxter ʇıʞʞnq ɐ sɐɥ ı

    iMattu Remove BKCommonLib or BeTheMob if you have them. Those are both reported as causing the problem.

    The plugin author is recklessly playing with the internals of CraftBukkit without adequately testing, and is breaking your servers. This dangerous development approach and breaking of servers has been ongoing for months. I would suggest finding new plugins to replace those using BKCommonLib.
     
  4. Offline

    dylanisawesome1

    "The plugin author is recklessly playing with the internals of CraftBukkit without adequately testing, and is breaking your servers. This dangerous development approach and breaking of servers has been ongoing for months."
    A bit harsh... We have not been "wrecklessly playing with" the internals of craftbukkit, but have been expanding our plugins to the full extent of minecraft.
     
  5. Offline

    10se1ucgo

    Would you be able to recommend a replacement for NoLagg?
     
  6. Offline

    theassassin_17

    I'm going to give you the real solution, I had the same issue. The problem here is BKCommonLib, it has this problem in the last version. Use version 1.44, and use the lastest version of NoLagg. This solves the problem without using other plugins.When the author of BKCommonLib fixes that, you can upgrade once again. For now, use 1.44
     
Thread Status:
Not open for further replies.

Share This Page