Lantern for Minecraft Bedrock

A proper IDE experience for Bedrock Add-Ons. Create add-ons efficiently by cutting out time scrolling through folders and manipulating files.

Features

Grouped Files

This extension adds a new view within the explorer which groups Minecraft Bedrock Add-On Files by identifier.

It currently groups files linked to entities, items, and blocks.

In the below picture, it shows all files linked to the chicken in the vanilla packs. The group view is in the secondary sidebar.

In the below picture, it shows all files linked to the zombie in the vanilla packs. The group view is in the same panel as the explorer.

Import from Snippet Repository

Lantern has a smart import feature that allows you to import files from repositories.

To use this, click on the package icon in the lantern menu or run Lantern: Open Snippet Repository UI from the command pallete.

Below is an example of importing a slime block from the bedrock-oss examples repository:

It renames imported files, their identifiers, and references to save you time.

To begin with, you must add a source for your snippets. Press the plus button on the top of the UI that is now open.

The repository https://github.com/Bedrock-OSS/bedrock-examples is a collection of examples created by Bedrock-OSS. Paste the link into the vscode dialogue to add it.

You can also create your own repositories to fetch snippets from.

Import from Vanilla Packs

If you right click on a directory in the entity section of the grouped files panel you can select Import Entity from Vanilla. A UI will come up which allows you to rename the identifier and files linked to the entity.

You can also run this using the command pallete under the command Lantern: Import Entity from Vanilla

This will download everything that links to the entity e.g. animations, render controllers

Linking scripts

Scripts aren't tied to a single identifier, so you link them explicitly with a @lantern-links-* comment placed directly above the code it relates to:

import { world } from "@minecraft/server"

// @lantern-links-entities ["custom:goblin"]
world.afterEvents.entityDie.subscribe((event) => {
    if (event.deadEntity.typeId === "custom:goblin") {
        // ...goblin death logic
    }
})

// @lantern-links-items ["custom:ruby"]
world.afterEvents.itemUse.subscribe((event) => {
    if (event.itemStack.typeId === "custom:ruby") {
        // ...ruby use logic
    }
})


// @lantern-links-blocks ["custom:slab"]
world.afterEvents.placeBlock.subscribe((event) => {
    if (event.block.typeId === "custom:ruby") {
        // ...slab use logic
    }
})

This file now shows up as a child of custom:goblin and custom:ruby in the Lantern view.

List several ids in one comment to link them all e.g. // @lantern-links-entities ["custom:goblin", "custom:goblin_king"].

The fastest way to add one: put your cursor on the relevant line in a .ts/.js file and right-click → Link to Entity/Item/Block; the comment is inserted just above.

Requirements

You must have a config.json file at the root of the project with the following keys:

{
	"packs": {
		"behaviorPack": "./packs/BP",
		"resourcePack": "./packs/RP"
	}
}

This conforms to the Bedrock OSS Project Config Standard.

If you have opened an existing regolith/dash/bridge/bedrockcli project then you will already have this within your project.

For more information

• Release Notes
• Repository

Attribution

• The icons in the sidebar were taken from SirLich/bedrock-addon-icons [LICENSE]

• This includes icons from Godot. [LICENSE]

• File and folder icons are taken from microsoft/vscode-codicons [LICENSE]