Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FML detected the backup level.dat is being used #224

Closed
AlleinSoldat opened this issue Sep 30, 2018 · 7 comments
Closed

FML detected the backup level.dat is being used #224

AlleinSoldat opened this issue Sep 30, 2018 · 7 comments

Comments

@AlleinSoldat
Copy link

I travel a lot so I use my laptop consistently. So, I transfer all of my progress between my laptop and my desktop. The save game I used first on my desktop after update and it's throwing that error. If I click yes on it, it replaces blocks I've places with either air or some random block like stairs. I have attached screenshots. If I revert back to version 1.0.16, everything works just fine on both computers.

Steps to Reproduce (for bugs)

  1. Transfer save game from one PC to another
  2. Open save in game

Client Information
Modpack Version: 1.0.17
Server/LAN/Single Player: SSP
Optifine Installed: Nope
Shaders Enabled: Nope

stoneblock fml error

2018-09-30_13 22 10

@Sunekaer
Copy link
Owner

Sunekaer commented Oct 1, 2018

what blocks from what mods has been removed?

@TigerWalts
Copy link

TigerWalts commented Oct 1, 2018

I have been dealing with the same issue.

It's considering the FML data in level.dat to be invalid. It falls back to the level.dat_old. That one also fails but it retains the Data node but rebuilds the FML and forge nodes. But because it considers the old FML data to be invalid it ignores it and also skips converting block ids in the region files.

Looking at the level.dat file from before and after updating, a lot of id/index numbers that blocks are registered with have changed, there are 6 more blocks and they would all been assigned ids anew.

You may want to check if this is a known issue with certain Forge versions.

EDIT, this is a likely contender: MinecraftForge/FML#524
It's from a few years back but it's related.


The issue appears to be that there are too many blocks:

Exception reading C:\Users\tiger\Documents\Minecraft\Instances\StoneBlock (1)\saves\world\level.dat
java.lang.RuntimeException: Invalid id 4096 - maximum id range exceeded.
	at net.minecraftforge.registries.ForgeRegistry.add(ForgeRegistry.java:296)
	at net.minecraftforge.registries.ForgeRegistry.loadIds(ForgeRegistry.java:694)
...

1.0.17 busts the id limit, this causes an Exception which prevents the id remapping from happening.

@tjd46
Copy link

tjd46 commented Oct 1, 2018

I think @TigerWalts is right as if I add https://minecraft.curseforge.com/projects/notenoughids even my old world loads right up fine.
Another alternative might be https://minecraft.curseforge.com/projects/jeid

@Sunekaer
Copy link
Owner

Sunekaer commented Oct 3, 2018

does it work for you adding https://minecraft.curseforge.com/projects/notenoughids @AlleinSoldat ?

@AlleinSoldat
Copy link
Author

Haven't had a chance to try. I was stuck at work all day yesterday. I'll give it a shot right now and report back.

@AlleinSoldat
Copy link
Author

Seems to work with the addition of notenoughids. Thanks for the help everyone!

@Sunekaer
Copy link
Owner

Sunekaer commented Oct 7, 2018

1.0.18

@Sunekaer Sunekaer closed this as completed Oct 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants