The arguments are not specified correctly The command can then be executed, and the player is sent to those coordinates. In Java Edition, the coordinates in these messages can be clicked, which can put the command / tp ~ in the chat box. When locating biome, if successful, the following message is sent to chat: ' The nearest is at ( blocks away)', in which is the distance from the executor to the biome. When locating structure or POI, if successful, the following message is sent to chat: ' The nearest is at ( blocks away)', in which is the horizontal distance from the executor. , the search range is a ball with a radius of 256 blocks. The horizonal search range is 12801×12801 blocks in Java Edition. , the horizonal search resolution is 32 blocks, and vertical resolution is 64 blocks, which means biomes that are too narrow may not be found. Structures in the Anvil chunk region of the command's execution are prioritized over others due to a bug, meaning the found structure is not necessarily the closest. In Java Edition, the horizonal search range is 201×201 chunks. , the vertical coordinate of structure is ignored when finding. This argument also supports point of interest type tags, as following: Tagįor /locate structure. The following are resource locations of POIs: Point of Interest

Must be an existing registered resource location or tag in minecraft:point_of_interest_type registry. JE : : resource_or_tag Specifies the point of interest to locate. Must be a boolean (either true or false). In Bedrock Edition, must be an ID of a generated structure (without namespace)īE: useNewChunksOnly: Boolean: enum Specifies if a structure of any type wants to be located in new chunks only ( true) or not ( false), and it's false by default. In Java Edition, must be a resource location or a tag, which will be resolved during command execution into an entry or tag in minecraft:worldgen/structure registry. JE (case-sensitive): : resource_or_tag_keyīE: structure: Structure: enum Specifies the structure to locate. In Bedrock Edition, must be an ID of a biome (without namespace) In Java Edition, must be an existing registered resource location or tag in minecraft:worldgen/biome registry. In Java Edition, this argument also supports biome tags. locate structure /locate biome Arguments īE: biome: Biome: enum Specifies the biome to locate. I really don't want this to come off as just negative, because there's so much potential here and the key to unlocking it is so simple with these basic sensing commands, it's just that I cannot overstate how the current lack of them really is an insurmountable roadblock./locate structure /locate biome /locate poi Our group thinks MEE has such incredible potential, but in our programming classes (in any language), a big focus is always on how programming gives us a foundation of powerful yet simple commands that we can then build from to create infinitely more complex and exciting results with the current MEE feature-set however, we're just not seeing the same potential as other platforms such as Scratch (as an example for this age-range) do such a fantastic job of offering. I noticed an 'extensions' area, but haven't been able to find any real information on user-created blocks, functions, commands, etc., so any info on that would be appreciated as well. I'm looking for anyone associated with MEE itself or from the community that has any information on these issues and/or possible solutions. There are certain features that we'd love to see, such as creating custom crafting recipes that we know would be really engaging for our students, but the lack of sensing abilities like the ones listed above are absolutely the most important by far, to the point I'd say they should be labeled 'essential.' Without a strong set of tools to get information from and about the environment, we're in a position where we can't really take what we've been given and 'build' to anything more in-depth.

Get location of block player has destroyed.

Get location of block player has placed.

Get location of block player is looking/aiming at.

A quick example that I hope helps describe the type of commands we're surprised are missing is the ability to get the location of blocks where certain actions/events have taken place for instance: It feels as though we're missing some of the most basic/essential building-blocks required to really advance the classes beyond the surface-level activities our kids will complete within the first few classes. The huge issue my team and I are running into when working on lesson-plans and curriculum for Minecraft Education Edition is that there seem to be some surprising omissions in-terms of commands for 'sensing' certain things in the world.

Minecraft teleport command 1.13 facing