🍌 Preview 1.21.80.27

[fervent mauve]

Can I make Custom Biomes?

No. Custom biomes have been broken since 1.18. Mojang is fully aware of this and working hard to bring back this capability.

Here is the bug report: https://bugs.mojang.com/browse/MCPE-100700

Apr 9, 2025, 12:02 AM

[ivory gorge]

And this week's preview fixed it?

[rose rain]

Correct!

[raven helm]

kind of, yeah

[ivory gorge]

Was it fixed or did they just give is a workaround

[round ingot]

Ahh... the city life
-# Sponsored by Vibrant Visuals 🤣

[pastel terrace]

WOOO

[ancient thicket]

=D

[worn orchid]

I'd say fixed

[rose rain]

I say both.

It isn't fully fixed, it's using sub biomes, but fixed enough.

[heady valve]

With caves and cliffs completely changing the way biomes and terrain as a whole is generated, most of the components prior to 1.17 won't work.

Speaking of which, I'd like a list

[rose rain]

Of.

[heady valve]

Of biome components that don't work. Speaking of which, it appears that the biome JSON link in their official docs isn't working anymore

It redirects to here. https://learn.microsoft.com/en-us/?view=minecraft-bedrock-experimental

[rose rain]

Mike changed the ToC yesterday.

[heady valve]

Ok I found the component list now. I had to go through another page to find it.https://learn.microsoft.com/en-us/minecraft/creator/reference/content/biomesreference/examples/componentlist?view=minecraft-bedrock-experimental

[red flower]

We don't have subcommand support yet do we?

[heady valve]

Nope

[cloud jackal]

hello everybody my name is markiplier

wrong chat

[grand talon]

Hello welcome, My name is goodbye

[cloud jackal]

hello good my name is come

[sly hazel]

wait nintendo switch has preview edition??

[heady valve]

No

[bronze kindle]

Does anyone know if Mojang is going to namespace the vanilla biomes before custom biomes release to stable?

[rose rain]

The video said so.

[bronze kindle]

Okay, so, yeah: cave biome replacements are iffy but they kinda work.

[rose rain]

Iffy how? They seem to work correctly for me.

[heady valve]

I wonder how they plan on truly supporting custom biomes? Since right now you can only replace existing ones

[rose rain]

Unlikely it seems. Especiallly if marketplace support and then trying to fit it biome gen and terrain blending.

[bronze kindle]

It's not an intuitive experience. You set up a custom biome that has no attributes on its own and then use features to actually do anything. Aside from mob spawning, you'd might as well just use feature-driven cave biomes… which would give you way more placement control and actually allow you to generate inside normal stone caves.

[rose rain]

Vanilla does this so I suspect thats why Mojang did this way.

My feature placement right now is also oh so iffy.

Been a while since I touched world gen and I forgot y dist is world relative not chunk.

[heady valve]

That's what I'm saying. Right now, you can't make cave biomes where there aren't any

[rose rain]

A dirty patch is making the whole underground a generic cave biome.

*For Mojang Vanilla Gameplay team to consider.

[heady valve]

That would work, but as you said, it's a dirty patch

[bronze kindle]

I think it's actually totally fair that that space is considered its own biome.

[heady valve]

If only we could have more custom biome placement conditions. Imagine being able to query vanilla noise routers

[bronze kindle]

We really, really need the ability to query the noise curves from features at least.

[rose rain]

World Gen QNA 2 when.

[unkempt holly]

I'm still really confused on how they implement 3D biomes in bedrock, somehow you can be in multiple biomes on same y level (excluding underground biomes) given same position

[solar herald]

you want MORE? Are you not entertained?!

[rose rain]

💔 Scripting got 2...greedy Navi.

[chilly herald]

Is that a gladiator quote?

[heady valve]

I can see the nether getting biome replacement support without any user facing API changes, but I'm a little concerned about the end

[magic vale]

but we still don't have the air tag qna

[rose rain]

It makes entirely sense though for overworld support first/only.

[heady valve]

Of course

One step at a time

[bronze kindle]

I will say this, though: I'm realizing this system can be compatible with a more generic system in the future.

[gaunt veldt]

Sorry, I will look to fix this in the next doc update. Just trying to refactor and autogenerate (with annotation) more things.

[heady valve]

Goodbye terrain shape related components 🫡

[bronze kindle]

I think the future should hold noise target thresholds (a la Java) with a convenience property for just replacing a vanilla (existing) target.

That way we can still have a weighted system that's weighted per 5D slice.

[heady valve]

I'm imagining molang support for biome placement condition

[bronze kindle]

I don't think it needs it.

And that's crazy that I am saying that.

[heady valve]

Well I'm just thinking about the possibilities there. You can have conditions that query different kinds of noise routers. Maybe even custom ones

Even check the Y value for deep biomes, or biomes near the height limit

[bronze kindle]

I genuinely think that something like…

"minecraft:noise_targets": {
  "temperature": [-0.3, 0],
  "continentalness": [0.5, 1],
  …
  "weight": 3
}

…Would be delightfully easy to support… one day.

[heady valve]

I suppose so. Then custom noise routers

[bronze kindle]

I think that's fine. You could consider some additional properties to be key-value pairs binding noise identifiers to range selectors.

[heady valve]

But in all seriousness, yeah your solution is definitely more elegant and intuitive than just slapping molang on

[bronze kindle]

Yeah, to maintain performance, the values should be static instead of using Molang.

The biggest disappointment to me, as a Marketplace developer, is that it won't be possible to target "middle spaces" between biomes. I'd love to add sandy plains or chaparrals transitioning between vanilla biomes.

That's just totally impossible here.

[heady valve]

With your suggestion, that could be possible

[bronze kindle]

Alternatively, if Mojang opened up real noise queries to Molang in features, I could just do it myself the hard way.

[honest yoke]

Why??
Who asked for this?

[worn orchid]

Just filter out undefined?

Doesn't seem like a big deal

[honest yoke]

it's a headache, why do i have to pay attention to the headers and labels when they do nothing?

header
toggle
label
header
toggle

will return
undefined
boolean
undefined
undefined
boolean

instead of
boolean
boolean

[worn orchid]

It's literally .filter(x=>x) 13 chars

[magic vale]

how did it break existing things if those things didnt include headers and labels

[worn orchid]

It's a change exclusive to v2

There's an inherent expectation for breaking changes anyways

[magic vale]

that would filter out false, 0 and empty strings so you'd have to be more strict .filter(x => x !== undefined)

[worn orchid]

Ah right

[honest yoke]

i didn't, just saying it's a useless change that no body asked for

[placid pewter]

Why not use minecraft:geometry.full_block geometry?

You can even give it its own culling rules, the bone name should just be block iirc

[humble lichen]

https://tenor.com/view/saul-goodman-better-call-saul-saul-goodman3d-meme-breaking-bad-gif-24027228

[magic vale]

I'm asking why the change was needed too

[magic vale]

not data-driven so I didn't know if that would work since other things like scale and bone visibility don't

i'll try it

[magic vale]

can't get it to work

[bronze kindle]

I know my medicine is making me kinda dumb… I just don't think I understand how to fully optimize my custom block culling using the new culling rule conditions.

I'm trying to imagine how to cull lateral faces from a lower slab. I want to cull them when a fellow lower slab or even a right-side-up stair is adjacent. The former case is simple enough… but the latter? I just don't see how that's possible here.

I'm also quite surprised that condition is now required when one of its values is "default". I think the schema should be reconsidered.

For now, I supposed custom walls, lower slabs, and upper slabs could all have their own independent culling layers to get at least somewhat improved culling. I don't think it'd be reasonable to try to handle stairs.

@solar herald, is the above kinda what was intended for now?

[devout inlet]

Not sure if i missed it, but can query.graphics_mode_is_any detect vibrant visuals? Or would it be the same as deferred

We have some entities that disable shadows in their rc but they're basically just black with vv, was hoping to do a query to fix that

[gaunt sinew]

vv is the same as deferred, so it should still work. Although these queries are currently experimental so they might rename the deferred option to vibrant_visuals or something like that when they are released

[devout inlet]

Alright cool thanks, I'll have to give that a try

[trim siren]

Realms outdated?

[placid pewter]

huh, the MS docs state that it can have it's own culling rules... not sure if it's a mistake or a bug

[rocky vine]

Custom biomes :0

[rose rain]

Crying...we all had the smae idea.

[rocky vine]

lol

[wintry crown]

The condition field being required is a mistake and will be fixed. As for the other things, that will be looked at but I don't think the new culling rule conditions will cover everything.

[vast agate]

For the stairs don't those 2 blocks share minecraft:vertical_half?

Or does both blocks have to be the same to use state based conditions

[near kelp]

THEYRE BACK ???? ? ? ?

[rose rain]

Yes.

[near kelp]

so

hi bedrock community

[spark wing]

Custom Buttons?

[vast agate]

No way to make a redstone source

Also to make redstone components there is the issue of them passively lagging the game in mass quantities

[spark wing]

Custom buttons

[vast agate]

Oh UI buttons

[spark wing]

I want my bedrock minecraft to have buttons like in the picture above

[heady valve]

Likely won't see it for a while. Before having custom buttons, we should have custom input mapping in general.

[bronze kindle]

Thanks for getting back to me. I'm considering updating all my existing stuff to optimize culling as much as I can. Would you be able to tell me if there are any other culling conditions being considered in the immediate future?

If not, I'll go forth and prepare for this current tech to optimize slabs and walls as best as I can.

[toxic rock]

@near kelp yo

[near kelp]

hi

[worn orchid]

Chinacraft

[vast agate]

The things I'd do do be able to apply box UV textures to specific bones

[vast agate]

This is for blocks

[gusty sphinx]

When would this fully be released? I really cant wait for custom biomes

Like ik I could code up the biomes right now but I wanna wait until it fully release

[raven helm]

Well 1.21.80 as an experimental feature probably

As a stable it might take a really long time to get there

[gusty sphinx]

Just wondering when 1.21.80.27 should fully release

[gusty sphinx]

And yes thats true, Arent half the experiments been there for years?

[raven helm]

June ig

[gusty sphinx]

Not far tbh

[wintry crown]

We are planning some minor updates to culling conditions, but nothing expansive.

[bronze kindle]

Okay, cool. I'll start optimizing culling as best I can. Thank you.

[rose rain]

Anyone hear anything about Preview for Consoles thjis week?

[solar herald]

PS5 is the only one that should have been delayed. I think the latest is that one is skipping Preview this week.

[wheat adder]

Didn’t ps get the 1.21.80.26 update (saw it in a toycat video)

[solar herald]

yeah - .24, .25 and .26 are all the same.

[wheat adder]

Why is it different in the first place though

[solar herald]

When we submit builds to all the different platform holders, sometimes things trip in the ingestion and processing. Often, the fastest way to resolve this is to just increment the build number and send it again. Or sometimes we catch a very last minute severe crash on one platform and we do a surgical fix and that causes the build number of that platform to increment.

[wheat adder]

Makes sense, btw have you been made aware of vv being broken when in the editor screen

[solar herald]

thanks 🙂 I'm sure the team is looking into this!

[tiny tulip]

And otherwise make a bugreport so it doesn't get missed 🤭

[rose rain]

Ah so PS5 isn't getting Preview 1.21.80.27 then? Or did I misinterpret that?

[wheat adder]

It’s not getting this weeks preview

[solar herald]

let me check

correct. no PS5 this week. should be back for next week's Preview. appologies for the inconvenience.

[brave hollow]

preview day has been cancelled

:floppybanana:

[pastel terrace]

Would varying increment be reset every 1.xx, such as 1.22, etc.
Like would they all show the same 1.22.xx and then the build number would vary afterwards?

I'm trying to say, would they synchronise again at each Title Update, but I couldn't say that for some reason xD

[solar herald]

yeah, since that's a more "major" update.

[bronze kindle]

Aww, man, I'd thought that BlockCustomComponentInstance would return the parameters of the custom component. I wonder if that's planned… or if the refernced interface is just a means of error dodging.

[humble lichen]

i wonder if theres an effective way to deal with this in the future

i hope filter is good enough for this

[devout inlet]

Just curious, why is it a problem?

.filter(x => x !== null) will result in the same response as before

[humble lichen]

for me, a few elements can be hidden or shown depending on player's condition (a tag)

so i had to make a whole function that pushes elements

[raven helm]

I think .filter(x => x) will work too?

[devout inlet]

that'll also remove 0s and empty strings

[raven helm]

Oh

[solid pelican]

Weird bug that would happen when you are using a mobile device and if you turn off your phone in minecraft not in the pause menu. Then turn it back on it will do this.

[pale terrace]

It might be intended thing since switching off your phone does not pause the game. which, it will do client-side and internal server syncing thing when the phone is back on, it'll do that until the game thinks both client and server are fully synced.

[solid pelican]

I don't think the shield acting like that should be intended

[pale terrace]

Wrong subject. but yeah they shouldn't be like that

it's just a visual bug with pause feature. shouldn't bother anyone that much.

[solid pelican]

Tbh, I was only talking about the shield. I was just explain how it started

[full monolith]

Insert [Always been.] meme

[solar herald]

As an LLM, I do not lie, I hallucinate.

[rose rain]

https://tenor.com/view/drake-yachty-censored-not-drake-tech-support-gif-8658410013845332703

Then can you hallucinate air tag please?

[gusty sphinx]

What addon gives the Java screen? Or is that the old console edition addon?

[solid pelican]

Just a resource pack, I have a couple of texture packs that make it look like old minecraft but in java

Still bedrock, just looks like java

[broken walrus]

Vdx java ui(vdx desktop ui)

[bronze kindle]

I wonder if it would be possible for the team to add multiple culling layers to a block. For example, bottom slabs could have "down" and "side.lower_half". An upper half slab culling rule could then specify that the up face should be culled when the block above has the "down" layer.

(I have no idea how culling works in the engine, so this may be infeasible or insufficient performance-wise.)

Right now, we can only do exact matches to itself… which is painfully limiting.

[glass timber]

Can u send me a link for that?

[violet prairie]

https://mcpedl.com/vdx-legacy-desktop-ui/

search engine exists

[fervent mauve]

When Preview?

Mojang devs are off for the weekend, so it is unlikely to be preview day my dudes

When do Previews usually happen?

Previews starting from March 11, 2025 will try to release on a Tuesday: https://bsky.app/profile/jorax.bsky.social/post/3lk4lhrpmoc2p

Apr 19, 2025, 12:02 AM

[gusty sphinx]

Aight

[vast agate]

So uh

Is there any way of making this work

The dark patch that is surrounded is a leaf block

And is getting culled from those 3 directions from the non-full slab block

Also when 2 of the same permutation is placed on top of each other the bottom/top face is culled

Less of an issue for top, much more of an issue for bottom