New CraftBukkit build now available; provides CRITICAL exploit fix.

Discussion in 'Bukkit News' started by EvilSeph, Apr 8, 2011.

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


    If it isn't causing any lag use:
  2. Offline


    this made me lul
  3. Offline


    he is very serious.. and don't call him surely.. LMAO

  4. Offline


    Ok, waiting on CB671 because MOST plugins do not work with CB670 because of the NULL issues everyone is having. I have seen a LOT of this complaint ALL over the plugin threads. My server I literally had to shut down completely. It became useless because the CB670 forced plugins to rewrite files ( Permissions for example ) and put NULL all over the config file. The Plugin coders are waiting on Bukkit to put out another ( FIXED ) version of CB.

    What it did was allow all the grievers to do what they wanted to the servers. Lots of us have this issue right now and we had to be forced to shut down our servers. It caused a lot more work for everyone who is having to go through hand by hand to get rid of the word NULL. So we wait patiently for Bukkit to come out with new version. :)

    And by the way, just wanted to say.. Go Bukkit !! you guys rock !!
  5. Offline


    We need to land - this woman needs to be gotten to a hospital!
    A hospital? What is it?
    It's a big building with patients, but that's not important right now.

  6. Offline


    HAHAHAHAAHAHA you got it.. :p Love that movie.. :)
  7. Actually, it's the plugins and config files that are going to have to be updated, not CraftBukkit - this was intentional breakage, if severe for some people (it wasn't for most).
  8. Offline


    Wait.. so NULL IS supposed to be there ? and not one of the plugin creators knew about it ? because from what I am reading.. NONE of them knew this. And they are waiting on craftbukkit to update.

    If its them who has to update, this is going to be an interesting thread REAL soon.. lol
  9. Offline


    As I said on the Permissions thread, the nulls are caused by a combination of how Java's Map classes work and the way SnakeYAML interprets null data. I have already submitted a pull request fixing the problem. They are not supposed to be there.
  10. Offline


    that's what I thought.. so NULL is not supposed to be there.
  11. Offline


    So basically what im getting out of all this is, if you run a server dont update to 670 especially if your not the most skilled admin like me?
  12. Offline


    Nope, not it at all. :p

    How about helping people. There is a LOT of admins all over this forum who would love to know your "secrets" they "they" could not figure out.. That you just happen to know all the answers too. Most all of us admins are having the same issues.. but with different plugins.. based off the same issue of the CB670.

    EDIT : And we want the newer updated CB because of the Exploits that are in the older versions.. in the older versions , as was stated... there is an exploit that people were hacking into that would bring the server down. So we NEED this new update.
  13. Ah wait. I was thinking of the wrong nulls. My bad. :p
  14. Offline


  15. Offline

    Netto Hikari

  16. Offline


    well I got the new 670 build up and running with all my current plugins with almost no issues had to remove civilized spawn entirely but that no big issue atm well see how things go for now :p
  17. Offline


    The size increase seems to be due to the inclusion of the SQLite libraries & classes.
  18. Offline


    I updated from 617 and I had a lot of complaints from my friends playing on my server about it being really laggy. So you guys are not alone. So I rolled back to 617 till someone works it out. Hopefully its all sorted before 1.5 heads our way.
    Rich Boos likes this.
  19. Offline


    Alas using Crafty to run the latest, I get the following error messages. Any help appreciated.

    > 15:56:48 [INFO] Starting minecraft server version Beta 1.4
    > 15:56:48 [INFO] Loading properties
    > 15:56:48 [INFO] Starting Minecraft server on *:25500
    > 15:56:48 [INFO] This server is running Craftbukkit version git-Bukkit-0.0.0-646-gb61ef8c-b670jnks (MC: 1.4)
    > 15:56:48 [SEVERE] java.lang.NullPointerException
    > 15:56:48 [SEVERE] at<init>(
    > 15:56:48 [SEVERE] at org.bukkit.util.config.Configuration.load(
    > 15:56:48 [SEVERE] at org.bukkit.craftbukkit.CraftServer.<init>(
    > 15:56:48 [SEVERE] at net.minecraft.server.ServerConfigurationManager.<init>(
    > 15:56:48 [SEVERE] at net.minecraft.server.MinecraftServer.d(
    > 15:56:48 [SEVERE] at
    > 15:56:48 [SEVERE] at
    > 15:56:48 [SEVERE] Unexpected exception
    at org.bukkit.util.config.Configuration.load(
    at org.bukkit.craftbukkit.CraftServer.<init>(
    at net.minecraft.server.ServerConfigurationManager.<init>(
    at net.minecraft.server.MinecraftServer.d(
  20. Offline


    Anyone else getting crasy amounts of mobs spawned with 670?
  21. Offline


    no - no mobs spawning as I can no longer run a server as i get the above error messages
  22. Offline


    It's most likely a problem with a craftbukkit configuration file. Have you tried to delete all of them (make backups before) and then starting craftbukkit to let it generate new files?
  23. Offline


    aha - sorry - 670 running nicely now - Its crafty that was causing the problem.
  24. Offline


    Actually we almost don't get any mobs at all after the update sadly
  25. Offline


    There is another thread about many mobs spawned, I suggest to check your plugins.
  26. Offline


    I miss the Chuck Norris facts over on Jenkins; I always set the build's 'fact' as part of the MOTD so my users knew when the server was updated. :D
  27. Offline


    Uh... so the front page says we should be using 669 now? Is this a mistake?
  28. Offline


    yup, just an order error, 670 is recommended too and it's newer
  29. Offline

    EvilSeph Retired Staff

    I accidentally promoted 669 after I had promoted 670. Ignore it and keep using 670.
  30. Offline


    Having huge memory issues with 670 under windows installing debian to give it a try. Otherwise I guess I'll rollback to 617.
Thread Status:
Not open for further replies.

Share This Page