🍌 Preview 1.21.130.20

[gleaming bobcat]

i wonder if us not getting static_light this preview means we won't see it until 140

[winged estuary]

???

[gleaming bobcat]

i mean like, i assume this preview cycle they might focus on the VV changes they made in this preview.

instead of adding even more stuff

[winged estuary]

I will remind you we got custom biomes back in the last preview of .100

[gleaming bobcat]

i know they can add more features in later previews of an update

just more "will the other stuff they add this cycle be more VV related things or will they focus on just improving the things they did this preview"

[winged estuary]

Has anyone tested if the new connection trait applies to chest?

[hoary carbon]

seems vanilla blocks don't use it at all

(yes i have upcoming creator features enabled)

[placid gate]

But this component was already used before

[charred crescent]

@sullen fog, do you know anything about the more recent loot table APIs in scripting? I think I see a couple of issues to report.

[sullen fog]

I don't but I can forward feedback if you'd like

[charred crescent]

1️⃣ The APIs seem to be really complete, but the SetBannerDetailsFunction class seems to be missing a couple of the properties on the corresponding loot table object: base_color and patterns.

Here's a working example:

{
  "pools": [
    {
      "rolls": 1,
      "entries": [
        {
          "type": "item",
          "name": "minecraft:banner",
          "functions": [
            {
              "function": "minecraft:set_banner_details",
              "type": 0,
              "base_color": "red",
              "patterns": [
                {"pattern": "stripe_right", "color": "blue"}
              ]
            }
          ]
        }
      ]
    }
  ]
}

2️⃣ What's up with LootTableEntry? It seems like this is implying a directly nested loot table as opposed to a path reference. To my knowledge, Bedrock loot tables have never supported directly nested tables. (If it does, please let me know how!)

Thanks in advance!

[sullen fog]

I forwarded the feedback!

[charred crescent]

(Sorry, you're my only contact!)

[sullen fog]

As a dev who latches onto any resource at my fingertips, I get it lol

[fresh mauve]

wait we can do that with set_banner_details? I thought we could only make it a illager banner or not?

[ocean iron]

Documentation lied to you again

[fresh mauve]

yeah

[charred crescent]

Yeah, test it for yourself.

[winged estuary]

Have you created this bug report yet btw?

[fresh swan]

Yeah, I have reported the bug here: https://mojira.dev/MCPE-229476

[winged estuary]

🙏 Tysm.

[fallow nest]

No problem

[placid gate]

This bug also affects 1.21.130.22

[timid wren]

my custom biomes seem to be working fine? whats the issue

[winged estuary]

The biome itself is registered but nothing applies. No features, nada.

[timid wren]

strange mine works 100% fine tho, is this in a different version?

[winged estuary]

In 1.21.130.20

[timid wren]

fair enough, im not in preview lol

theyl prob fix it since thats a preview ver tho

[placid gate]

I have some feedback. I noticed that, starting with this Preview, it's no longer possible to export structures on mobile. In my opinion, as a Marketplace creator who doesn't own a computer, this is a very bad change. It would be good to have official support for exporting structures on mobile, or to reactivate the export of structures on mobile, because honestly, this change is very bad and greatly harms creators who don't have a computer.

[winged estuary]

Navi is the Scripting lead, not this. Please don't ping Mojangsters or reply to unrelated stuff.

[rigid wren]

mobile devices are computers :P

[ocean iron]

https://feedback.minecraft.net/hc/en-us/articles/360058571432-Minecraft-Beta-1-16-230-50-Xbox-One-Windows-10-Android
The 1.16.230.50 changelog says

Structure blocks can now be exported on Android

[carmine ivy]

Yeah, that was like during pre-android 11.

so people can still do their stuff just fine. now due to google, yeah you can't do anything much now and should expect for something like this to break.

I don't think it's a mojang problem but rather just google locking things down to some extent. due to their policy basically not being able to expose the com.mojang folder anymore, they have to comply or just don't exist in the store.

[rich spire]

It didn't save structures in com.mojang tho, you were able to select any arbitrary output folder and file name

Someone had to go and intentionally disable this awesome feature, seemingly for no reason :(

[carmine ivy]

yeah it did not save but uses some builtin save location.

though that also falls under the policy as well unfortunately.

you can't put it on nearly any folders except the download folder anyways.

[placid gate]

Therefore, they could open the screen to share the mcstructure file as a screenshot.

[carmine ivy]

Due to how mojang is playing really safe with stuff like this, i doubt that's gonna happen.

Hell, we don't even get export worlds so what do you expect.

[placid gate]

I doubt it too, but I'm suggesting a great alternative to provide good functionality without suffering from platform rules. Creators are important to Minecraft; honestly, it would be the least they could do.