Skip to content
You're viewing an older version of this GitHub Action. Do you want to see the latest version instead?
box

GitHub Action

Minecraft Bedrock Action: Create MCWorld

v1.0

Minecraft Bedrock Action: Create MCWorld

box

Minecraft Bedrock Action: Create MCWorld

The github action that will create a mcworld in a given respository

Installation

Copy and paste the following snippet into your .yml file.

              

- name: Minecraft Bedrock Action: Create MCWorld

uses: Blockception/[email protected]

Learn more about this action in Blockception/MB-Action-Create-MCWorld

Choose a version

Minecraft Bedrock Action: Create MCWorld

The github action that will create a mcworld in a given respository

Inputs

folder:
The folder where the world is, example ${{github.workspace}}/world

processJson:
Whether or not to format json and minify json, defaults to true

trimFiles:
Whether or not to remove unwanted files, defaults to true

Outputs

worldFilepath:
The outputted mcworld filepath

Example usage

# This is a basic workflow to help you get started with Actions
name: create-mcworld

# Controls when the action will run.
on:
  push:
    # Sequence of patterns matched against refs/tags
    tags:
      - "v*"

  # Allows you to run this workflow manually from the Actions tab
  workflow_dispatch:

# A workflow run is made up of one or more jobs that can run sequentially or in parallel
jobs:
  # This workflow contains a single job called "build"
  build:
    # The type of runner that the job will run on
    runs-on: ubuntu-latest

    # Steps represent a sequence of tasks that will be executed as part of the job
    steps:
      # Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
      - uses: actions/checkout@v2

      # Runs a single command using the runners shell
      - uses: Blockception/[email protected]
        id: create_mcworld
        with:
          # Path to the folder, assume ${{github.workspace}} leads to root of the repo
          folder: ${{github.workspace}}/world

      # Creates the release page
      - name: Create Release
        id: create_release
        uses: actions/create-release@v1
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} # This token is provided by Actions, you do not need to create your own token
        with:
          tag_name: ${{ github.ref }}
          release_name: Release ${{ github.ref }}
          body: automated release
          draft: false
          prerelease: false

      # Uploads to the newly made release
      - name: Upload Release Asset
        id: upload-release-asset
        uses: actions/upload-release-asset@v1
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
        with:
          upload_url: ${{ steps.create_release.outputs.upload_url }} # This pulls from the CREATE RELEASE step above, referencing it's ID to get its outputs object, which include a `upload_url`. See this blog post for more info: https://jasonet.co/posts/new-features-of-github-actions/#passing-data-to-future-steps
          asset_path: ${{ steps.create_mcworld.outputs.worldFilepath }}
          asset_name: world.mcworld
          asset_content_type: application/zip