Problem XyCraft world breaking bug

[LightKnight]

So it is a new server , and when i pass near a place ( red rock canyon ) the server gives " Internal server error "
and this is the crash -

Spoiler

[WARNING] [Minecraft] Failed to handle packet for : java.lang.NullPointerException
java.lang.NullPointerException
at soaryn.xycraft.world.gen.WorldPopCrystal.a(WorldPopCrystal.java:81)
at soaryn.xycraft.world.gen.WorldPopulator.genOre(WorldPopulator.java:54)
at soaryn.xycraft.world.gen.WorldPopulator.genOres(WorldPopulator.java:80)
at soaryn.xycraft.world.gen.WorldPopulator.gen(WorldPopulator.java:45)
at soaryn.xycraft.world.gen.WorldPopulator.generate(WorldPopulator.java:39)
at cpw.mods.fml.common.registry.GameRegistry.generateWorld(GameRegistry.java:91)
at im.a(ChunkProviderServer.java:259)
at zz.a(Chunk.java:1258)
at im.c(ChunkProviderServer.java:153)
at il.<init>(PlayerInstance.java:43)
at ik.a(SourceFile:172)
at ik.d(SourceFile:300)
at gm.d(ServerConfigurationManager.java:220)
at iv.a(NetServerHandler.java:415)
at eb.a(SourceFile:136)
at cg.b(TcpConnection.java:458)
at iv.d(NetServerHandler.java:141)
at iw.b(NetworkListenThread.java:57)
at ht.b(SourceFile:30)
at net.minecraft.server.MinecraftServer.r(MinecraftServer.java:703)
at ho.r(DedicatedServer.java:269)
at net.minecraft.server.MinecraftServer.q(MinecraftServer.java:599)
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:497)
at fy.run(SourceFile:849)

any fix for this ? except deleting the map or something like that

 

[Spoo]

Before messing with anything, save a backup copy of your world.

Since Xycraft is causing the crash, you could remove Xycraft and reload the world. After saving, add it back in. Beware that doing so will remove all Xycraft items and blocks from existing chunks (including stuff you've built with). You'll need to explore new chunks to find Xycraft ores.

(Or just stay away from the red rock canyon until there's an update to Xycraft.)

 

[Naolas]

After you verified it is Xycraft, you could try disabling certain blocks individually to narrow down which of them is causing the issue.

Once you figured that out, you could only chunkload the offfending area and then remove the block you previously identified from it.

It will take time and many restarts and file copies, but it would reduce the impact of how many blocks would be removed.