Merge branch 'Bedrock-OSS:wiki' into wiki

docs/blocks/block-format-history.md

@@ -16,6 +16,23 @@ mentions:
 -   Updated `minecraft:destructible_by_mining`
     -   Released `item_specific_speeds` parameter from experimental
 
+<Tag name="experimental" />
+<Label color="blue">Upcoming Creator Features</Label>
+
+-   Added `minecraft:item_visual`
+    -   Determines how this block is displayed as an item.
+    -   Contains `geometry` which determines the displayed geometry component.
+    -   Contains `material_instances` which determines the displayed material instances component.
+-   Added `minecraft:liquid_detection`
+    -   Determines how this blocks behaves with different types of liquid.
+    -   Contains `detection_rules` which each contain the following parameters:
+        -   `liquid_type` determines which type of liquid this rule applies to. Currently only `water` is supported.
+        -   `can_contain_liquid` determines whether the liquid type can occupy the same space as this block e.g., waterlogging.
+        -   `on_liquid_touches` determines what happens when the liquid type flows into the block.
+        -   `stops_liquid_flowing_from_direction` determines an array of directions that the liquid cannot flow out of this block from.
+-   Updated `minecraft:material_instances`
+    -   Updated `ambient_occlusion` instance parameter to require a float which determines ambient occlusion intensity.
+
 ## 1.21.40
 
 ### Components
@@ -31,11 +48,11 @@ mentions:
 <Tag name="experimental" />
 <Label color="blue">Upcoming Creator Features</Label>
 
--   Updated `minecraft:destructible_by_mining`
-    -   Added `item_specific_speeds` which determines the `destroy_speed` for each `item` descriptor in an array.
 -   Added `minecraft:redstone_conductivity`
     -   Contains `redstone_conductor` which determines whether this block conducts redstone.
     -   Contains `allows_wire_to_step_down` which determines whether redstone wire can travel down the side of this block.
+-   Updated `minecraft:destructible_by_mining`
+    -   Added `item_specific_speeds` which determines the `destroy_speed` for each `item` descriptor in an array.
 
 ## 1.21.10
 

docs/json-ui/json-ui-documentation.md

@@ -642,7 +642,7 @@ Most people use them by giving them the same value:
 	width=782
 />
 
-However, what happens when they have different values? Let's look at happens when `anchor_from: center` and `anchor_from: top_left`. It's the best example to demonstrate what's really happening.
+However, what happens when they have different values? Let's look at what happens when `anchor_from: center` and `anchor_to: top_left`. It's the best example to demonstrate what's really happening.
 
 <CodeHeader>RP/ui/example_file.json</CodeHeader>
 

docs/json-ui/json-ui-intro.md

@@ -18,7 +18,7 @@ mentions:
     - LeGend077
     - mark-wiemer
     - TheItsNameless
-    -
+    - ThomasOrs
     - QuazChick
 description: Introduction to JSON UI.
 ---
@@ -27,6 +27,7 @@ description: Introduction to JSON UI.
 
 :::warning
 JSON UI is being deprecated in favor of [Ore UI](https://github.com/Mojang/ore-ui). Note that any add-ons using JSON UI will eventually break in the coming years.
+Unlike JSON UI, Ore UI is hardcoded and cannot be modified by resource packs.
 :::
 
 :::tip

docs/meta/addon-performance.md

@@ -1,5 +1,5 @@
 ---
-title: Add-on Performance
+title: Add-On Performance
 mentions:
     - SirLich
     - Joelant05

docs/nbt/mcstructure.md

@@ -67,13 +67,19 @@ In this case, the file in the `mystructure` folder is the one that "wins," resul
 > > > > >
 > > > > > > ![String][string] `name`: The block's identifier, such as `minecraft:planks`.
 > > > > > > ![Compound][compound] `states`: The block's states as keys and values. Examples: `wood_type:"acacia"`, `bite_counter:3`, `open_bit:1b`. The values are the appropriate NBT type for the state: strings for enum values, integers for scalar numbers, and bytes for boolean values.
-> > > > > > ![Integer][int] `version`: Compatibility versioning number for this block (currently `17959425` as of writing, in 1.19).
+> > > > > > ![Integer][int] `version`: Compatibility versioning number for this block (currently `17959425` as of writing, in 1.19). For example, `17879555` is hex `01 10 D2 03`, meaning 1.16.210.03.
 > > > >
 > > > > ![Compound][compound] `block_position_data`: Contains additional data for individual blocks in the structure. Each key is an integer index into the flattened list of blocks inside of `block_indices`. Layer is unspecified as it is irrelevant.
 > > > >
-> > > > > ![Compound][compound] `<index>`: A single piece of additional block data, applied to the block at its index position.
-> > > > >
-> > > > > > ![Compound][compound] `block_entity_data`: Block entity data as NBT, stored the same as block entities in the world file itself. Position tags are saved, but replaced upon loading. No other objects seem to exist adjacent to this one at this time.
+> > > > > ![Compound][compound] `<index>`: A single piece of additional block data, relevant to the block at its index position.
+> > > > > 
+> > > > > > ![Compound][compound] `block_entity_data`: Block entity data as NBT, stored exactly the same as block entities in the world file itself. Position tags are saved, but replaced upon loading. Layer is unspecified, as multiple block entities cannot coexist in a block space.
+> > > > > >
+> > > > > > ![List][list] `tick_queue_data`: Contains one more compounds of scheduled tick information. This is used for blocks like coral to make it die, water to make it flow, and other various scheduled updates.
+> > > > > > 
+> > > > > > > ![Compound][compound] A single pending tick.
+> > > > > > > 
+> > > > > > > > ![Integer][int] `tick_delay`: The amount of ticks remaining until this block should be updated. No other values seem to exist adjacent to this one at this time.
 >
 > ![List][list] `structure_world_origin`: List of three integers describing where in the world the structure was initially saved. Equal to the position of the saving structure block, plus its offset settings. This is used to determine where entities should be placed when loading. An entity's new absolute position is equal to its old position, minus these values, plus the origin of the structure's loading position.
 >

docs/visuals/math-based-animations.md

@@ -1,5 +1,5 @@
 ---
-title: Math-based Animations
+title: Math-Based Animations
 tags:
     - intermediate
 category: General

docs/visuals/structure-presentation.md

@@ -38,6 +38,17 @@ By making [JSON UI](/json-ui/json-ui-intro) edits you can change the background
 
 ![](/assets/images/visuals/structure-presentation/structure-block-1.png)
 
+Or you can use the **Structure Presentation Pack** by @minato4743 to simplify the process. It includes some default colors and gradients as well as a toggle to hide the preview arrows.
+
+<Button link="/assets/packs/visuals/structure-presentation/structure_presentation_pack.mcpack" download>
+    Download Pack
+</Button>
+
+![](/assets/images/visuals/structure-presentation/structure_presentation_pack.png)
+
+![](/assets/images/visuals/structure-presentation/pack_gradient_result.png)
+
+
 ### Rendered 3D Object
 
 Structures can be exported as a 3d model. If 3D export button is not working for you, you can try applying a 3d-export-fix pack.