Bad chunks. Possible to fix?

Discussion in 'Bukkit Help' started by AkaAnonymous, Feb 27, 2011.

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

    AkaAnonymous

    Code:
    2011-02-27 21:50:03 [INFO] Chunk (0, 149) stored at  (5, 139)
    2011-02-27 21:50:03 [INFO] net.minecraft.server.Chunk
    2011-02-27 21:50:03 [SEVERE] java.lang.Throwable
    2011-02-27 21:50:03 [SEVERE]     at net.minecraft.server.ChunkProviderServer.b(ChunkProviderServer.java:115)
    2011-02-27 21:50:03 [SEVERE]     at net.minecraft.server.World.c(World.java:202)
    2011-02-27 21:50:03 [SEVERE]     at net.minecraft.server.World.h(World.java:1470)
    2011-02-27 21:50:03 [SEVERE]     at net.minecraft.server.World.g(World.java:1434)
    2011-02-27 21:50:03 [SEVERE]     at net.minecraft.server.MinecraftServer.h(MinecraftServer.java:329)
    2011-02-27 21:50:03 [SEVERE]     at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:253)
    2011-02-27 21:50:03 [SEVERE]     at net.minecraft.server.ThreadServerApplication.run(SourceFile:366)
    2011-02-27 21:50:03 [INFO] Chunk (0, 149) stored at  (6, 136)
    2011-02-27 21:50:03 [SEVERE] java.lang.Throwable
    2011-02-27 21:50:03 [SEVERE]     at net.minecraft.server.LongHashtable.get(LongHashtable.java:31)
    2011-02-27 21:50:03 [SEVERE]     at net.minecraft.server.ChunkProviderServer.b(ChunkProviderServer.java:107)
    2011-02-27 21:50:03 [SEVERE]     at net.minecraft.server.World.c(World.java:202)
    2011-02-27 21:50:03 [SEVERE]     at net.minecraft.server.World.h(World.java:1470)
    2011-02-27 21:50:03 [SEVERE]     at net.minecraft.server.World.g(World.java:1434)
    2011-02-27 21:50:03 [SEVERE]     at net.minecraft.server.MinecraftServer.h(MinecraftServer.java:329)
    2011-02-27 21:50:03 [SEVERE]     at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:253)
    2011-02-27 21:50:03 [SEVERE]     at net.minecraft.server.ThreadServerApplication.run(SourceFile:366)
    
    Running on Windows 7 Ultimate x64 build 7600

    Java version "1.6.0_23"
    Java(TM) SE Runtime Environment (build 1.6.0_23-b05
    Java HotSpot(TM) 64-Bit Server VM (build 19.0-b09, mixed mode)

    Build-Jdk: 1.6.0_20
    Implementation-Title: CraftBukkit
    Implementation-Vendor: Bukkit Team
    Implementation-Version: git-Bukkit-0.0.0-457-g434ce6d-b439jnks

    Plugins:
    -ClothColor_latest
    DeathChest
    dynmap
    Essentials
    EssentialsBan
    EssentialsChat
    EssentialsEco
    EssentialsGod
    EssentialsGroupBridge
    EssentialsHelp
    EssentialsHome
    EssentialsProtect
    EssentialsServerlist
    EssentialsSpawn
    EssentialsTele
    EssentialsWarp
    FakePermissions
    Flashlight v1-0-3
    GroupManager
    LWC
    Multiverse
    Slowhealth
    Tpack
    VoidMage
    WorldEdit

    Yes, I understand that Essentials is buggy, stupid, etc. Whatever. I don't need to hear that. I'm almost sure the problem lies either in how Minecraft Server is rendering a specific chunk, (0, 149), or that Dynmap is being retarded and I need to wipe the files from the web folder.

    The map in question is fairly large, and would require hours in an editor to re-locate everyone's buildings over to a new map. Can this map be salvaged without moving all my users' buildings to a new server?

    Any help is much appreciated. Thank you guys for helping people out of tight squeezes.
    --- merged: Feb 28, 2011 5:53 AM ---
    Update: Shortly after the writing, a user noticed some "griefing" done to one of his structures. I counted the blocks and it was a 16x16 area, which is the size of a chunk. I closed the server, opened up MC edit, and restored the chunk from a backup. Hope this helps anyone with the same problem.
     
  2. Offline

    Tame

    I have the same issue but I have no backup so if you knew any other way that'd be great...
     
  3. Offline

    AkaAnonymous

    You can find the chunks in MCEdit and delete them. Just select the affected chunk, if you can find it, and use the chunk control tool to delete the bad chunk. Paste it over with something nearby.
     
Thread Status:
Not open for further replies.

Share This Page