mojira.dev

Jessica Ogle

Assigned

No issues.

Reported

REALMS-10470 Java Realms- new world started on 1.19 generating some chunks with 1.17 biome algorithm Awaiting Response MC-241021 Infinite Bad Omen Duplicate

Comments

Okay. So I went back into the realm and completed 4 adjacent maps, zoomed out twice. (Because that's what we started with, because kids LOL) (labeled Realm)

Then I created 3 different creative worlds.

Created in 1.17.1, stayed in 1.17.1, completed the same 4 maps. (labeled 1.17)

Created in 1.17.1, spawned in, flew straight up to look around, then exited without leaving world spawn. I then opened it in 1.19 and completed the same 4 maps. (labeled Exp.)

Created in 1.19, stayed in 1.19, completed the same 4 maps. (labeled 1.19)

 

Now, I'm not sure what the default render distance is on a realm... or if I have changed ours at some point... But the realm & the experiment look... similar. I'm guessing my singleplayer render distance is higher.

What I can't figure out is how/why the brand new world created on our realm just for 1.19 used 1.17 algorithms at world gen and then switched over before we explored anything.

 

[media]

Oops, I thought I put it in Realms to begin with.

 

Yes, once we get past a certain distance from spawn I think it's right. We haven't explored too very far yet.

There are no data packs or templates or anything. Just vanilla realm with a specific seed number.

 

I'm planning on getting on there today and actually doing some exploring to see just how far the glitch goes. We've been mining and trying to get everyone geared up first. 

No, there's still a problem. Look at the pictures. Spawn was supposed to be on a beach with ocean on one side, plains on the other, and a really cool mountain behind the village. Instead several chunks of river and mountain biome got pasted in and ruined the view and layout of the village. While that might not be that big of a thing, just aesthetic, the question remains: how and why did my realm use 1.17 terrain algorithms at all, when it is a native 1.19 realm? It shouldn't have been able to, it wasn't supposed to, therefore it's a bug.

The whole world was newly created on 1.19 just two days ago.

I have a video of the issue but I can't get it compressed small enough to upload here.

This is actually happening on new (non-migrated) accounts too.

 

This is happening on my son's account also. He owns both Bedrock/Windows 10 edition and (as of today) Java edition. The launcher does not recognize either of them.

 

I finally got the Microsoft store to re-download Bedrock, tried to log in, now it's been stuck on "Signing in with your Microsoft Account" for a good 10 minutes.

 

Microsoft broke Minecraft 😒

If max Bad Omen time is 1 hour and 40 minutes, how was it still showing xx:xx over an hour later with no additional pillagers killed?