Then do the same for serverconfig and stats. (the issue will not be in DIM1 nor will it be in DIM-1)ĭo the same for region (this is all of your player made stuff + chunks) It will ask to overwrite the existing ones (in this new world that you have made.) press yes. Once I found the file that was causing the issue, I just missed it out in the copying process.įirst, copy over the DIM1 and DIM-1 over to this new world. it crashes when I launch minecraft itself with the erebus mod on it. Rinse and repeat.) Once I had found the file that was causing the issue, I would go into it and copy everything in it over to the new world file one by one, running minecraft, checking to see if the nether was working in-between every copy. (for example, copy in the data file, then load into the new world and check if the nether is working. The way I did it back in the day was by hand picking every file to see which one was causing the issue. I am uncertain as to where the actual issue was with the nether not working (as to in which file it is located in). Like a completely new world - like you would starting a new survival world. You need to single out specific world files and copy them over. Note: just copying the whole world will not work (since you are copying over the nether bug as well). I don't actually know what was causing the issue in the first place but I believe it might have been something to do with "experimental gameplay" or whatever. I loaded in (the only thing that was missing was my inventory but you can put that into a chest in your bugged world before moving files over to the new world) and the nether was working again. The actual overworld is basically chunks of the other files (I did this quite a while back and it took quite a bit of time to realise which files are responsible for what in the game, so I can't recall what files exactly). Discord is the best place to reach me for support. If it does work there then you can restart the server and copy the solo world file into Aternos and run the working file. Copy the world file onto your computer and go into that world in your solo player Minecraft. If a server has too much lag, it might randomly crash the client multiple times until it stops lagging. Crashing a server using the world height limit crashes both the server and client. Id love to see all the stuff you make so please send me screenshots or videos. I have one other suggestion that might work. Server-caused crashes It is very rare but possible for a server to cause the client to crash (particularly some of the buggy mods). MC Eternal is a large-sized pack with currently around 380 mods. DIM1 is the nether (pretty sure) and DIM-1 is the end. Recommended world type: BOP is suggested. minecraft, then saves) and copied over all of the data from my original world to this new world. Then, went into the game files (via %appdata%, then. Alright, so, it's been a while but I saw this pop up so I might as well answer it since I managed to fix it.įirst, I created a new world.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |