Jump to content

Level.dat problem on even new worlds


Adarcer

Recommended Posts

Was hoping someone could help me I am making a modpack and need too create a new world at times too check orespawn, biome decoration spawn, dungeons , lakes  etc, but every time i try too create a new world i get this error "Forge Mod Loader detected that the backup level.dat is being used" I can get into old world by renaming the level.dat_old so forge cannot find it, but new worlds are blocked. have tried making a new instance in multimc, and still had same problem.

latest.log

crash-2017-12-12_21.12.00-server.txt

Link to comment
Share on other sites

sorry that was newest crash log cause i pushed the button that took me back too menu instead,here is the tail end of the crash log while trying to create a new world. just need advice on what I need to do the crash log does not tell me which mod if any is causing the problem 

 

[18:37:11] [Server thread/ERROR]: Exception reading C:\Games\Minecraft\MultiMC\instances\Mining Survival 1.10.2\minecraft\saves\HopeThis Works\level.dat

java.lang.ArrayIndexOutOfBoundsException: 640

at net.minecraft.util.IntIdentityHashBiMap.func_186814_a(IntIdentityHashBiMap.java:100) ~[od.class:?]

at net.minecraftforge.fml.common.registry.FMLControlledNamespacedRegistry.addObjectRaw(FMLControlledNamespacedRegistry.java:579) ~[FMLControlledNamespacedRegistry.class:?]

at net.minecraftforge.fml.common.registry.FMLControlledNamespacedRegistry.add(FMLControlledNamespacedRegistry.java:482) ~[FMLControlledNamespacedRegistry.class:?]

at net.minecraftforge.fml.common.registry.FMLControlledNamespacedRegistry.loadIds(FMLControlledNamespacedRegistry.java:776) ~[FMLControlledNamespacedRegistry.class:?]

at net.minecraftforge.fml.common.registry.PersistentRegistryManager.loadPersistentDataToStagingRegistry(PersistentRegistryManager.java:460) ~[PersistentRegistryManager.class:?]

at net.minecraftforge.fml.common.registry.PersistentRegistryManager.injectSnapshot(PersistentRegistryManager.java:280) ~[PersistentRegistryManager.class:?]

at net.minecraftforge.fml.common.FMLContainer.readData(FMLContainer.java:327) ~[FMLContainer.class:?]

at net.minecraftforge.fml.common.FMLCommonHandler.handleWorldDataLoad(FMLCommonHandler.java:418) ~[FMLCommonHandler.class:?]

at net.minecraft.world.storage.SaveFormatOld.loadAndFix(SaveFormatOld.java:118) [azz.class:?]

at net.minecraft.world.storage.SaveHandler.func_75757_d(SaveHandler.java:121) [azy.class:?]

at net.minecraft.server.integrated.IntegratedServer.func_71247_a(IntegratedServer.java:76) [bzl.class:?]

at net.minecraft.server.integrated.IntegratedServer.func_71197_b(IntegratedServer.java:197) [bzl.class:?]

at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:431) [MinecraftServer.class:?]

at java.lang.Thread.run(Unknown Source) [?:1.8.0_151]

[18:37:21] [Server thread/ERROR]: Encountered an unexpected exception

java.lang.NullPointerException

at net.minecraft.world.WorldProvider.func_76558_a(WorldProvider.java:37) ~[atl.class:?]

at net.minecraft.world.WorldServer.<init>(WorldServer.java:113) ~[ls.class:?]

at WorldServerOF.<init>(WorldServerOF.java:25) ~[WorldServerOF.class:?]

at net.minecraft.server.integrated.IntegratedServer.func_71247_a(IntegratedServer.java:81) ~[bzl.class:?]

at net.minecraft.server.integrated.IntegratedServer.func_71197_b(IntegratedServer.java:197) ~[bzl.class:?]

at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:431) [MinecraftServer.class:?]

at java.lang.Thread.run(Unknown Source) [?:1.8.0_151]

[18:37:22] [Server thread/ERROR]: This crash report has been saved to: C:\Games\Minecraft\MultiMC\instances\Mining Survival 1.10.2\minecraft\crash-reports\crash-2017-12-13_18.37.21-server.txt

[18:37:22] [Server thread/INFO]: Stopping server

[18:37:22] [Server thread/INFO]: Saving players

[18:37:22] [Server thread/INFO]: Saving worlds

[18:37:22] [Server thread/INFO] [FML]: Applying holder lookups

[18:37:22] [Server thread/INFO] [FML]: Holder lookups applied

[18:37:22] [Server thread/INFO] [fluxnetworks]: Removed Networks

[18:37:22] [Server thread/INFO] [mcjty.lib.varia.Logging]: RFTools: server is stopping. Shutting down gracefully

[18:37:22] [Server thread/INFO] [mcjty.lib.varia.Logging]: RFTools: server is stopping. Shutting down gracefully

[18:37:22] [Server thread/INFO] [FML]: The state engine was in incorrect state SERVER_STARTING and forced into state SERVER_STOPPED. Errors may have been discarded.

 

 

crash-2017-12-13_18.37.21-server.txt

Edited by Adarcer
Link to comment
Share on other sites

The thing in spoilers ... was a truly fresh world and was the end of the log when i pushed the button on client that would attempt too load the world anyways (either yes or no, one takes you back too menu)  ... can tell by the save name. the crash log had the right date and time, what seems funny too me is this is supposed too be a single player test world instance not a server instance. 

 

for some reason new games are being seen as old games... seem too have found a way around this i have to copy and paste the level.dat into another folder rename it to level.dat_old and move back into save folder... then new world loads up after the error message ... but that is extremely annoying too have too do any idea on how too fix this problem

 

 

 

Edited by Adarcer
Link to comment
Share on other sites

No with just forge installed on a separate instance it works as expected.. was kinda hoping someone would know what mod was causing the problem or a possible mod conflict, as the error does not say what mod is causing the error. or some type off error message explanation page, that might give me a clue on what is causing the error. like for example is it a mod with worldgen, or a mob that i can disable, or a mod i can just outright remove.

Edited by Adarcer
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.



×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.