fix: Use Bedrock GDK (#114)

Author: mammerla

addon_starter/1_hello_world/.env

@@ -1,3 +1,3 @@
 PROJECT_NAME="aop_mobs"
-MINECRAFT_PRODUCT="BedrockUWP"
+MINECRAFT_PRODUCT="BedrockGDK"
 CUSTOM_DEPLOYMENT_PATH=""

addon_starter/1_hello_world/package-lock.json

@@ -5,7 +5,7 @@
   "description": "Minecraft Add-On Hello World Project",
   "private": true,
   "devDependencies": {
-    "@minecraft/core-build-tasks": "^5.2.0",
+    "@minecraft/core-build-tasks": "^5.5.0",
     "eslint-plugin-minecraft-linting": "^2.0.2",
     "source-map": "^0.7.4",
     "ts-node": "^10.9.1",

addon_starter/1_hello_world/package.json

@@ -1,3 +1,3 @@
 PROJECT_NAME="aop_mobs"
-MINECRAFT_PRODUCT="BedrockUWP"
+MINECRAFT_PRODUCT="BedrockGDK"
 CUSTOM_DEPLOYMENT_PATH=""

addon_starter/2_entities/.env

@@ -5,7 +5,7 @@
   "description": "Minecraft Add-On Entities Project",
   "private": true,
   "devDependencies": {
-    "@minecraft/core-build-tasks": "^5.2.0",
+    "@minecraft/core-build-tasks": "^5.5.0",
     "eslint-plugin-minecraft-linting": "^2.0.2",
     "source-map": "^0.7.4",
     "ts-node": "^10.9.1",

addon_starter/2_entities/package-lock.json

@@ -14,10 +14,10 @@ products:
 
 This sample demonstrates everything you need to have an add-on in Minecraft. There are three versions and progressions:
 
-* `start` is a foundational starter project. It comes with a justjs-based workflow tool 
-* `1_hello_world` is a basic entity that will show you that your add-on is working. It comes a mob that overrides the default cow in Minecraft
-* `2_entities` adds a set of entities (from the MCLive2022 add-on pack to the add-on)
-* `complete` adds more functionality and scripts to the add-on
+- `start` is a foundational starter project. It comes with a justjs-based workflow tool
+- `1_hello_world` is a basic entity that will show you that your add-on is working. It comes a mob that overrides the default cow in Minecraft
+- `2_entities` adds a set of entities (from the MCLive2022 add-on pack to the add-on)
+- `complete` adds more functionality and scripts to the add-on
 
 ## Prerequisites
 
@@ -45,35 +45,35 @@ Visit the [Visual Studio Code website](https://code.visualstudio.com) and instal
 
 1. Open a Windows Terminal or PowerShell window and change the working directory to your **myaddon** folder:
 
-    ```powershell
-    cd c:\projects\myaddon\
-    ```
+   ```powershell
+   cd c:\projects\myaddon\
+   ```
 
 1. Use NPM to install our tools:
 
-    ```powershell
-    npm i
-    ```
+   ```powershell
+   npm i
+   ```
 
 1. Use this shortcut command to open the project in Visual Studio Code:
 
-    ```powershell
-    code .
-    ```
+   ```powershell
+   code .
+   ```
 
 It might also ask you to install the Minecraft Debugger and Blockception's Visual Studio Code plugin, which are plugins to Visual Studio Code that can help with Minecraft development. Go ahead and do that, if you haven't already.
 
 1. In Visual Studio Code, open the file `.env`. This contains the environment variables to use to configure project:
 
 ```
 PROJECT_NAME="starter"
-MINECRAFT_PRODUCT="BedrockUWP"
+MINECRAFT_PRODUCT="BedrockGDK"
 CUSTOM_DEPLOYMENT_PATH=""
 ```
 
 - **PROJECT_NAME** is used as the folder name under all the assets are going to be deployed inside the game directories (e.g., development_behavior_packs\\**PROJECT_NAME**, development_resource_packs\\**PROJECT_NAME**).
 
-- **MINECRAFT_PRODUCT**. You can choose to use either Minecraft or Minecraft Preview to debug and work with your scripts. These are the possible values: **BedrockUWP, PreviewUWP, Custom**.
+- **MINECRAFT_PRODUCT**. You can choose to use either Minecraft or Minecraft Preview to debug and work with your scripts. These are the possible values: **BedrockGDK, BedrockGDK, Custom**.
   Use **Custom** in case of deploy on any other path.
 
 - **CUSTOM_DEPLOYMENT_PATH**. In case of using **Custom** for **MINECRAFT_PRODUCT**, this is the path used to generate the assets.
@@ -100,7 +100,4 @@ With this starter, you've seen how to build a nice little add-on.
 
 ## Manifest
 
--[start](https://github.com/microsoft/minecraft-samples/blob/main/addon_starter/1_hello_world): This contains a starter add-on bare-minimum set of files.
--[1_hello_world](https://github.com/microsoft/minecraft-samples/blob/main/addon_starter/1_hello_world): This contains a starter add-on with a basic starter entity.
--[2_entities](https://github.com/microsoft/minecraft-samples/blob/main/addon_starter/2_entities): This contains a starter add-on with a full set of entities. 
--[complete](https://github.com/microsoft/minecraft-samples/blob/main/addon_starter/complete): This contains the finished add-on starter example.
+-[start](https://github.com/microsoft/minecraft-samples/blob/main/addon_starter/1_hello_world): This contains a starter add-on bare-minimum set of files. -[1_hello_world](https://github.com/microsoft/minecraft-samples/blob/main/addon_starter/1_hello_world): This contains a starter add-on with a basic starter entity. -[2_entities](https://github.com/microsoft/minecraft-samples/blob/main/addon_starter/2_entities): This contains a starter add-on with a full set of entities. -[complete](https://github.com/microsoft/minecraft-samples/blob/main/addon_starter/complete): This contains the finished add-on starter example.

addon_starter/2_entities/package.json

@@ -1,3 +1,3 @@
 PROJECT_NAME="aop_mobs"
-MINECRAFT_PRODUCT="BedrockUWP"
+MINECRAFT_PRODUCT="BedrockGDK"
 CUSTOM_DEPLOYMENT_PATH=""