Updating to the latest version destroys my world

Question

Updating to the latest version destroys my world

Quietlee opened this issue a year ago · 3 comments

Quietlee commented a year ago

Describe the bug
A clear and concise description of what the bug is.

Updating from RegionsUnexploredFabric-0.4.1+1.20.1.jar to RegionsUnexploredFabric-0.5.1_02+1.20.1.jar completely breaks the world gen. A large portion of our spawn area consists of plains dirt with barley on it. After updating to the latest version this week all of the plains dirt disappears, leaving about 5 empty blocks on top of the underlying stone, the grass that would have been attached to the top layer of plains dirt is floating in the air and all of the structures (generated and player built) are all floating in the air where they used to be on plains dirt.

Crash Logs
Please add crash logs or latest logs to allow us to identify the error.

I asked my hosting site to roll back my server so I don't have access to the log. The game didn't crash, your mod just ruined a large portion of my world.

How To Reproduce
Steps to reproduce the bug: Updating to the latest version RegionsUnexploredFabric-0.5.1_02+1.20.1.jar

Version
Minecraft Version: 1.20.1

Modloader Version: Fabric

Mod Version: RegionsUnexploredFabric-0.5.1_02+1.20.1.jar

Screenshots
If applicable, add screenshots to help explain your problem.

The xaero world map initially goes black on the areas that contain plains dirt, everything is in shadow. If I use the /brush smooth command on areas it will update the lighting in those areas but the plains dirt has completely disappeared, leaving only stone underneath where it sued to be.

UHQ-GAMES · Answer 1 · 2023-09-01T01:55:04.000Z

this is because those blocks were renamed in this update and the game thinks they don't exist, so it just turns them to air. I believe you can use Blockswap mod to work around the issue by replacing the old blocks with the 0.5.0 equivalent on load. This is why I put the warning in the changelog for 0.5.0 as it is basically a fully remade update with a lot of breaking changes.

Quietlee · Answer 2 · 2023-09-01T08:22:08.000Z

Couldn't you just leave the name as it was so that you don't break every players world that were unfortunate enough to use your mod? This seems like a lot of work and grief just for a simple name change.

…

On Fri, 1 Sept 2023, 02:55 UHQ-GAMES, ***@***.***> wrote: this is because those blocks were renamed in this update and the game thinks they don't exist, so it just turns them to air. I believe you can use Blockswap mod to work around the issue by replacing the old blocks with the 0.5.0 equivalent on load. This is why I put the warning in the changelog for 0.5.0 as it is basically a fully remade update with a lot of breaking changes. — Reply to this email directly, view it on GitHub <#28 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASOCC6TV5NUWUQEXEBGPXYTXYE6AFANCNFSM6AAAAAA4FUNZYM> . You are receiving this because you authored the thread.Message ID: ***@***.***>

UHQ-GAMES · Answer 3 · 2023-09-01T13:47:28.000Z

I didn't like the names of the blocks so I felt they needed to be changed. That's why I put that warning about it in the 0.5.0 changelog and did it. Im sorry it damaged your world but mods generally don't update well and this update was a really big update that really changed almost everything.

Share to