Minecraft: Bedrock Edition Creator Documentation

repository·main·Indexed 42 days ago

https://github.com/microsoftdocs/minecraft-creator

Documentation for developers customizing Minecraft: Bedrock Edition using Add-Ons. Includes detailed references for in-game commands such as /camera for perspective and FOV control, /aimassist for player configuration, /allowlist for server access, /clone for block manipulation, and /changesetting for server administration.

Tokens
375K
Snippets
872
Records
1.7K
Agent score
54%

What's inside Minecraft

  1. What is Snowstorm and how to use it for particle effects

    main

    Snowstorm is a third-party visual editing tool used to design particles and particle effects for Minecraft: Bedrock Edition.

    In Minecraft: Bedrock Edition, you can create:

    • Particles: Lightweight visual items.
    • Particle Emitters: Logic that determines when particles are created.

    Once designed, these particles can be included in your resource packs and triggered using the /particle command or via JSON definitions. Snowstorm provides a visual interface to edit the underlying particle files.

    Note: Snowstorm is an external tool provided by third-party contributors (JannisX11) and is not an official Mojang or Microsoft product.

  2. Introduction to Scripting in Minecraft: Bedrock Edition

    main

    Scripting in Minecraft: Bedrock Edition allows you to extend customization beyond textures and properties by writing programs that respond to game events. Scripts can control entities, blocks, and items, manipulate the world, and create new game mechanics.

    Language Support

    • JavaScript: The primary language used for scripting.
    • TypeScript: A dialect of JavaScript that adds additional syntax and features. While it requires extra setup steps, the concepts learned in JavaScript apply to TypeScript as well.
  3. What is Chunker and how to access it

    main

    Chunker is a third-party, open-source tool used to convert Minecraft worlds between Java Edition and Bedrock Edition. It can be run as a standalone application on Windows, Mac, and Linux, or via a Command Line Interface (CLI).

    Important Note: Chunker is provided by external contributors and is not an official Mojang or Microsoft product. Use it at your own discretion.

    Capabilities:

    • Converts level settings, world data (blocks, biomes, tile entities), multiple dimensions, containers/items, and in-game maps.
    • Note: It currently cannot convert entities or player inventories, unless you are editing a world and outputting to the same source world version (in which case they are kept).

    Access: Download the application or CLI version from the official GitHub releases page: https://github.com/HiveGamesOSS/Chunker/releases.

  4. Validate sound_definitions.json files

    main
    The Minecraft Creator Tools provide validation rules for sound_definitions.json files used in resource packs. These rules ensure that custom sounds are properly defined, follow the correct JSON syntax, and reference audio files using the expected folder structure. Validation helps prevent runtime issues where sounds might fail to play due to structural errors or incorrect file paths.
  5. Use the System class for system-level operations

    main

    The System class in @minecraft/server provides access to system-level events, world state information, and scheduling functions. It is a central hub for managing game loops, delays, and asynchronous tasks within the Minecraft engine.

    Key capabilities include:

    • Scheduling: Running code in the next tick, at intervals, or after a delay.
    • State Access: Checking the currentTick, whether the world is in an editor, and accessing serverSystemInfo.
    • Events: Accessing afterEvents and beforeEvents for system-level operations.
    • Job Management: Running long-running tasks using Generators via runJob to prevent frame drops.
  6. MCTools Validation Rules Reference

    main
    MCTools uses a comprehensive set of validation rules to check Minecraft add-on content for potential issues before deployment. These rules cover everything from manifest integrity and JSON schema compliance to texture dimensions and file path lengths. Use these rules to identify errors, warnings, and best practices in your project.
  7. Project Integrity Validation Rules

    main

    Minecraft Creator Tools includes Project Integrity validation to ensure the structural correctness of your project. These rules check for orphaned files and improperly organized pack structures to prevent deployment errors.

    There are two primary validation rules:

    1. PRJINT101 (Extraneous Content): A Warning triggered when files or folders exist that are not part of any recognized pack structure. These are considered 'orphaned' files.
    2. PRJINT102 (Nested Pack Structure): An Error triggered when a pack contains multiple manifest.json files. Minecraft packs must have exactly one manifest.json at their root; nested packs are not supported.