Gruntastic

I believe everything is resolved as of now as efficiency works and durability is done through scripting.

To be honest, I haven't done anything with the biome files for quite some (been waiting for custom biomes to be supported again) so they might have fixed it, but there's a certain section specifically for the mesa that doesn't fall under any of the biomes in the biomes folder and can only be overwritten using the caves or overworld tags.

There is a tag 'caves' that overrides regular caves, for some reason, some biomes now fall use this tag.

Not sure when this was fixed, but it now works properly in the 1.19.80 betas

Added the mcaddon, just note the provided pack will only work for 1.19.80 and higher.

@Test Pattern, I'm not sure where I found this but this is the only way to tag blocks and items with minecraft tags (such as minecraft:is_pickaxe, minecraft:is_shovel, etc.) that I know of

Resolved with the addition of tags in recipes (though it would be nice if there was some documentation about these tags)

Not sure if we are meant to have access to vanilla states or not, but we can now use custom states in commands

The recipes that failed were shapeless recipes, I recently changed them to be shaped which fixed them being skipped but there is still hundreds of warnings appearing when loading a world which could potentially obstruct other actual issues. I'm not sure why this 'fix' was even needed in the first place. At least give us the option to disable warnings like this.

Still affects 1.19.50

Look for a dirt slab in the nature section, place it in a snowy biome and set the weather to rain, watch snow form on top of the slab.

That doesn't change the fact that these recipes are still not able to modified as they do not appear in the recipes folder.

This component along with other useful components have been removed for some reason, technically 'fixing' this bug but in the worst way possible.

Technically resolved with the addition of player actor properties, albeit in a roundabout way.

Resolved as of 1.19.2

Still occurs in 1.18 betas

This is still occurring in 1.18 betas, I've also seen instances of vanilla trees being cut at world borders now. Seeing as this report hasn't been updated yet, could a mod add the following to the report?

Steps To Reproduce:

1. Download the attached StructureCutBugTest.zip and install the behaviour pack

2. Load a world with the pack

3. Observe that supplied structure gets cut off at chunk borders

Observed Results:

• The structure gets cut off at chunk borders, the largest size structure possible for some reason is 48x48, though since the new terrain generation, any structure has the potential to get cut along a chunk border, even smaller structures or features like trees.

Expected Results:

• All structures are placed properly during terrain generation and creators are able to chain large structures together (using sequence and scatter features) without structures being cut off at chunk borders.

I've updated this bug report to provide clearer examples of what's broken. There are still other components that are broken like the shooter component in MCPE-101146 but this report is mainly about melee items.

Still broken in 1.18 betas

The issue occurs when running the effect command with the run_command component for events, any effect that uses ticks for time (instant damage, instant health, saturation) uses seconds instead, whereas from a regular command (not part of an event, just run from the command window) use ticks for time correctly.

Pre caves and cliffs there was an abundance of cave entrances, while there are a handful of the smaller caves around now, there isn't a lot. Perhaps that's what Mojang wants?

I'll remove 1.18.0.20 for now

Cave entrances seem pretty common on the surface now, there's still not many small entrances but there are plenty of big ones, not sure if this is fixed or not yet.